From owner-freebsd-fs Tue Oct 30 5:43:12 2001 Delivered-To: freebsd-fs@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id EE78E37B408 for ; Tue, 30 Oct 2001 05:43:04 -0800 (PST) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout1.freenet.de with esmtp (Exim 3.33 #1) id 15yZAV-0002c0-00; Tue, 30 Oct 2001 14:43:03 +0100 Received: from b821c.pppool.de ([213.7.130.28] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.33 #3) id 15yZAU-0001ic-00; Tue, 30 Oct 2001 14:43:02 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.6/8.11.6) with ESMTP id f9UD0KD05773; Tue, 30 Oct 2001 14:00:21 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200110301300.f9UD0KD05773@Magelan.Leidinger.net> Date: Tue, 30 Oct 2001 14:00:19 +0100 (CET) From: Alexander Leidinger Subject: Re: physical block no -> name of file (FFS)? To: bde@zeta.org.au Cc: julian@elischer.org, fs@FreeBSD.ORG In-Reply-To: <20011030213850.U1629-100000@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 30 Okt, Bruce Evans wrote: >> > you would need to start with 'fsck' and add an option to specify a block >> > to watch for (partiton relative). >> > >> > fsck -n -B NUM >> > could easily return an inode number for you and a filename too given >> > enough hacking... >> >> Yes, but I want to do it on a production system. > > Just back up the files and note which ones can't be read. Better, compare > them with a previous backup. Yes, this solves my problem (now that I know in which partition the bad block is). But doesn't this need more resources than a dedicated program which only traverses the metadata? On a busy system it may be worthwile to have such a program (and I may be willing to write it). >> But thanks for the hint, I haven't thought at looking into fsck, will do >> it later. > > fsck is not very useful for the original problem of finding files with > bad blocks in them, since it only accesses metadata. And the sequence of blocks which holds the content of a given file isn't included in this metadata? fsck_ffs may give me a hint how the physical representation on the disk looks like (if nobody points me to a better documentation). Bye, Alexander. -- Press every key to continue. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message