Re: xfs_repair no modify output

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

Yes.

> 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....

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs


[Index of Archives]     [Linux XFS Devel]     [Linux Filesystem Development]     [Filesystem Testing]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux