> This was completely untested by us, and is not guaranteed to work! I think
> you were lucky. We move and change blocks on the filesystem, during some
> time the filesystem is NOT consitent, so if one of those files is accessed than
> you might run into a panic.
Sorry? In single user with a readonly / and nothing else? I would have to be
EXTREMELY unlucky to get any other access while the fs is inconsistent ;-)
Seriously, I get the point (shit happens doesn't it?), but this prompts my next
question: isn't this the same as running fsck? Maybe with growfs we have a
longer window of inconsistency, but the idea is mostly the same. I think there
should be (probably there already is) a way to "reserve" access to the fs, so
that no other process can possibly get an inconsistent state.
--
Speak softly and carry a cellular phone.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
