From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Add "barrier" option to support "-o remount,barrier"
Date: Fri, 03 Jan 2014 08:43:54 +0800 [thread overview]
Message-ID: <52C607CA.6000105@cn.fujitsu.com> (raw)
In-Reply-To: <20140102154103.GL6498@twin.jikos.cz>
On Thu, 2 Jan 2014 16:41:03 +0100, David Sterba wrote:
> On Thu, Dec 26, 2013 at 02:45:10PM +0800, Qu Wenruo wrote:
>> Btrfs can be remounted without barrier, but there is no "barrier" option
>> so nobody can remount btrfs back with barrier on. Only umount and
>> mount again can re-enable barrier.(Quite awkward)
> Ok for adding the mount option.
>
>> Reported-by: Daniel Blueman <daniel@quora.org>
>> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
>> ---
>> Documentation/filesystems/btrfs.txt | 6 ++++++
>> fs/btrfs/super.c | 8 +++++++-
>> 2 files changed, 13 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/filesystems/btrfs.txt b/Documentation/filesystems/btrfs.txt
>> index 5dd282d..f6f71d6 100644
>> --- a/Documentation/filesystems/btrfs.txt
>> +++ b/Documentation/filesystems/btrfs.txt
>> @@ -51,6 +51,12 @@ Unless otherwise specified, all options default to off.
>> defrag process. Works best for small files; Not well suited for
>> large database workloads.
>>
>> + barrier
>> + Enable the use of block layer write barriers. Write barriers ensure
>> + that certain IOs make it through the device cache and are on persistent
>> + storage.
>> + Barriers are enabled by default.
> There's the 'nobarrier' option already, I think it's better to keep the
> pairing option documentation at one place and mark the default one with (*).
>
> Related to that, there should imho be a pairing option for every mount
> option where it makes sense, so all the combinations work through
> remount.
>
> The defaults do not need to be listed via btrfs_show_options, ie. keep
> the output same as it is now.
>
>
> david
>
Thanks for pointing out these problem.
This makes sense.Like space_cache and nospace_cache follows the way you
mentioned,
but most other options just followed the alphabet order, and a lot of
pairing is missing.
I'll try to add all the missingpairing and unify mount options in the
document.
Qu
prev parent reply other threads:[~2014-01-03 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 6:45 [PATCH] btrfs: Add "barrier" option to support "-o remount,barrier" Qu Wenruo
2014-01-02 15:41 ` David Sterba
2014-01-03 0:43 ` Qu Wenruo [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=52C607CA.6000105@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--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.