From: Christoph Hellwig <hch@infradead.org>
To: device-mapper development <dm-devel@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>
Subject: Re: shutting down logical volumes once an underlying device fails?
Date: Fri, 28 Sep 2012 09:05:05 -0400 [thread overview]
Message-ID: <20120928130505.GA16549@infradead.org> (raw)
In-Reply-To: <20120926201116.GD7882@redhat.com>
On Wed, Sep 26, 2012 at 04:11:17PM -0400, Mike Snitzer wrote:
>
> Don't think any shutdown should be initiated by the kernel.
>
> But events that userspace could respond to by deactivating (an
> arbitrarily complex) lvm device would be the way forward IMHO.
Deactivating is maybe a bit of a too strong word. But I'd expect we'll
get EIO from al sectors not just those on the failed device.
> Could this tie back to needing better UA handling/notification between
> kernel<->userspace?
That current proposed solution we have internally is to simply poll
the status output for the PVs and handle it all in userspace. To me
this seems a bit clumsy, but at least it's easily doable in short time.
prev parent reply other threads:[~2012-09-28 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 16:11 shutting down logical volumes once an underlying device fails? Christoph Hellwig
2012-09-26 20:11 ` Mike Snitzer
2012-09-28 13:05 ` Christoph Hellwig [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=20120928130505.GA16549@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).