From owner-freebsd-fs Tue Oct 30 2:48: 2 2001 Delivered-To: freebsd-fs@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 4F1ED37B406 for ; Tue, 30 Oct 2001 02:47:59 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA07140; Tue, 30 Oct 2001 21:47:47 +1100 Date: Tue, 30 Oct 2001 21:46:48 +1100 (EST) From: Bruce Evans X-X-Sender: To: Alexander Leidinger Cc: , Subject: Re: physical block no -> name of file (FFS)? In-Reply-To: <200110300920.f9U9KmD03241@Magelan.Leidinger.net> Message-ID: <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 Tue, 30 Oct 2001, Alexander Leidinger wrote: > On 29 Okt, Julian Elischer 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. > 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. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message