xfs
[Top] [All Lists]

Re: crashes with xfs_fsr in 2.6.25-2-amd64 and 2.6.26-1-amd64 (debian) (

To: "Nathaniel W. Turner" <nate@xxxxxxxxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx>
Subject: Re: crashes with xfs_fsr in 2.6.25-2-amd64 and 2.6.26-1-amd64 (debian) (f'up)
From: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: Wed, 29 Apr 2009 12:58:33 -0500
In-reply-to: <49F88E73.7060403@xxxxxxxxxxxxxxx>
References: <20090428032406.GA14234@xxxxxxxxxx> <49F88E73.7060403@xxxxxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nathaniel W. Turner wrote:
> Hi Marc,
>
> Marc Lehmann wrote:
>> It also happens to the same filesystem each time (maybe because
>> it does the heavy I/O),a and it is also the same filesystem where
>> xfs_repair hangs in an endless loop often (but not always). (see
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525880)
>>
>> The filesystem was created a month or so ago using blocksize of 512
>> and
>> lazy-count=1, but I have many of those xfs filesystems.
>>
>> Since this is a production system and I have no backup abilities, I
>> have
>> to no choice but to reformat the disk now.
>>  
> I'm not sure about the root cause of your crash,
The crash is probably due to a bad inode, the file system needs to be
repaired.
> but I just wanted to mention that before you blow away this
> filesystem, you should probably try repairing it with a recent
> version of xfs_repair (like 3.0.0).
> ftp://oss.sgi.com/projects/xfs/cmd_tars/
That is a good suggestion, 2.9.8 is quite old at this point.
xfs_check might also be useful as it might point to the problem inode.
>
> Also, I have seen similar problems to those described in Debian bug
> 525880 with xfs_repair not making progress (although I'm running
> 32-bit), and adding "-P" to the xfs_repair invocation helped in many
> cases.
>
> Cheers,
> nate
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ+JVJNRmM+OaGhBgRAilEAJ9jBvIqlvMtlog0Oyeeb0BPbaMrowCfXmTE
2Pk4UxofSyr1zq6Dfuq8aDk=
=L9qB
-----END PGP SIGNATURE-----

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