Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 07 Sep 2005 13:08:12 -0500
From:      Eric Anderson <anderson@centtech.com>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        questions@freebsd.org, Robert Watson <rwatson@freebsd.org>, Mikhail Teterin <mi+kde@aldan.algebra.com>, fs@freebsd.org
Subject:   Re: Strange case of filesystem corruption?
Message-ID:  <431F2C8C.3010203@centtech.com>
In-Reply-To: <20050907174513.GA32771@xor.obsecurity.org>
References:  <200509051953.22337@aldan> <20050906114055.R51625@fledge.watson.org> <200509060931.33977@aldan> <20050906144512.T75104@fledge.watson.org> <431DB382.7000904@centtech.com> <20050907174513.GA32771@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote:
> On Tue, Sep 06, 2005 at 10:19:30AM -0500, Eric Anderson wrote:
> 
>>Robert Watson wrote:
>>
>>>On Tue, 6 Sep 2005, Mikhail Teterin wrote:
>>>
>>>
>>>>On Tuesday 06 September 2005 06:51 am, Robert Watson wrote:
>>>>= Have you recently experienced a system crash or hard reboot without 
>>>>proper
>>>>= shutdown?
>>>>
>>>>According to dmesg.boot, this filesystem was flagged as "not properly 
>>>>dismounted" back then. The machine's uptime is currently 47 days and 
>>>>no background fskcs are running, of course.
>>>>
>>>>Yours analysis is, likely, correct then... I guess, the fix should be 
>>>>MFCed. (What about 6.0-release?) Thanks!
>>>
>>>
>>>The change was made in HEAD before the 6.x branch, so it's currently in 
>>>RELENG_6.  I fired off an e-mail to Kirk to ask about MFC'ing it to 
>>>RELENG_5, and will do so once I hear back, assuming he thinks there is 
>>>no reason not to.
>>>
>>>Do you have back logs to when bgfsck was running, btw?  Normally it 
>>>should correct this sort of thing, suggestion that bgfsck exited without 
>>>correcting them, which is a little worrying.  You may want to boot to 
>>>single user and fsck manually...
>>
>>I thought that having background_fsck="NO" in your rc.conf would make 
>>the partition get mounted even though it is unclean, and no fsck's would 
>>happen (I use this 'feature' right now, since doing bgfsck on a 2TB 
>>partition takes about 2 hours just to make the snapshot, which means 
>>filesystem activity is suspended for that time).
> 
> 
> AFAIK, no, this just does a regular old fg fsck.

You are absolutely right!  My mistake - I had forgotten I did some other 
hacks to ignore those filesystems (so I can fsck manually)!

Too bad the mksnap_ffs is so slow on large (>20GB) partitions.. :(

Thanks for the correction!
Eric



-- 
------------------------------------------------------------------------
Eric Anderson        Sr. Systems Administrator        Centaur Technology
Anything that works is better than anything that doesn't.
------------------------------------------------------------------------



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?431F2C8C.3010203>