From: David Greaves <david@dgreaves.com>
To: david@lang.hm
Cc: Paul Clements <paul.clements@steeleye.com>,
Jan Engelhardt <jengelh@computergmbh.de>,
Al Boldi <a1426z@gawab.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
netdev@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: [RFD] Layering: Use-Case Composers (was: DRBD - what is it, anyways? [compare with e.g. NBD + MD raid])
Date: Mon, 13 Aug 2007 13:43:55 +0100 [thread overview]
Message-ID: <46C0520B.20804@dgreaves.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708130127260.22470@asgard.lang.hm>
david@lang.hm wrote:
>> Would this just be relevant to network devices or would it improve
>> support for jostled usb and sata hot-plugging I wonder?
>
> good question, I suspect that some of the error handling would be
> similar (for devices that are unreachable not haning the system for
> example), but a lot of the rest would be different (do you really want
> to try to auto-resync to a drive that you _think_ just reappeared,
Well, omit 'think' and the answer may be "yes". A lot of systems are quite
simple and RAID is common on the desktop now. If jostled USB fits into this
category - then "yes".
> what
> if it's a different drive? how can you be sure?
And that's the key isn't it. We have the RAID device UUID and the superblock
info. Isn't that enough? If not then given the work involved an extended
superblock wouldn't be unreasonable.
And I suspect the capability of devices would need recording in the superblock
too? eg 'retry-on-fail'
I can see how md would fail a device but may now periodically retry it. If a
retry shows that it's back then it would validate it (UUID) and then resync it.
> ) the error rate of a
> network is gong to be significantly higher then for USB or SATA drives
> (although I suppose iscsi would be limilar)
I do agree - I was looking for value-add for the existing subsystem. If this
benefits existing RAID users then it's more likely to be attractive.
David
next prev parent reply other threads:[~2007-08-13 12:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 10:35 [RFD] Layering: Use-Case Composers (was: DRBD - what is it, anyways? [compare with e.g. NBD + MD raid]) Al Boldi
2007-08-12 11:28 ` Jan Engelhardt
2007-08-12 16:39 ` david
2007-08-12 17:03 ` Jan Engelhardt
2007-08-12 17:45 ` Iustin Pop
2007-08-13 1:41 ` Paul Clements
2007-08-13 3:21 ` david
2007-08-13 8:03 ` David Greaves
2007-08-13 8:31 ` david
2007-08-13 12:43 ` David Greaves [this message]
2007-08-13 9:02 ` Jan Engelhardt
2007-08-13 7:51 ` David Greaves
2007-08-12 11:51 ` Evgeniy Polyakov
2007-08-12 15:28 ` Al Boldi
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=46C0520B.20804@dgreaves.com \
--to=david@dgreaves.com \
--cc=a1426z@gawab.com \
--cc=david@lang.hm \
--cc=jengelh@computergmbh.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.clements@steeleye.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).