From owner-freebsd-fs  Sun Nov 19  5:37:18 2000
Delivered-To: freebsd-fs@freebsd.org
Received: from mail.interware.hu (mail.interware.hu [195.70.32.130])
	by hub.freebsd.org (Postfix) with ESMTP id 19A4B37B479
	for <fs@freebsd.org>; Sun, 19 Nov 2000 05:37:16 -0800 (PST)
Received: from kinshasa-37.budapest.interware.hu ([195.70.51.165] helo=elischer.org)
	by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian))
	id 13xUef-0005KW-00; Sun, 19 Nov 2000 14:37:13 +0100
Message-ID: <3A17D787.68A9E27C@elischer.org>
Date: Sun, 19 Nov 2000 05:37:11 -0800
From: Julian Elischer <julian@elischer.org>
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en, hu
MIME-Version: 1.0
To: dwalton@acm.org
Cc: fs@freebsd.org
Subject: Re: corrupted filesystem
References: <3A174EA5.24115.102AB11@localhost>
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Dave Walton wrote:
> 
> On 19 Nov 2000, at 0:59, Julian Elischer wrote:
> 
> > probably. Soft updates would have limitted he damage to files
> > created/extended in the last 30 seconds.
> 
> Note to self:  Remember to turn on softupdates.
> 
> > Dave Walton wrote:
> > > ------------------------------------------------------------
> > > fsdb (inum: 2)> ls
> > > slot 16 ino 3039518 reclen 16: directory, `home'
> > > fsdb (inum: 2)> cd home
> > > component `home': current inode: regular file
> > > ------------------------------------------------------------
> > >
> > > Ok, now I'm really confused!  First fsdb reports home as a
> > > directory, but when I cd into it, it becomes a regular file?  How can
> > > that be?
> >
> > no, it is still a regular file..
> > 'cd' in fsdb just makes it the 'current' inode.
> 
> I understand that.  But if you look at the short excerpt from fsdb
> above, it specifically says "directory" when I do ls.  But after I cd to
> it, fsdb says "regular file".  Quite a contradiction.


there is a file/dir bit in the directory  as well
obviously they disagree..

hopefully if you can run fsck -y you can find the inodes of the 
user's individual directories when they are put in lost+found 


> 
> > It's possible that the real inode is floating around somewhere,
> > 'unattached'.
> > or maybe the 'data' is correct but the inode is wrong.
> 
> Either way, any tips for tracking down the real contents of home?
> 
> > can you 'ls' it?
> 
> Nope.  It seems to act just like a normal file, except when I do an
> ls on it's parent in fsdb.
> 
> Dave
> 
> ----------------------------------------------------------------------
> Dave Walton                                            dwalton@acm.org
> ----------------------------------------------------------------------

-- 
      __--_|\  Julian Elischer
     /       \ julian@elischer.org
    (   OZ    ) World tour 2000
---> X_.---._/  presently in:  Budapest
            v


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message