From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Greg KH <greg@kroah.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [topic] Richer internal block API
Date: Mon, 02 Jun 2014 13:33:06 -0400 [thread overview]
Message-ID: <yq1tx838be5.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20140601023458.GA5243@kroah.com> (Greg KH's message of "Sat, 31 May 2014 19:34:58 -0700")
>>>>> "Greg" == Greg KH <greg@kroah.com> writes:
>> Perhaps there is something wrong with that approach. Certainly in
>> regards to how to bridge the gap between what we now have for logical
>> volume support, and what we should have, or what BSD has, that
>> approach is demonstrably a perennial failure. After all these years,
>> we still have dm and md as separate islands, no usable snapshotting
>> block device, and roughly zero interaction between filesystems and
>> volume managers.
Greg> People have talked about this for over a very long time.
Lots of talking, indeed. But I think the main problem that there's
nothing (or very little) to see here. Move along :)
Either you let the filesystem explicitly manage RAID and snapshots (like
btrfs) or you let DM or MD do it behind the filesystem's back. What's
the point of introducing a new interface to do something that we already
have?
That doesn't mean that there isn't merit to the "given this cookie, do
you happen to have another copy?" call we have discussed in the past.
Somebody just needs to do it. But I honestly think that btrfs is a much
better approach to that whole thing...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-06-02 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 17:49 Daniel Phillips
2014-05-29 18:13 ` Greg KH
2014-05-29 18:13 ` Daniel Phillips
2014-05-29 18:23 ` Greg KH
2014-05-29 18:43 ` Daniel Phillips
2014-05-29 23:43 ` Greg KH
2014-05-31 22:44 ` Daniel Phillips
2014-06-01 2:34 ` Greg KH
2014-06-02 17:33 ` Martin K. Petersen [this message]
2014-06-02 18:10 ` James Bottomley
2014-06-01 4:31 ` NeilBrown
2014-05-30 9:56 ` Lukáš Czerner
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=yq1tx838be5.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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