Date: Wed, 31 Dec 2003 16:02:27 -0800 From: Tim Kientzle <kientzle@acm.org> To: David Gilbert <dgilbert@dclg.ca> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: 5.1-R-p11 unable to "sync disks" when shutting down Message-ID: <3FF36393.6000109@acm.org> In-Reply-To: <16371.24594.660308.151100@canoe.dclg.ca> References: <20031229164130.GA797@pp.htv.fi> <16370.20382.81302.449649@canoe.dclg.ca> <16371.20373.212950.533985@canoe.dclg.ca> <20031231152453.G1441@bo.vpnaa.bet> <3FF35F60.1070803@acm.org> <16371.24594.660308.151100@canoe.dclg.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
David Gilbert wrote: >>>>>>"Tim" == Tim Kientzle <kientzle@acm.org> writes: > > Tim> What's needed is some way for fsck to mark a filesystem as > Tim> having a bgfsck in progress. Then fsck -F can check for that marker. > > Hrm. Isn't this done? Isn't there a 'special' snapshot created by > the bgfsck process? Or does this snapshot evaporate (have no links)? You've exceeded my expertise with that one. Also, using the snapshot as a flag wouldn't be robust against errors in the snapshot code itself. I note that fsck_ffs sets a flag "needs foreground check" if the background check fails. It might suffice to change the logic just a bit: * Set this flag when bg check starts * Clear the flag when bg check succeeds That would ensure that a foreground check gets done if the system rebooted during the bg check or if the bg check crashed for any reason. I'm not sufficiently familiar with fsck_ffs to tackle this, but it could be a pretty simple fix. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FF36393.6000109>