On Sat, 7 Dec 2002, Archie Cobbs wrote:
> Bruce Evans wrote: > > > So in summary my recommendation is to add a big warning to the > > > growfs(1) man page that is should not be run on the root partition, > > > even if you have booted single-user mode and haven't mounted / yet. > > > I.e., to grow a root partition, you must boot from a different partition. > > > > 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. I've seen ufs write back the superblock on unmounting a read-only filesystem (!). it was a few years ago but I wouldn;t be surprised if it was still true.. After you did it on the filesystem. (ran growfs) what did you do next? the safe answer would be to pull the plug. > > In any case, when you're talking about the danger of destroying a > filesystem it probably wouldn't hurt to have a little extra clarity > in the documentation. > > Or better yet, should the kernel prevent raw writes to the / partition? > Guess that would prevent fsck from working though. > > -Archie > > __________________________________________________________________________ > 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
