xfs
[Top] [All Lists]

Re: Corrupted files

To: Roger Willcocks <roger@xxxxxxxxxxxxxxxx>
Subject: Re: Corrupted files
From: Leslie Rhorer <lrhorer@xxxxxxxxxxxx>
Date: Tue, 09 Sep 2014 20:31:07 -0500
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, Sean Caron <scaron@xxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <3E40936B-A1F2-424D-B0B3-54B6C7B50B13@xxxxxxxxxxxxxxxx>
References: <540F1B01.3020700@xxxxxxxxxxxx> <CAA43vkXwHF9RHW-cbTZ91_vF6wiQ6o_+TQDL3=7kD9P4tErCNQ@xxxxxxxxxxxxxx> <CAA43vkWgh8-EjDXjkySUn+y18W1O+v_W5j+fQankRTgDCmc8tw@xxxxxxxxxxxxxx> <540F7E37.7020500@xxxxxxxxxxx> <540F9FE9.7070500@xxxxxxxxxxxx> <3E40936B-A1F2-424D-B0B3-54B6C7B50B13@xxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
On 9/9/2014 8:10 PM, Roger Willcocks wrote:

On 10 Sep 2014, at 01:48, Leslie Rhorer <lrhorer@xxxxxxxxxxxx> wrote:

  The only ones remaining at issue are 3 files which cannot be read, written or 
deleted.

The most straightforward fix would be to note down the inode numbers of the 
three fies and then use xfs_db to clear the inodes; then run xfs_repair again.

See:

http://xfs.org/index.php/XFS_FAQ#Q:_How_to_get_around_a_bad_inode_repair_is_unable_to_clean_up

That sounds reasonable. If no one has any more sound advice, I think I will try that.


but before that try running the latest (3.2.1 I think) xfs_repair.

I am always reticent to run anything outside the distro package. Ive had problems in the past with doing so. 3.1.7 is pretty close, so unless there is a really solid reason to use 3.2.1 vs. 3.1.7, I think I will stick with the distro version and try the above. Can you or anyone else give a reason why 3.2.1 would work when 3.1.7 would not? More importantly, is there some reason 3.1.7 would make things worse while 3.2.1 would not? If not, then I can always try 3.1.7 and then try 3.2.1 if that does not help.

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