From: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] badblocks handling with LVM
Date: Thu, 26 Apr 2001 15:26:52 +0200 [thread overview]
Message-ID: <20010426152651.B26041@vestdata.no> (raw)
In-Reply-To: <20010426100603.A9820@sistina.com>; from Heinz J. Mauelshagen on Thu, Apr 26, 2001 at 10:06:03AM +0000
On Thu, Apr 26, 2001 at 10:06:03AM +0000, Heinz J. Mauelshagen wrote:
> > The problem is that when you move LV's around and make snapshots the bad
> > blocks on the underlieing media will move. Therefore I think that management
> > of bad blocks possibly should be done in the LVM.
> >
> > Or should we just assume that LVM runs over RAID arrays of ATA/SCSI disks
> > that have sector-sparing so that bad blocks are not an issue?
>
> That's what I recommend because disks typically "hide" bad sectors to a certain
> degree using bad block relocation et al.
> If the given disk capacity for this is not enough because too many bad blocks
> occured already then you are in serious trouble and need to repleace
> your disk (subsystem) anyway IMO.
And if anyone insist on using LVM to mark the blocks anyway, it can be
done with out special code. Just create a volume named "broken", and put
the PVs in question in this.
--
Ragnar Kj�rstad
Big Storage
next prev parent reply other threads:[~2001-04-26 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 5:19 [linux-lvm] badblocks handling with LVM laurent
2001-04-23 10:08 ` Andreas Dilger
2001-04-25 17:59 ` Russell Coker
2001-04-26 10:06 ` Heinz J. Mauelshagen
2001-04-26 13:26 ` Ragnar Kjørstad [this message]
2001-04-26 14:27 ` Goetz Bock
2001-04-26 14:36 ` Ragnar Kjørstad
2001-04-26 17:11 ` Heinz J. Mauelshagen
2001-04-27 23:59 ` Andreas Dilger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010426152651.B26041@vestdata.no \
--to=lvm@ragnark.vestdata.no \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.