Date: Sun, 19 Nov 2000 03:53:09 -0800 From: "Dave Walton" <dwalton@acm.org> To: Julian Elischer <julian@elischer.org> Cc: fs@freebsd.org Subject: Re: corrupted filesystem Message-ID: <3A174EA5.24115.102AB11@localhost> In-Reply-To: <3A179656.CA555A2B@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > 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 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A174EA5.24115.102AB11>