From: Robin Bowes <robin-lists@robinbowes.com>
To: Maurilio Longo <maurilio.longo@libero.it>
Cc: David Greaves <david@dgreaves.com>,
Guy <bugzilla@watkins-home.com>,
'Neil Brown' <neilb@cse.unsw.edu.au>,
linux-raid@vger.kernel.org, dean-list-linux-raid@arctic.org
Subject: Re: Badstripe proposal (was Re: Bad blocks are killing us!)
Date: Thu, 18 Nov 2004 10:29:05 +0000 [thread overview]
Message-ID: <419C7971.6090902@robinbowes.com> (raw)
In-Reply-To: <419C729D.3E36A473@libero.it>
Maurilio Longo wrote:
> David and others,
>
> I'd like to add that evms ( http://evms.sourceforge.net/ ) already has a
> bad-block management layer, maybe it could be merged inside md to have write
> errors management as well, maybe :)
Good point.
When I set up my RAID (albeit a relatviely non-critical domestic system)
I considered whether or not to use EVMS because of the bad block
relocation feature.
In the end, I went with md, lvm2, and mdadm, primarily as I recall
because at the time EVMS did not support lvm2 and also required
additional kernel patches to support bad block relocation. Plus, there
were issues about having the root filesystem managed by EVMS (it
requires the set up of a custom initrd).
All things considered, I chose the path of least resistance and went
with md/lvm2/mdadm. Perhaps it's time to reconsider that and look at
EVMS again?
R.
--
http://robinbowes.com
next prev parent reply other threads:[~2004-11-18 10:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200411150522.iAF5MNN18341@www.watkins-home.com>
2004-11-15 22:27 ` Bad blocks are killing us! Neil Brown
2004-11-16 16:28 ` Maurilio Longo
2004-11-16 18:18 ` Guy
2004-11-16 23:04 ` Neil Brown
2004-11-16 23:07 ` Guy
2004-11-17 13:21 ` Badstripe proposal (was Re: Bad blocks are killing us!) David Greaves
2004-11-18 9:59 ` Maurilio Longo
2004-11-18 10:29 ` Robin Bowes [this message]
2004-11-19 17:12 ` Jure Pe_ar
2004-11-20 13:15 ` Maurilio Longo
2004-11-21 18:23 ` Jure Pe_ar
2004-11-16 23:29 ` Bad blocks are killing us! dean gaudet
2004-11-17 21:58 ` Bruce Lowekamp
2004-11-18 1:46 ` Guy Watkins
2004-11-18 16:03 ` Bruce Lowekamp
2004-11-19 18:47 ` Dieter Stueken
2004-11-22 8:22 ` Dieter Stueken
2004-11-22 9:17 ` Guy
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=419C7971.6090902@robinbowes.com \
--to=robin-lists@robinbowes.com \
--cc=bugzilla@watkins-home.com \
--cc=david@dgreaves.com \
--cc=dean-list-linux-raid@arctic.org \
--cc=linux-raid@vger.kernel.org \
--cc=maurilio.longo@libero.it \
--cc=neilb@cse.unsw.edu.au \
/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).