Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 02 Mar 2006 23:39:45 -0500
From:      Yarema <yds@CoolRat.org>
To:        Robert Watson <rwatson@FreeBSD.org>
Cc:        David Rhodus <drhodus@machdep.com>, Pawel Jakub Dawidek <pjd@freebsd.org>, Dennis Koegel <amf@hobbit.neveragain.de>, FreeBSD-current@freebsd.org, Martin Machacek <m@m3a.net>, Kris Kennaway <kris@obsecurity.org>, Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>, FreeBSD-gnats-submit@freebsd.org
Subject:   Re: kern/93942: panic: ufs_dirbad: bad dir
Message-ID:  <952927C621848163A912B270@ramen.coolrat.org>
In-Reply-To: <20060303034932.V58513@fledge.watson.org>
References:  <courier.44046DC8.000006A2@CoolRat.org> <20060228195343.GA85313@xor.obsecurity.org> <3BD79FAD83E2122EC1644386@ramen.coolrat.org> <fe77c96b0603011210w439e1d11xb82e3498c1846e65@mail.gmail.com> <20060301201937.GA29208@xor.obsecurity.org> <A4A304ECE051757AD5D2E7C0@ramen.coolrat.org> <20060303034932.V58513@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--On March 3, 2006 3:51:45 AM +0000 Robert Watson <rwatson@FreeBSD.org> 
wrote:

>
> On Thu, 2 Mar 2006, Yarema wrote:
>
>> options	UFS_EXTATTR
>> options	UFS_EXTATTR_AUTOSTART
>
> If you disable just UFS_EXTATTR_AUTOSTART, does the panic go away?  The
> autostart routine relies on reading directory data (or at least,
> performing lookups) during the mount process.  While it shouldn't be
> running on UFS2, it could be that it is, and if something has changed in
> the mount process so that reading directories that early is no longer
> functional, it could be that this causes an incorrect reporting of
> on-disk corruption (i.e., it could be a data structure initialization
> problem or the like).
>
> Robert N M Watson

Damn, I just reformatted the corrupt partition so I can no longer try this. 
But as per Dmitry's suggestion before newfs wiped it all I did a:

mount -r /home
cat /home > /tmp/ar0s1e.ino2
umount /home
mount -r /dev/twed0s1e /home
cat /home > /tmp/twed0s1e.ino2
umount /home

Where ar0s1e is the corrupt slice and the dir is 17408 bytes in size and 
there seems to be a huge chunk of mostly null data following the entry for 
lost+found.  twed0s1e is where I backed up the /home fs and the dir in a 
more reasonable 1024 bytes in size.  Both files can be found at 
<http://yds.CoolRat.org/freebsd/>; along with an archive of my KERNCONF 
files containing a short README explaining how I manage my KERNCONFs.

-- 
Yarema



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