From owner-freebsd-fs Sun Nov 19 16:28:45 2000 Delivered-To: freebsd-fs@freebsd.org Received: from modgud.nordicrecords.com (h21-168-107.nordicdms.com [207.21.168.107]) by hub.freebsd.org (Postfix) with SMTP id 1379137B479 for ; Sun, 19 Nov 2000 16:28:43 -0800 (PST) Received: (qmail 9663 invoked by alias); 20 Nov 2000 00:28:39 -0000 Received: (qmail 9649 invoked from network); 20 Nov 2000 00:28:38 -0000 Received: from adsl-216-103-90-137.dsl.snfc21.pacbell.net (HELO thinkpad770z) (216.103.90.137) by mail.nordicrecords.com with SMTP; 20 Nov 2000 00:28:38 -0000 From: "Dave Walton" To: Julian Elischer , fs@freebsd.org Date: Sun, 19 Nov 2000 16:28:25 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: corrupted filesystem Reply-To: dwalton@acm.org Message-ID: <3A17FFA9.30580.3B5C5FD@localhost> In-reply-to: <3A17D787.68A9E27C@elischer.org> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 19 Nov 2000, at 5:37, Julian Elischer wrote: > there is a file/dir bit in the directory as well > obviously they disagree.. Ah. Now it makes sense. > 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 Isn't it possible for fsck -y to cause more damage while it tries to repair things? Thanks, Dave ---------------------------------------------------------------------- Dave Walton dwalton@acm.org ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message