From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs@vger.kernel.org
Subject: some project ideas: NFS4 ACLs, resilience on the same device, allowing to specify which devices are "distinct" in a RAID
Date: Mon, 02 Jun 2014 19:44:16 +0200 [thread overview]
Message-ID: <1401731056.4904.9.camel@heisenberg.scientia.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]
Hi.
Christian Kujau suggested in the wiki[] to post project ideas to the
list to give them some possible wider discussion.
So far I've had these ideas:
1) NFS 4 ACLs[1]
Not sure whether it has been proposed and/or rejected before),... but it
would be nice if it was a goal for btrfs to support NFS4 ACLs.
These are much more powerful than POSIX.1e ACLs... and I think it would
be nice if all the major Linux filesystems would support them in
addition or as an alternative to the POSIX.1e ACLs. Of course one would
have to think about a schema what happens when there are ACLs of both
types in place for a file, whether this is allowed at all or not and how
rules would be merged.
2) DUP of data
I think btrfs already supports to have the same blocks copied on
multiple locations on the same device for resilience,... but only for
meta-data...
I think ZFS supports that for data as well...
Advanced code could try to spread such replicas as far as possible (i.e.
different spindles on rotating drives, ... different chips on flash
based storage)
3) allow to tell btrfs which devices are really distinct in a RAID
For some reasons people may have setups e.g. like this:
/dev/sda1
/dev/sda2
/dev/sdb1
/dev/sdc1
Now one could create a RAID5 on them, but apparently sda1 and sda2 are
on the same disk... so I'd like a way to tell btrfs that these are the
"same" and not really that redundant.
Cheers,
Chris.
[0] https://btrfs.wiki.kernel.org/index.php?title=Talk%3AProject_ideas&action=historysubmit&diff=26841&oldid=26831
[1] https://btrfs.wiki.kernel.org/index.php/Talk:Project_ideas#NFS4_ACLS
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5165 bytes --]
next reply other threads:[~2014-06-02 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 17:44 Christoph Anton Mitterer [this message]
2014-06-03 17:03 ` some project ideas: NFS4 ACLs, resilience on the same device, allowing to specify which devices are "distinct" in a RAID Goffredo Baroncelli
2014-06-07 1:34 ` Christoph Anton Mitterer
2014-06-07 8:25 ` Goffredo Baroncelli
2014-06-14 2:40 ` Christoph Anton Mitterer
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=1401731056.4904.9.camel@heisenberg.scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).