linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathijs Kwik <bluescreen303@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: the flushoncommit mount option
Date: Wed, 19 May 2010 09:04:35 +0200	[thread overview]
Message-ID: <AANLkTimZ9JkeR-N-eCeeq3Ju-lhzzo8zkx_8im-qfjrD@mail.gmail.com> (raw)

Hi all,

Over the past few months, I've been trying out btrfs on separate mountpoints.
I like it very much so I would like to try it on my home or root
volumes and see if I can do something fun with the snapshots.
As btrfs still isn't production-ready, I made sure everything is
backed-up to an external ext4 disk.

Now when I first moved to try out ext4, there were some issues with
the way it handled commits(I think) compared to ext3, which made some
desktop-applications act weird.
This was fixed later, but I don't remember if it was ext4 to blame or
the apps changing their behavior to not depend on ext2/3 semantics.

Now, looking at btrfs's mount options, the flushoncommit description
sounded vaguely familiar regarding these ext4 oddities.
However, I couldn't find a good description of what the
(dis)advantages of flushoncommit would be.
On the volume I used upto now (music/video storage), I didn't notice
any differences, but maybe using it for home (dotfiles) or root will
be a bit different.

Does anyone remember the ext4 oddities I'm talking about?
Are they related to this flushoncommit mount option or am a totally
missing the point here?
And in case it is related... should I use the option for root or home
or is it safe to leave out?

Thanks for any information about this.
Mathijs

FYI: I'm using xubuntu 10.04 64bit, with (backported) 2.6.34 and the
latest btrfs-progs from git.

                 reply	other threads:[~2010-05-19  7:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=AANLkTimZ9JkeR-N-eCeeq3Ju-lhzzo8zkx_8im-qfjrD@mail.gmail.com \
    --to=bluescreen303@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;
as well as URLs for NNTP newsgroup(s).