Date: Sat, 23 Mar 1996 00:11:08 -0800 (PST) From: Rob Mallory <rmallory@wiley.csusb.edu> To: bde@zeta.org.au (Bruce Evans) Cc: bde@zeta.org.au, terry@lambert.org, freebsd-current@freefall.freebsd.org Subject: Re: lost+found ??? Message-ID: <199603230811.AAA27044@wiley.csusb.edu> In-Reply-To: <199603230444.PAA08953@godzilla.zeta.org.au> from "Bruce Evans" at Mar 23, 96 03:44:44 pm
index | next in thread | previous in thread | raw e-mail
> > >> >Of course if you mount async, all bets are off. 8-(. > >> > >> I.e., lost+found only works when it is least needed :-). > > >Not true. If you are running async, you are obviously willing > >to newfs the partition when you reboot after a crash. I've only > >barely refrained from suggesting we change the option name from > >"async" to "i_am_willing_to_newfs_the_partition_after_a_crash". > > Yes, I expect to lose it all after every 1000-100000 crashes. > Ummm.. I think I might lean towards Terry's mount -o flag mentioned above... knowing which filesystems to "risk" (/usr/obj is good) and having current backups is good. Then again, I see newfs/restore as the perfect "speed-disk" defragger, and -async as a perfect excuse to defrag my disks every now and then!! recently, I defragg'd after it lost the "." directory of my /usr/obj async mounted filesystem. fuzz-check put a new lost+found in the newly created (empty) directory of the async filesystem,, but I laughed when 'df' reported 78% usage! hehe! ((hey--I noticed recently you cant newfs a mounted filesystem like you could about 4 months ago.:( I defrag'd my / one time when newfs'ing what I thought to be a new drive... it was rather cool doing a 'cat etc/*' after realizing what i really newfs'd, and watching the buffer-cache work really well! it actually still "had" a bunch of files for a few seconds before a major panic! hehe.. freebsd is fun. -Rob Malloryhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603230811.AAA27044>