linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] badblocks handling with LVM
Date: Thu, 26 Apr 2001 10:06:03 +0000	[thread overview]
Message-ID: <20010426100603.A9820@sistina.com> (raw)
In-Reply-To: <01042519594802.31687@lyta>; from russell@coker.com.au on Wed, Apr 25, 2001 at 07:59:48PM +0200

On Wed, Apr 25, 2001 at 07:59:48PM +0200, Russell Coker wrote:
> On Monday 23 April 2001 12:08, Andreas Dilger wrote:
> > Laurent writes:
> > > I have blocks marked bad on a ext2 filesystem.  The device has bad
> > > blocks. I'm wondering how bad blocks are handled with lvm.  I would like
> > > to create a phycal volume on this device and use reiserfs on it.
> > > Could you give me some informations ?
> >
> > As long as the bad blocks are not in the first ~250kB of the partition/disk
> > then LVM doesn't care about it.  However, reiserfs doesn't yet support bad
> > blocks in the filesystem (this is currently under development AFAIK), so
> > this will not help you.
> 
> 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.

> 
> -- 
> http://www.coker.com.au/bonnie++/     Bonnie++ hard drive benchmark
> http://www.coker.com.au/postal/       Postal SMTP/POP benchmark
> http://www.coker.com.au/projects.html Projects I am working on
> http://www.coker.com.au/~russell/     My home page
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-04-26 10:06 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 [this message]
2001-04-26 13:26       ` Ragnar Kjørstad
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=20010426100603.A9820@sistina.com \
    --to=mauelshagen@sistina.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).