Date: Sun, 3 Apr 2011 17:29:22 +0300 From: George Kontostanos <gkontos.mail@gmail.com> To: Bruce Cran <bruce@cran.org.uk> Cc: Stefan `Sec` Zehl <sec@42.org>, freebsd-stable@freebsd.org, Marko Lerota <mlerota@claresco.hr> Subject: Re: Constant rebooting after power loss Message-ID: <BANLkTimg0OFNSNkdzSjnFR7GbU3LWc%2BizQ@mail.gmail.com> In-Reply-To: <4D986266.9060205@cran.org.uk> References: <87d3l6p5xv.fsf@cosmos.claresco.hr> <20110401154732.GC37730@ice.42.org> <4D986266.9060205@cran.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Those are workarounds. A system should not reach to a point where it doesn't come up because of a pending fsck. And even if it does console access must be ensured. My point is that by disabling these you might bring it up but you seriously risk data integrity. Regards On Sun, Apr 3, 2011 at 3:04 PM, Bruce Cran <bruce@cran.org.uk> wrote: > On 01/04/2011 16:47, Stefan `Sec` Zehl wrote: > > If you want to get rid of the reboot loop, set: >> >> background_fsck="NO" >> >> Then it will either come up, or ask for help if anything fails. >> > > I realise that people like having systems that come up quickly after a > crash, but is it worth reconsidering disabling background fsck by default > since it can cause issues like this? > > -- > Bruce Cran > > -- George Kontostanos aisecure.net <http://www.aisecure.net>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTimg0OFNSNkdzSjnFR7GbU3LWc%2BizQ>