From: Lars Marowsky-Bree <lmb@suse.de>
To: Neil Brown <neilb@cse.unsw.edu.au>, Daniel Gryniewicz <dang@fprintf.net>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: [RFCI] How best to partition MD/raid devices in 2.6
Date: Fri, 14 Nov 2003 11:16:47 +0100 [thread overview]
Message-ID: <20031114101647.GJ32211@marowsky-bree.de> (raw)
In-Reply-To: <16308.26754.867801.131463@notabene.cse.unsw.edu.au>
On 2003-11-14T16:30:42,
Neil Brown <neilb@cse.unsw.edu.au> said:
> There are issues with the raid superblock but assuming they can be
> solved, I want partitioning to work easily.
>
> Can LVM work happily with 'legacy' partitioning information?
I'd really suggest to run DM (either LVM2 or EVMS2) on top of md
instead. It's much more flexible; I don't see any benefit in 'old style'
partition information, which has all sorts of problems - ie,
non-transactional updates (_why_ were you running raid again? ;), static
as they can't be modified during runtime etc.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering \ ever tried. ever failed. no matter.
SUSE Labs | try again. fail again. fail better.
Research & Development, SUSE LINUX AG \ -- Samuel Beckett
next prev parent reply other threads:[~2003-11-14 10:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 3:11 [RFCI] How best to partition MD/raid devices in 2.6 Neil Brown
2003-11-14 5:09 ` viro
2003-11-14 5:32 ` Neil Brown
2003-11-14 5:21 ` Daniel Gryniewicz
2003-11-14 5:30 ` Neil Brown
2003-11-14 10:16 ` Lars Marowsky-Bree [this message]
2003-11-14 18:29 ` Jeff Garzik
2003-11-14 21:44 ` Matt Domsch
2003-11-14 22:45 ` viro
2003-11-17 0:46 ` Automatic Write Reallocation Enable, question? Guy
2003-11-17 0:46 ` Guy
2003-11-14 5:27 ` [RFCI] How best to partition MD/raid devices in 2.6 Daniel Pittman
2003-11-14 6:10 ` viro
2003-11-14 7:39 ` Luca Berra
2003-11-14 8:04 ` Paul Jakma
2003-11-14 8:04 ` Paul Jakma
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=20031114101647.GJ32211@marowsky-bree.de \
--to=lmb@suse.de \
--cc=dang@fprintf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--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 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.