From: Josef Bacik <josef@redhat.com>
To: Mat <jackdachef@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [mount] commit intervall for metadata and btrfs - is it planned ?
Date: Wed, 10 Feb 2010 13:55:37 -0500 [thread overview]
Message-ID: <20100210185537.GA20133@localhost.localdomain> (raw)
In-Reply-To: <loom.20100210T190536-373@post.gmane.org>
On Wed, Feb 10, 2010 at 06:15:26PM +0000, Mat wrote:
> Hi guys,
>
> First off: you guys are doing amazing work !
>
> btrfs "Better-FS" gets more and more stable, fast and space-efficient than
> all/most of the other filesystems :)
>
>
> It being able to survive compiling of openoffice, chromium webbrowser and other
> stressful stuff is a testament to its ever growing maturity
>
>
> Now on to my question:
>
> Since I'm using btrfs on more and more test-partitions on my system and also am
> into energy saving:
>
> is the following mount-option which exists for reiserfs, ext2-4 and reiser4
> (tmgr.atom_max_age) also planned to be implemented for btrfs ?
>
> commit=nrsec
> Sync all data and metadata every nrsec seconds. The default
> value is 5 seconds. Zero means default.
>
> (in this case ext3)
>
> if yes, when will it be added ?
>
>
It would be simple enough to do, but keep in mind that btrfs doesnt act like
ext2/3 does, so the commit doesn't necessarily mean _all_ data will go down to
disk, just data thats been allocated and writeout has been started on, which is
mostly controlled by the vm's dirty writeback stuff or if the apps you use have
been using fsync(). Any metadata thats been dirtied will be sync'ed every 30
seconds. Doing much more than that is just widening the window for you to lose
new files and stuff (again, if they've not been fsync()'ed). Personally 30
seconds is a good balance between being safe and saving battery life, but I'm
sure at some point we'll expose the commit interval via a mount option. Thanks,
Josef
next prev parent reply other threads:[~2010-02-10 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 18:15 [mount] commit intervall for metadata and btrfs - is it planned ? Mat
2010-02-10 18:55 ` Josef Bacik [this message]
2010-02-23 12:49 ` Mat
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=20100210185537.GA20133@localhost.localdomain \
--to=josef@redhat.com \
--cc=jackdachef@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox