[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] Re: How to handle Bad Block relocation with LVM?



On Mon, 2003-02-14 at 17:26, Joe Thornber <joe fib011235813 fsnet co uk> wrote:
> Eric,
> 
> We would like to automate the process that you have described in LVM2
> at some point.  So if you get an error on an LV and new PE will be
> allocated, as much data as possible copied from the bad PE to the new
> PE, and then remap the LV so that it's using the new PE (very much
> like a small pvmove).
> 
> The EVMS team are writing a bad block relocator target for device
> mapper, but I don't feel it's neccessary to add yet another device
> layer to the LVs.  If I have a bad block I don't mind loosing a whole
> PE (people may not agree with me on this ?)

I actually quite agree.  Here are a few points:

o A PE is typically less than 0.01% of my total disk space.

o Corruption on a drive tends to spread, especially if sectors near the
corruption are accessed frequently, so it's best to avoid a whole
section of a drive around a bad spot.

o In general, I would want to throw away a drive that had so many bad
sectors that it's firmware relocation software could no longer handle
them.  So, my main purpose in relocating the PE is to recover as much
data from it as I can before junking the drive.

Have fun (if at all possible),
-- 
The best we can hope for concerning the people at large is that they
be properly armed.  -- Alexander Hamilton
-- Eric Hopper (hopper omnifarious org  http://www.omnifarious.org/~hopper) --

Attachment: signature.asc
Description: This is a digitally signed message part


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]