From: Christoph Hellwig <hch@infradead.org>
To: dm-devel@redhat.com
Subject: shutting down logical volumes once an underlying device fails?
Date: Wed, 26 Sep 2012 12:11:06 -0400 [thread overview]
Message-ID: <20120926161106.GA12653@infradead.org> (raw)
A coworker has been testing failure scenarious using lvm, and noticed
that when a PV fail a filesystem on a logical volume that spans multiple
PVs only fails once it accesses the actually failed physical device.
At least for system using higher level error detection and replication
behaviour that fails a LV as soon as one of the underlying devices fails
would be much more helpful. Is the current LVM behaviour intention and
should we work around this using userspace monitoring, or would be
patches to introduce a shutdown state similar to what we have in XFS for
example be welcome?
next reply other threads:[~2012-09-26 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 16:11 Christoph Hellwig [this message]
2012-09-26 20:11 ` shutting down logical volumes once an underlying device fails? Mike Snitzer
2012-09-28 13:05 ` Christoph Hellwig
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=20120926161106.GA12653@infradead.org \
--to=hch@infradead.org \
--cc=dm-devel@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).