Re: a new way to hang 7.0
- From: Elliot Finley <efinleywork@xxxxxxxxxxx>
- Date: Mon, 31 Dec 2007 08:39:54 -0700
On Sun, 30 Dec 2007 12:19:29 -0500, you wrote:
The system is a dual-Xeon (i386) running 7.0-PRERELEASE as of Dec 29th.
It went like this:
root@corbulon:/home/mi (102) dump 0auCLf 32 - / | gzip -9 > /net/blue/corbulon.root.0.dump.gz
/net/blue/corbulon.root.0.dump.gz: Read-only file system.
^C^C [... hang ...]
Indeed, I mistyped the destination path and ended up in the
non-writable directory.
Something -- I'd guess, it was the snapshot-creation -- hung
the system solid.
After correcting the destination path and REBOOTING, the dump
is proceeding. I removed the L-flag too, just in case :(
Is this really a new way, or is it well known already? Thanks!
-L has been hanging systems ever since it existed. Don't use it.
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: a new way to hang 7.0
- From: Mikhail Teterin
- Re: a new way to hang 7.0
- From: Michael Butler
- Re: a new way to hang 7.0
- References:
- a new way to hang 7.0
- From: Mikhail Teterin
- a new way to hang 7.0
- Prev by Date: Problem with Atheros 5424/2424 on Current AMD64
- Next by Date: Re: a new way to hang 7.0
- Previous by thread: a new way to hang 7.0
- Next by thread: Re: a new way to hang 7.0
- Index(es):