Skip to contentSkip to conversation

commit intervall for metadata and btrfs - is it planned ?

mount Mat 2 participants 3 messages Feb 10, 2010 – Feb 23, 2010 Btrfs file system

lore
Share & tools
lore

Mat

author
#0 lore raw

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 ?

Many thanks in advance

Mat

#1 lore raw
Quoted 20 lines · Mat

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 ?

Quoted 9 lines

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

author
#2 lore raw
Quoted 6 lines · Josef Bacik
Quoted 5 lines · Mat

Hi guys,

First off: you guys are doing amazing work !

btrfs "Better-FS" gets more and more stable, fast and space-efficien=

t than

Quoted 4 lines
Quoted 4 lines

all/most of the other filesystems :)

It being able to survive compiling of openoffice, chromium webbrowse=

r and other

Quoted 6 lines
Quoted 6 lines

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

Quoted 3 lines
Quoted 3 lines

into energy saving:

is the following mount-option which exists for reiserfs, ext2-4 and =

reiser4

Quoted 4 lines
Quoted 4 lines

(tmgr.atom_max_age) also planned to be implemented for btrfs ?

=A0 =A0 =A0 =A0commit=3Dnrsec
=A0 =A0 =A0 =A0 =A0 =A0 =A0 Sync all data and metadata =A0every =A0n=

rsec =A0seconds. =A0The =A0default

Quoted 9 lines
Quoted 7 lines

=A0 =A0 =A0 =A0 =A0 =A0 =A0 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 a=

ct like

Quoted 1 line

ext2/3 does, so the commit doesn't necessarily mean _all_ data will g=

o down to

Quoted 1 line

disk, just data thats been allocated and writeout has been started on=

, which is

Quoted 1 line

mostly controlled by the vm's dirty writeback stuff or if the apps yo=

u use have

Quoted 1 line

been using fsync(). =A0Any metadata thats been dirtied will be sync'e=

d every 30

Quoted 1 line

seconds. =A0Doing much more than that is just widening the window for=

you to lose

Quoted 1 line

new files and stuff (again, if they've not been fsync()'ed). =A0Perso=

nally 30

Quoted 1 line

seconds is a good balance between being safe and saving battery life,=

but I'm

Quoted 1 line

sure at some point we'll expose the commit interval via a mount optio=

n. =A0Thanks,

Quoted 3 lines

Josef

Thanks for your answer Josef !

I'll tweak /proc/sys/vm/dirty_writeback_centisecs, the other /proc/sys/vm/dirty* knobs for now
and stick to the limit of 30 seconds

Regards

Mat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html