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