On 05/07/2010, at 1:07, Dimitry Andric wrote: > bsdlabel -e /dev/md0s1 > > The last one indeed fails, because the device is in use. This is > expected, but the error message is very misleading, and should be > improved.
Maybe, I wouldn't call it expected because it used to work :) I agree about the error message though! > The real 'bug' (although there will probably be loads of bikesheds about > it) is probably that if you *do* unmount the filesystem, bsdlabel still > fails: > > umount /mnt/test > bsdlabel -e /dev/md0s1 > [class not found yada yada] > > Apparently, unmounting does not properly 'release' whatever underlying > geom device is preventing read/write access. However, if you then set > the footshooting flag: > > sysctl -w kern.geom.debugflags=0x10 > bsdlabel -e /dev/md0s1 > > bsdlabel can write without problems, at least on my box. Stranger > even, if you subsequently turn off the footshooting flag, it *still* > can write to the label. That is, unless you mount and unmount the > filesystem, after which is again, sort of 'locked' against writing. > > All highly confusing. :) Hmm odd, the sysctl had no effect here.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"