Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Feb 2006 12:08:08 -0700 (MST)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        bakul@bitblocks.com
Cc:        hackers@freebsd.org
Subject:   Re: Bad block -> file mapping 
Message-ID:  <20060218.120808.73002804.imp@bsdimp.com>
In-Reply-To: <200602181902.k1IJ243D041278@gate.bitblocks.com>
References:  <20060218.104749.104696960.imp@bsdimp.com> <200602181902.k1IJ243D041278@gate.bitblocks.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200602181902.k1IJ243D041278@gate.bitblocks.com>
            Bakul Shah <bakul@bitblocks.com> writes:
: >                                     However, I'd kinda like to know
: > which file that is.  If it is a boring file (foo.o, say), I'd dd the
: > bad block with 0's and then remove it.  If it is a non-boring file,
: > I'd try to recover it a couple of times, etc.
: 
: So you want a function that does this?
: 
:     LBA -> slice/partition/offset -> fs/inode -> list of file names
: 
: Logic for the second step should be in fsck.

Yea.  I was kinda hoping to find a tool that would do that given the
LBA of the disk...  I can do the math by hand, but if I don't have
to...

: I haven't kept uptodate on disk stds so likely I am talking
: through my hat but in ST506 there used to be a diagnostic
: read function that returned the bad block and its CRC.  That
: allows at least a chance of a manual correction.
: 
: > Once I have the file in BAD, I'd planned on overwriting it with 0's
: > and then removing it if I could read the block again.
: 
: Why do you care?

I want to know what file I'm trashing, explicitly.  I could just do
the dd trick to the raw block, but then I'd have a divot left in the
file that I have no clue is there...

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060218.120808.73002804.imp>