similar to: [PATCH] Btrfs: sectorsize align offsets in fiemap

Hi, We are trying to use OCFS2 as VM storage. After running into problems with qemu's disk_mirror feature we now think there could be a problem with the FIEMAP ioctl in OCFS2. As far as I understand the situation looks like this: Qemu inquiries the FS if the given section of the image is already allocated via the FIEMAP ioctl [1] It especially checks if fm_mapped_extents is greater 0.

Introduce a new flag FIEMAP_FLAG_COW to fiemap ioctl(2) interface. If this flag is set, the kernel will only return the mapped extents which are in copy-on-write state. Signed-off-by: Jie Liu <jeff.liu at oracle.com> Cc: Alexander Viro <viro at zeniv.linux.org.uk> Cc: Andreas Dilger <adilger at dilger.ca> Cc: Dave Chinner <david at fromorbit.com> Cc: Mark Fasheh

I''m going to be removing hole extents in the near future so I wanted to make a sanity test for btrfs_get_extent to make sure I don''t break anything in the meantime. This patch just puts btrfs_get_extent through its paces by giving it a completely unreasonable mapping to look at and make sure it is giving us back maps that make sense. Thanks, Signed-off-by: Josef Bacik

https://bugzilla.samba.org/show_bug.cgi?id=8918 Summary: Use fiemap to quickly detect zero ranges of source file Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org

This is my still-working-on-it code for btrfs directIO read. I''m posting it so people can see the progress being made on the project and can take an early shot at telling me this is just a bad idea and I''m crazy if they want to, or point out where I made some stupid mistake with btrfs core functions. The code is not complete and *NOT* ready for review or testing. I looked at

We use set_bit() to assign ordered extent''s flags, but in the related tracepoint we don''t do the same thing, which makes the trace output not to parse flags correctly. Also, since the flags are bits stuff, we change to use __print_flags with a ''delim'' instead of __print_symbolic. Signed-off-by: Liu Bo <bo.li.liu@oracle.com> ---

Hi all - The following 9 patches add more error handling to the btrfs code: - Add btrfs_panic - Catch locking failures in {set,clear}_extent_bit - Push up set_extent_bit errors to callers - Push up lock_extent errors to callers - Push up clear_extent_bit errors to callers - Push up unlock_extent errors to callers - Make pin_down_extent return void - Push up btrfs_pin_extent errors to

This patch introduce extent buffer cache for every i-node. By this way, we can save the search time and reduce the lock contention of the root because we needn''t search the item from the root of b+ tree. Implementation: - add two pointers of extent buffer into btrfs_inode struct, one for nodes/leaves of fs/file tree, the other for nodes/leaves of the log tree. - add a variant to tell

Testing with a modified copy of the fsfuzz, the btrfs filesystem hanged with the following output in dmesg. The system still remain responsive, except for the terminal that was doing the testing. Any attempt to list files in the btrfs-mounted directory will block as well. I am not sure how to proceed from here. Possibly to reboot the system next. But anyone can shed some suggestion?

I need everybody to go over this with a fine toothed comb since it is a pretty big change. I think it is right and it seems to come out right, but if it''s not it will mean we screw up O_DIRECT on snapshotted files with preallocated extents, so please, make sure it is correct :). --- Subject: [PATCH] Btrfs: rework can_nocow_odirect We are always doing the file extent lookup in here

This depends on the change to ordered data search. Signed-off-by: jim owens <owens6336@gmail.com> --- fs/btrfs/dio.c | 150 +++++++++++++++++++++++++++++++++++++++----------------- 1 files changed, 104 insertions(+), 46 deletions(-) diff --git a/fs/btrfs/dio.c b/fs/btrfs/dio.c index b6934be..c930ff5 100644 --- a/fs/btrfs/dio.c +++ b/fs/btrfs/dio.c @@ -435,14 +435,81 @@ static void

Hi, everyone! mkfs.btrfs just does the following check for sectorsize when we use it to make a btrfs. sectorsize = max(sectorsize, (u32)getpagesize()); Does that mean we can set sectorsize to any number greater than pagesize? If not, I think we should do more check for sectorsize in mkfs.btrfs. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of

moved the node-,leaf-,sectorsize from btrfs_root to btrfs_fs_info since we don''t intend to allow different sizes between trees also removed sectorsize from btrfs_block_group_cache because it now can use the one in fs_info updated all uses accordingly please note in disk-io.c: -static int __setup_root(nodesize, leafsize, sectorsize, stripesize, - *root,

Our code is not ready to cope with a sectorsize that''s not equal to PAGE_SIZE. It will lead to hanging-on while writing something. Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com> --- fs/btrfs/disk-io.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c index 20196f4..b9866f2 100644 --- a/fs/btrfs/disk-io.c +++

Hi - I''m trying btrfs with kernel 2.6.38.8-32.fc15.x86_64 (a Fedora kernel). I''m just doing a tar-to-tar copy onto the file system with compress- force=zlib. Here are some traces of the stuck processes. flush-btrfs-5 seems to be stuck: Jul 8 11:49:40 xback2 kernel: [74920.681032] flush-btrfs-5 D ffff88003c7bae60 0 11712 2 0x00000080 Jul 8 11:49:40 xback2 kernel:

Returns a file''s size on disk. Had been posted by Chris Ball over a year ago (http://article.gmane.org/gmane.comp.file-systems.btrfs/2873). Chris Mason suggested a couple of improvements back then, which I have implemented in this version: - use u64 to return the result - replaced the loop while (1) { struct btrfs_ordered_extent *ordered;

Hi Timo, Any chance the mbox/mdbox writer code could be modified to do physical preallocation on files to help avoid file(system) fragmentation? Constantly appending a file is the prime recipe for causing fragmentation, and mbox is notorious for this--not a fault of Dovecot but the nature of the mbox beast. Obviously maildir doesn't have such a problem, but some (many?) of us still prefer

Is there a way to find the holes in sparse files, other than assuming contiguous blocks of zeroes are holes? Thanks, Sean

I just downloaded the pre48 and ran make. It ran fine for everything, but ended with a number of errors related to the syslxcom program. Usually, I only see the messages about the windows build since I am doing the make on a Fedora 10 system. Is there something new that has been added that requires something that I am missing? From looking at the program this isn't related to the isolinux

https://bugzilla.samba.org/show_bug.cgi?id=12305 Bug ID: 12305 Summary: --fallocate and --sparse works wrong Product: rsync Version: 3.1.1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: