From: Nate Carlson <natecars@natecarlson.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] I/O error
Date: Tue, 14 Mar 2006 22:14:27 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.63.0603142213570.16758@tungsten.msp.technicality.org> (raw)
In-Reply-To: <20060314191028.GA25405@percy.comedia.it>
On Tue, 14 Mar 2006, Luca Berra wrote:
> probably because multipath-tools is a cleaner solution?
Hmm.. hadn't run into this one before; looked over the docs.. looks
interesting, and very flexible, but also a heck of a lot more complicated.
:)
------------------------------------------------------------------------
| nate carlson | natecars@natecarlson.com | http://www.natecarlson.com |
| depriving some poor village of its idiot since 1981 |
------------------------------------------------------------------------
prev parent reply other threads:[~2006-03-15 4:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 12:39 [linux-lvm] I/O error German Staltari
2006-03-13 15:57 ` Nate Carlson
2006-03-14 19:10 ` Luca Berra
2006-03-15 4:14 ` Nate Carlson [this message]
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=Pine.LNX.4.63.0603142213570.16758@tungsten.msp.technicality.org \
--to=natecars@natecarlson.com \
--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).