Date: Mon, 12 Jun 2006 16:44:48 -0400 From: "Zaphod Beeblebrox" <zbeeble@gmail.com> To: "=?ISO-8859-1?Q?Bj=F6rn_K=F6nig?=" <bkoenig@cs.tu-berlin.de>, stable@freebsd.org Subject: Re: unmounting a filesystem safely that doesn't exist anymore Message-ID: <5f67a8c40606121344g18d53ce9x4038384a734c3ce0@mail.gmail.com> In-Reply-To: <20060612193427.GE1226@roadrunner.aventurien.local> References: <448B0419.3090303@cs.tu-berlin.de> <20060612193427.GE1226@roadrunner.aventurien.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/12/06, Ulrich Spoerlein <uspoerlein@gmail.com> wrote: > > Bj=F6rn K=F6nig wrote: > > > I did a mistake: I unplugged my digital camera accidentally before I > unmounted the > > filesystem. *doh* This happens very often, because I'm very > scatterbrained. =3D) The kernel > > will panic and all filesystems remain unclean in any case now. I know > that this is a well > > know issue and in past discussions you stated that this behaviour is > intended and won't be > > changed ad hoc. I just want to know if somebody knows a workaround or > small trick that > > prevents the other filesystems from being unclean on next boot-up. > > You might give the automounter (am-utils) a whirl. They are very > confusing to set up, but you can set the unmount-if-unused timeout to > something like 5 seconds. This could narrow the window enough to not > panic you system frequently :) That's rather hackish ... especially since this is a common problem and a rather obvious hole in using FreeBSD for noobs. It seems that a better solution would be to allow filesystems to be mounted with a 'sync' flag. Or even an ULTRA-sync flag. Meaning strict sync semantics and even 'sync' running against the FS every few seconds. If a filesystem so-mounted completely disappears (or errors out), then it should just go "poof" as if it was umount -f'd.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40606121344g18d53ce9x4038384a734c3ce0>