Date: Mon, 28 Jul 2008 17:10:03 +0200 From: Pawel Worach <pawel.worach@gmail.com> To: RW <fbsd06@mlists.homeunix.com> Cc: freebsd-hackers@freebsd.org Subject: Re: forcefsck on booting stage Message-ID: <488DE14B.2040103@gmail.com> In-Reply-To: <20080728153204.567bb54c@gumby.homeunix.com.> References: <488DB785.3020805@gmail.com> <20080728130057.GA798@eos.sc1.parodius.com> <200807281510.12070.marc.loerner@hob.de> <20080728153204.567bb54c@gumby.homeunix.com.>
next in thread | previous in thread | raw e-mail | index | archive | help
RW wrote: > On Mon, 28 Jul 2008 15:10:11 +0200 > Marc L__rner<marc.loerner@hob.de> wrote: > >> On Monday 28 July 2008 15:00, Jeremy Chadwick wrote: >>> On Mon, Jul 28, 2008 at 04:11:49PM +0400, sam wrote: >>>> Hello, >>>> >>>> How to make 'fsck -f' on booting stage of remote system? >>> I believe by setting background_fsck="no" in /etc/rc.conf? That's >>> the only way I know of, besides booting single user and doing it >>> manually. >> Doesn't this only disable background fsck support? >> By creating file "/forcefsck" you can force an fsck at next reboot, >> because some scripts test for existence. > > That's in linux AFAIK, but it would be fairly straightforward to > modify /etc/rc.d/fsck to get that behaviour though. > > fsck -f is interactive, so you would want to add the -y option to > prevent its hanging waiting for console input. > That is what fsck_y_enable="YES" is for. -- Pawel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?488DE14B.2040103>