Date: Thu, 14 May 2009 16:02:45 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Andrew Snow <andrew@modulus.org> Cc: Pat Wendorf <dungeons@gmail.com>, freebsd-stable@freebsd.org Subject: Re: File system corruption Message-ID: <4A0C1675.4090609@icyb.net.ua> In-Reply-To: <4A0B31A2.9030805@modulus.org> References: <2c2c47aa0905121110i6355930bwce3a9c6afb117d4d@mail.gmail.com> <200905131124.16897.milu@dat.pl> <2c2c47aa0905131337w4a338386t2407f7df7a398cf7@mail.gmail.com> <4A0B31A2.9030805@modulus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 13/05/2009 23:46 Andrew Snow said the following: > Pat Wendorf wrote: >> I spoke too soon I guess: A buddy of mine at the hosting provider took >> down >> the box and did a fsck -y on the var partition, this seems to have >> cleaned >> it up. It looks like the regular fsck -p could not repair it. > > > You may like to put fsck_y_enable="YES" in your /etc/rc.conf, though > this does not affect the root volume. This would make fsck -y run on all filesystems (clean, just checked, always ro, etc) iff fsck -p fails. This can be dangerous too if filesystem state is such that fsck gets confused. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A0C1675.4090609>