Date: Wed, 25 Dec 1996 11:58:59 +1030 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: andreas@klemm.gtn.com (Andreas Klemm) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org, mrcpu@cdsnet.net Subject: Re: mount -o noatime unsupported in -current? Message-ID: <199612250129.LAA21213@genesis.atrad.adelaide.edu.au> In-Reply-To: <Pine.BSF.3.95.961224142452.27730A-100000@klemm.gtn.com> from Andreas Klemm at "Dec 24, 96 02:27:35 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Andreas Klemm stands accused of saying: > > > > Yes, i'm using it often before rm -r'ing a large subhierarchy (and > > ``mount -o noasync -u'' later). > > Yes, this is a nice trick ;) Then rm -rf works like hell ;-)) > It's blindly fast and very dangerous ;) Actually, I've crashed any number of boxes using '-o async' and have yet to lose anything substantial. We don't ship with it because fsck tends to get a bit unhappy about it, and talking a customer through a manual fsck can be a pain, but internally we use it all the time; IMHO the performance advantage for things like large CVS operations and big deletions is a fair tradeoff against the possible risk of having to restore from backup. > andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612250129.LAA21213>