Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g08Fb1M08303 for linux-xfs-outgoing; Tue, 8 Jan 2002 07:37:01 -0800 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g08Faqg08276 for ; Tue, 8 Jan 2002 07:36:53 -0800 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id PAA1444677 for ; Tue, 8 Jan 2002 15:34:45 +0100 (CET) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy-e185.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA4033145; Tue, 8 Jan 2002 08:35:32 -0600 (CST) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA96390; Tue, 8 Jan 2002 08:35:31 -0600 (CST) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id g08EYio25209; Tue, 8 Jan 2002 08:34:44 -0600 Subject: Re: "No such file or directory" (still) (was Re: file corruption during emacs build on XFS logical volume From: Steve Lord To: "Ralf G. R. Bergs" Cc: Linux XFS , Eric Sandeen In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.0.99+cvs.2001.12.18.08.57 (Preview Release) Date: 08 Jan 2002 08:34:44 -0600 Message-Id: <1010500484.15632.27.camel@jen.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Status: O Content-Length: 1099 Lines: 37 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! > > 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? It does indeed look like a similar problem to the repair output. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com