From owner-freebsd-current Fri Jan 28 8:22:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 08FE814E19 for ; Fri, 28 Jan 2000 08:22:52 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id IAA81548; Fri, 28 Jan 2000 08:22:33 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001281622.IAA81548@gndrsh.dnsmgr.net> Subject: Re: very silent, but heavy filesystem-crash In-Reply-To: <20000128171618.C1305@cage.tse-online.de> from Andreas Braukmann at "Jan 28, 2000 05:16:18 pm" To: braukmann@tse-online.de (Andreas Braukmann) Date: Fri, 28 Jan 2000 08:22:32 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... > > Starting an 'fsck' results in: > > cage:[/] # fsck /scratch > ** /dev/da1s1g > ** Last Mounted on /scratch > ** Phase 1 - Check Blocks and Sizes > PARTIALLY TRUNCATED INODE I=16 > SALVAGE? [yn] ^C > ***** FILE SYSTEM MARKED DIRTY ***** Next step is run the ``save'' fsck: fsck -n /scratch >/someplacewithspace 2>&1 Then take a look at the logfile and see just how many more errors it would have found had you let it procede... > I interrupted the fsck-run as soon as I decided that it might be > advisable to leave it in its hosed state just for the case that > there is some illuminated filesystem-hacker who would like to > take a peek. (I would allow ssh-access to the box ...) $1.00/MB for me to recover it.... if you need it. I don't do it for fun. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message