linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: linux-lvm@sistina.com, Andreas Dilger <adilger@turbolinux.com>
Subject: Re: [linux-lvm] badblocks handling with LVM
Date: Wed, 25 Apr 2001 19:59:48 +0200	[thread overview]
Message-ID: <01042519594802.31687@lyta> (raw)
In-Reply-To: <200104231008.f3NA8Gkx001134@webber.adilger.int>

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?

-- 
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

  reply	other threads:[~2001-04-25 17:59 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 [this message]
2001-04-26 10:06     ` Heinz J. Mauelshagen
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=01042519594802.31687@lyta \
    --to=russell@coker.com.au \
    --cc=adilger@turbolinux.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).