xfs
[Top] [All Lists]

Re: "No such file or directory" (still) (was Re: file corruption during

To: "Steve Lord" <lord@xxxxxxx>
Subject: Re: "No such file or directory" (still) (was Re: file corruption during emacs build on XFS logical volume
From: "Ralf G. R. Bergs" <rabe@xxxxxxxxxxxxxx>
Date: Tue, 08 Jan 2002 15:49:01 +0100
Cc: "Linux XFS" <linux-xfs@xxxxxxxxxxx>
In-reply-to: <1010500484.15632.27.camel@xxxxxxxxxxxxxxxxxxxx>
Reply-to: "Ralf G. R. Bergs" <rabe@xxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
On 08 Jan 2002 08:34:44 -0600, Steve Lord wrote:

>On Tue, 2002-01-08 at 08:17, Ralf G. R. Bergs wrote:
>> 
>> Unfortunately I don't know ANYTHING about the structure of an XFS 
filesystem. 
>> Suppose I have the complete path of a "broken" file (that gives me the "No 
>> such file or directory" warning,) could you direct me how to use xfs_db to 
>> further narrow down the problem? I've tried understanding the xfs_db 
manpage 
>> but as a layman in XFS structure basics I failed miserably.
>
>I have a hard time understanding xfs_db!

Well, if even YOU have problems with this... :-)

>> I've played around with xfs_db a little bit, and received the following 
>> output:
>> 
>> xfs_db: blockget -n
>> dir 1426370585 block 8388614 extra leaf entry 62b7eea7 2a89
>> dir ino 1426370585 missing leaf entry for 62bdaea7/2a89
>> user quota id 232, have/exp bc 0/1 ic 0/1
>> user quota id 1000, have/exp bc 2521011/2521010 ic 19036/19035
>
>Can you try the
>inode 1426370585
>p
>
>sequence on this fs?

Sure, here you are:

Fileserver:~# xfs_db /dev/sdc5
xfs_db: inode 1426370585
xfs_db: p
core.magic = 0x494e
core.mode = 040775
core.version = 1
core.format = 3 (btree)
core.nlinkv1 = 2
core.uid = 0
core.gid = 71
core.atime.sec = Tue Jan  8 14:40:01 2002
core.atime.nsec = 824812000
core.mtime.sec = Fri Dec 10 12:02:02 1999
core.mtime.nsec = 000000000
core.ctime.sec = Mon Jan  7 21:20:13 2002
core.ctime.nsec = 832196000
core.size = 98304
core.nblocks = 38
core.extsize = 0
core.nextents = 29
core.naextents = 0
core.forkoff = 0
core.aformat = 2 (extents)
core.dmevmask = 0
core.dmstate = 0
core.newrtbm = 0
core.prealloc = 0
core.realtime = 0
core.gen = 0
next_unlinked = null
u.bmbt.level = 1
u.bmbt.numrecs = 1
u.bmbt.keys[1] = [startoff] 1:[0]
u.bmbt.ptrs[1] = 1:89149111

xfs_db: ncheck -i 1426370585
 1426370585 daten/[snip]/iGD_8/.

This is in fact the directory in which the "damaged" file resides (or is 
supposed to reside)!!

>It does indeed look like a similar problem to the repair output.

I sure hope so -- because I'm getting the same error message!

Thanks,

Ralf


-- 
Verkaufe Original-BMW-Raeder:                    L I N U X       .~.
http://adsl-bergs.rz.rwth-aachen.de/~rabe       The  Choice      /V\
                                                 of a  GNU      /( )\
                                                Generation      ^^-^^



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