Re: please review recent fixes for file write and fiemap

On Tue, Mar 8, 2011 at 11:58 AM, Chris Mason wrote: > Hi Everyone, > > The master branch of the btrfs-unstable tree has three shiny new > commits, which fix some important bugs in file_write and fiemap. > > These are not yet pushed to Linus but the plan is to send them out > before the final .38 r

Re: [PATCH V3] btrfs: implement delayed inode items operation

On tue, 8 Mar 2011 17:56:40 +0100, David Sterba wrote: > Hi, > > I did some testing, the speedup results match yours. I was watching kmem cache > stats of the delayed_node, seem to behave well. Increase and decrease of > number of active objects, from 3 to about ~400 (creat_unlink 5) and went

Re: resize ate my root node

Excerpts from Peter Stuge's message of 2011-03-07 12:48:20 -0500: > Hi, > > I ran btrfsctl resize -r -3gb /dev/sda2 using wireless-testing.git > based on 2.6.38-rc6 and all seemed good. df reported reduced size so > I repartitioned and rebooted. Filesystem can no longer be mounted: > > [10560.129

please review recent fixes for file write and fiemap

Hi Everyone, The master branch of the btrfs-unstable tree has three shiny new commits, which fix some important bugs in file_write and fiemap. These are not yet pushed to Linus but the plan is to send them out before the final .38 release. The commits fix errors in the copy_from_user handling wh

Re: [PATCH V3] btrfs: implement delayed inode items operation

Hi, I did some testing, the speedup results match yours. I was watching kmem cache stats of the delayed_node, seem to behave well. Increase and decrease of number of active objects, from 3 to about ~400 (creat_unlink 5) and went back to initial values after a few seconds. On my setup, there ar

Re: About btrfs chunk tree backups

On Tue, Mar 08, 2011 at 12:14:05PM +0800, Miao Xie wrote: > On Thu, 3 Mar 2011 07:37:25 -0500, Josef Bacik wrote: > > On Thu, Mar 03, 2011 at 05:01:00PM +0800, Miao Xie wrote: > >> Hi, Chris and Josef > >> > >> Recently, I am interested in chunk tree backups, which is described in > >> Project idea

[PATCH v1 3/6] btrfs: add state information for scrub

Add structures and state information needed for scrub Signed-off-by: Arne Jansen --- fs/btrfs/ctree.h | 26 ++ fs/btrfs/disk-io.c | 15 +++ fs/btrfs/ioctl.h | 29 + fs/btrfs/volumes.h |3 +++ 4 files changed, 73 insert

[PATCH v1 5/6] btrfs: sync scrub with commit & device removal

This adds several synchronizations: - for a transaction commit, the scrub gets paused before the tree roots are committed until the super are safely on disk - during a log commit, scrubbing of supers is disabled - on unmount, the scrub gets cancelled - on device removal, the scrub for the pa

[PATCH v1 4/6] btrfs: add scrub code and prototypes

This is the main scrub code. Signed-off-by: Arne Jansen --- fs/btrfs/Makefile |2 +- fs/btrfs/ctree.h | 14 + fs/btrfs/scrub.c | 1462 + 3 files changed, 1477 insertions(+), 1 deletions(-) diff --git a/fs/btrfs/Makefile b/fs/btrfs/Make

[PATCH v1 1/6] btrfs: add parameter to btrfs_lookup_csum_range

A parameter is added to search the commit root instead of the live root. Signed-off-by: Arne Jansen --- fs/btrfs/ctree.h |4 ++-- fs/btrfs/file-item.c |8 +++- fs/btrfs/inode.c |2 +- fs/btrfs/relocation.c |2 +- fs/btrfs/tree-log.c |4 ++-- 5 files changed,

[PATCH v1 0/6] btrfs: scrub

This series adds an initial implementation for scrub. It works quite straightforward. The usermode issues an ioctl for each device in the fs. For each device, it enumerates the allocated device chunks. For each chunk, the contained extents are enumerated and the data checksums fetched. The extents

[PATCH v1 6/6] btrfs: new ioctls for scrub

adds ioctls necessary to start and cancel scrubs, to get current progress and to get info about devices to be scrubbed. Note that the scrub is done per-device and that the ioctl only returns after the scrub for this devices is finished or has been canceled. Signed-off-by: Jan Schmidt --- fs/btrf

[PATCH v1 2/6] btrfs: make struct map_lookup public

definition of struct map_lookup moved from volumes.c to the header Signed-off-by: Arne Jansen --- fs/btrfs/volumes.c | 14 -- fs/btrfs/volumes.h | 14 ++ 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c index dad

[PATCH] remove unneeded DEFINE_WAITs

Signed-off-by: Arne Jansen --- fs/btrfs/extent-tree.c |2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c index a7aaa10..c1f0c28 100644 --- a/fs/btrfs/extent-tree.c +++ b/fs/btrfs/extent-tree.c @@ -4790,7 +4790,6 @@ wait_block

Re: btrfs lacking inode or file count?

Am 07.03.11 18:38, schrieb Christian Kujau: > On Mon, 7 Mar 2011 at 17:17, Jens Rosenboom wrote: >> I'm just starting to do some testing with btrfs and I noticed that "df >> -i" doesn't give any sensible output: > > Btrfs has dynamic inode allocation (like zfs), so it (should) never runs > out of

Re: synchronous removal?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I came across this when I tried to build a backup server. Was there any change on this in the meantime? Thanks, Andreas On 02.08.2010 17:25, K. Richard Pixley wrote: > How would you determine whether to remove another snapshot or to > wait for