From: "Vincent Olivier" <vincent@up4.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Response to Bcachefs Claims
Date: Wed, 26 Aug 2015 15:24:46 -0400 (EDT) [thread overview]
Message-ID: <1440617086.383124909@apps.rackspace.com> (raw)
In-Reply-To: <pan$ac59$d5b01668$cfc6f266$3accc55c@cox.net>
I'm still parsing through the multi-device advices. Will be back on this when I'm done. And I'll probably switch distro to Archlinux which seems the way to go if one is using cutting-edge kernel features like Btrfs.
As for the work on "Gotchas/Known Issues" on the Btrfs wiki, I also think that the best way is to start with the Gotchas page and put a more prominent link for it on the home page.
I would restructure the Gotchas page in the following ways :
* Add the mention "Known Issues" close to the title;
* Only keep current issues/gotchas (current stable kernel, current userspace utilities release), archive every other on a separate page;
* Group by smallest feature encompassing the issue : multi-device, quotas, subvolumes, compression, conversion from extX, interactions with other things like LVM, MD, encryption, etc.;
* Something that is "new" and not as thoroughly tested as other features should be listed there as well (I think) until there is a consensus (to be defined) on it being reliable enough to be taken out of the list. Or maybe that should go on another page ?
* Provide links to HOWTOs or best practices for the features discussed (multi-device GOTCHAS should link to multi-device HOWTO).
I will be thinking about it more before doing anything and still welcoming ideas.
Thanks !
Vincent
next prev parent reply other threads:[~2015-08-26 19:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 15:22 Response to Bcachefs Claims Vincent Olivier
2015-08-25 15:53 ` Austin S Hemmelgarn
2015-08-25 23:17 ` Suman Chakravartula
2015-08-25 16:13 ` Roman Mamedov
2015-08-25 17:55 ` Austin S Hemmelgarn
2015-08-25 16:27 ` Chris Mason
2015-08-25 16:39 ` Chris Murphy
2015-08-25 17:59 ` Austin S Hemmelgarn
2015-08-25 19:58 ` Chris Murphy
2015-08-26 1:17 ` Duncan
2015-08-26 19:24 ` Vincent Olivier [this message]
2015-08-29 11:17 ` David Sterba
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=1440617086.383124909@apps.rackspace.com \
--to=vincent@up4.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.