From: Thomas Schwinge <tschwinge@gnu.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] LVM NOT scary! (was: LVM scary!)
Date: Mon, 3 Apr 2006 08:41:12 -0400 [thread overview]
Message-ID: <20060403124112.GP19029@fencepost> (raw)
In-Reply-To: <443115F0.8030503@watford53.freeserve.co.uk>
On Mon, Apr 03, 2006 at 01:32:48PM +0100, Jim Ford wrote:
> Hmm, there are so many horror stories on this forum that I'm beginning
> to wish that I hadn't chosen the LVM option when I installed my Kubuntu
> system! Mind you, having said that, I never had problems with 5 years of
> software raid on a Slackware box.
Well, it's commonly know that mostly the horror stories are what people
tell each other and remember. And especially in this very place, as it's
main purpose (apart from developing the software further) is to be a
contact point for people encountering such issues.
I'm quite sure that there are (ten- / hundred-)thousands of LVM
installations that just work; like those I did on a number of systems.
> Just though I'd mention it!
Me too.
Regards,
Thomas
P.S. Next project for me: make GRUB2 read LVM volumes. Anyone who wants
to help or has already done something, please speak up now.
next prev parent reply other threads:[~2006-04-03 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 12:32 [linux-lvm] LVM scary! Jim Ford
2006-04-03 12:41 ` Thomas Schwinge [this message]
2006-04-03 12:46 ` [linux-lvm] LVM NOT scary! (was: LVM scary!) Jan-Benedict Glaw
2006-04-03 13:41 ` [linux-lvm] LVM NOT scary! Jim Ford
2006-04-03 13:46 ` Martin Eisenhardt
2006-04-03 13:47 ` Jan-Benedict Glaw
2006-04-03 13:48 ` Andy Smith
2006-04-03 12:58 ` [linux-lvm] LVM NOT scary! (was: LVM scary!) Anil Kumar Sharma
2006-04-03 12:51 ` [linux-lvm] LVM scary! Anil Kumar Sharma
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=20060403124112.GP19029@fencepost \
--to=tschwinge@gnu.org \
--cc=linux-lvm@redhat.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).