Date: Mon, 23 Jun 2008 14:41:29 -0400 From: "Zaphod Beeblebrox" <zbeeble@gmail.com> To: "Dominic Fandrey" <kamikaze@bsdforen.de> Cc: csaba-ml@creo.hu, freebsd-hackers@freebsd.org, Anish Mistry <amistry@am-productions.biz> Subject: Re: FreeBSD fusefs-kmod shutdown problem workaround Message-ID: <5f67a8c40806231141vf7b9567mdf75e81f32169211@mail.gmail.com> In-Reply-To: <485F4593.9050807@bsdforen.de> References: <485EAE11.2050808@bsdforen.de> <200806221615.50498.amistry@am-productions.biz> <485F4593.9050807@bsdforen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 23, 2008 at 2:41 AM, Dominic Fandrey <kamikaze@bsdforen.de> wrote: > Thanks for the pointer. Unfortunately it seems that Csaba's patch only > allows you to stall shutdown for 10 seconds. After heavy writing > more than a minute can be necessary to prevent data loss. > > I have created a problem report: ports/124901 > http://www.freebsd.org/cgi/query-pr.cgi?pr=124901 > > I hope this will make it. To me data loss and file system corruption > are the worst case scenario and to me it's worth stalling shutdown > for as long as it takes to write the data. > The shutdown watchdog timer is something I've had to adjust many times for many different ports. Given this; I propose we have (at least) a new rcorder script variable. Something like "SHUTTIME" encoding the expected number of seconds required for the daemon to shutdown in the worst case. Ideally, you'd want an overall watchdog and a per-script watchdog (so that you're not waiting the sum of all these times in most cases).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40806231141vf7b9567mdf75e81f32169211>