[Top] [All Lists]

Re: xfs_repair no modify output

To: "jamie@xxxxxxxxxxxx" <jamie@xxxxxxxxxxxx>
Subject: Re: xfs_repair no modify output
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Tue, 31 Jul 2012 08:07:59 +1000
Cc: xfs@xxxxxxxxxxx
In-reply-to: <769346391.171271.1343664034505.JavaMail.open-xchange@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <769346391.171271.1343664034505.JavaMail.open-xchange@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Mon, Jul 30, 2012 at 06:00:34PM +0200, jamie@xxxxxxxxxxxx wrote:
> Hi List,
> Sorry for the stupid question, just wanted a quick clarification on the
> following excerpts from an xfs_repair no modify.
> # xfs_repair -nv /dev/sdc1
> entry "YYYY" in dir 4294967424 points to an already connected directory inode 
> 145
>         would clear entry "YYYY"
> disconnected dir inode 4294967424, would move to lost+found
> Does this in effect mean that the file YYYY will end up and lost+found


> and
> directory (and its contents) will end up in lost+found.

Assuming you mean directory entry XXXX, no.

> Namely easy enough to move back. Or will the contents of XXXX be lost?

XXXX was an invalid directory entry. It got removed from the
directory, and the directory is otherwise unmodified. FWIW, it was
on inode 128, so it's probably an entry in the root directory....


Dave Chinner

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