xfs
[Top] [All Lists]

Re: Corrupted files

To: Leslie Rhorer <lrhorer@xxxxxxxxxxxx>
Subject: Re: Corrupted files
From: Roger Willcocks <roger@xxxxxxxxxxxxxxxx>
Date: Wed, 10 Sep 2014 02:10:47 +0100
Cc: Roger Willcocks <roger@xxxxxxxxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>, Sean Caron <scaron@xxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <540F9FE9.7070500@xxxxxxxxxxxx>
References: <540F1B01.3020700@xxxxxxxxxxxx> <CAA43vkXwHF9RHW-cbTZ91_vF6wiQ6o_+TQDL3=7kD9P4tErCNQ@xxxxxxxxxxxxxx> <CAA43vkWgh8-EjDXjkySUn+y18W1O+v_W5j+fQankRTgDCmc8tw@xxxxxxxxxxxxxx> <540F7E37.7020500@xxxxxxxxxxx> <540F9FE9.7070500@xxxxxxxxxxxx>
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

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

--
Roger

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