Bruce Evans wrote: > > > Er, it should be obvious that growfs can't reasonably work on the mounted > > > partitions. growfs.1 doesn't exist, but growfs.8 already has the warning > > > in a general form: > > > > > > .... Currently growfs can only enlarge unmounted file systems. Do not > > > try enlarging a mounted file system, your system may panic and you will > > > not be able to use the file system any longer... > > > > Well, I suspected that it might not work... but I would disagree that it > > was *obvious* that it would not work. This was before "mount" had been > > run, so / was supposedly mounted (?) read-only. > > Perhaps the unobvious point is that fsck could work. If the mount is r/w, > then neither growfs nor fsck can even open the partition r/w. fsck somehow > works in the case of a r/o root, but growfs apparently doesn't. I think > fsck depends on no other processes making (significant) vfs syscalls for > on the same partition while it is running (even r/o ones might be harmful > if they caused reads of metadata which might be inconsistent). Then when > fsck has finished it calls mount(... MNT_RELOAD...) to sync the metadata. > growfs doesn't do this, and even if it did it is not clear that it does > all the necessary syncing (growfs may change more or different metadata). > However, I think it does most of the necessary things.
FYI, I submitted a bug/enhancement request to summarize this.. http://www.freebsd.org/cgi/query-pr.cgi?pr=46110 -Archie P.S. Why does submitting a bug now generate an email response from (and who the heck is) "ThinkHost Support" ?? __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
