Date: Tue, 30 Oct 2001 21:46:48 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: <julian@elischer.org>, <fs@FreeBSD.ORG> Subject: Re: physical block no -> name of file (FFS)? Message-ID: <20011030213850.U1629-100000@delplex.bde.org> In-Reply-To: <200110300920.f9U9KmD03241@Magelan.Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011030213850.U1629-100000>