[Top] [All Lists]

Re: xfs_repair stops on "traversing filesystem..."

To: xfs@xxxxxxxxxxx
Subject: Re: xfs_repair stops on "traversing filesystem..."
From: Tomek Kruszona <bloodyscarion@xxxxxxxxx>
Date: Sat, 11 Jul 2009 01:44:18 +0200
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=ByU/dnyeL0SBKBcSPon2+LFX0kqiETprVdMpFESm6Ag=; b=EfM6MXPulV32Xb58llej8qxxCPxoMT2g7c9Bs7qGjoI1XA9Nqof83I1pogXhSLcoNU ub2R2wB5RmqBOz34ZbZeHGwrgR2xCyWd4w5x7uEJDaHi/P8xN2EuCIF26HKNOMM04OFj TGokl8c75m7m5iT/6C1f/oCXj2lTyyo9G35wg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=tk+Zgxm+MOZbKVoRomJxEA2j2hUDj9yGiAmpPuV8+fhkee5vv79d0ytLdj62acvcTy NyJ2FKDrJp7bj1DoiYpUiGbQrRT9vt8rgPl1fpk1Gy4/kn8tICsLCQ24hf29+zIJCN9b oq37/tF7F7BwFfYp+nn01AXe6m57kDdFfuSiE=
In-reply-to: <4A57AF5D.6080603@xxxxxxxxxxx>
References: <4A55FAF7.5040908@xxxxxxxxx> <4A56D176.9010702@xxxxxxxxxxx> <4A56ED5F.10400@xxxxxxxxx> <4A57A1C4.40004@xxxxxxxxxxx> <4A57AC69.7070502@xxxxxxxxx> <4A57AF5D.6080603@xxxxxxxxxxx>
User-agent: Mozilla-Thunderbird (X11/20090103)
Eric Sandeen wrote:
> These are all good questions ;)  TBH I'm kind of digging through repair
> in earnest for the first time.  I'm not certain why it got into this
> state, whether there is some underlying bug, perhaps leaving things
> wrongly referenced, or just a plain ol' mis-sizing of the caches.
> I have a patch now that ends like this; if all else fails at least it'd
> not spin forever, and give a hint of what to try.
> -Eric
> ...
> Phase 6 - check inode connectivity...
>         - resetting contents of realtime bitmap and summary inodes
>         - traversing filesystem ...
> unknown magic number 0 for block 8388608 in directory inode 40541
> rebuilding directory inode 40541
> unknown magic number 0 for block 8388608 in directory inode 48934
> rebuilding directory inode 48934
> unknown magic number 0 for block 8388608 in directory inode 56139
> rebuilding directory inode 56139
> unknown magic number 0 for block 8388608 in directory inode 63785
> rebuilding directory inode 63785
> Unable to free any items in cache for new node; exiting.
> Try increasing the bhash and/or ihash size beyond 64
> cache: 0x190ed4d0
> Max supported entries = 512
> Max utilized entries = 512
> Active entries = 512
> Hash table size = 64
> Hits = 130779
> Misses = 271155
> Hit ratio = 32.54

I made some tests and it seems, that filesystem to finish xfs_repair
needs to be repaired with bhash=1024... With default options it still
hangs on "traversing filesystem..." Is it possible to change this
behavior to normal in other way than reformat? Moreover I spotted some
strange thing. 16GB of data has been moved to lost+found. I tried to
clean L+F by
# rm -rf lost+found

but suddenly I got this:

# ls -l /mnt/storage/
ls: cannot access /mnt/storage/lost+found: No such file or directory
total 0
drwxr-xr-x 4 root    root 33 Mar  4 17:21 l_mirror
?????????? ? ?       ?     ?            ? lost+found

I had to run xfs_repair (bhash=1024) once again and then l+f disappeared...

So I started to think: does it have some influence on data that are
stored on this filesystem? I'm afraid that files on this FS may become
inconsistent :/

Best regards,
Tomasz Kruszona

<Prev in Thread] Current Thread [Next in Thread>