search for: btrfs_mount

...r dereferences and devices hanging in busy state) to sanitize error handling during mount sequence. This is on top of for-linus + slyfox''s double-free fix. Thanks, Ilya Ilya Dryomov (5): Btrfs: fix memory leak in btrfs_parse_early_options() Btrfs: fix subvol_name leak on error in btrfs_mount() Btrfs: avoid null dereference and leaks when bailing from open_ctree() Btrfs: close devices on all error paths in open_ctree() Btrfs: rework error handling in btrfs_mount() fs/btrfs/disk-io.c | 42 ++++++++++++++++++------------------------ fs/btrfs/super.c | 47 ++++++++++++++++...

...so be deleted. What''s under subvolumes are just various files and directories, should not be related to this problem. After a while of using this setup, without any obvious steps to reproduce it, the filesystem goes into a state where the following happens: # btrfs subvolume create btrfs_mount/test_subvolume Create subvolume ''btrfs_mount/test_subvolume'' ERROR: cannot create subvolume - File exists In regards to data, the filesystem is pretty empty, it only has a single empty directory. I don''t know about the metadata, at this point. The problem goe...

Hi, I''ve observed a rather strange behaviour while trying to mount two identical copies of the same image to different mount points. Each modification to one image is also performed in the second one. Example: dd if=/dev/sda? of=image1 bs=1M cp image1 image2 mount -o loop image1 m1 mount -o loop image2 m2 touch m2/hello ls -la m1 //will now also include a file calles "hello"

Hello everyone. The following patches are for Fedora 10(**). The distro-independent package will be put to kernel.org a bit later. I. Loading kernels from btrfs volumes Now you can load kernels and initrds from btrfs volumes composed of many devices. WARNING!!! Make sure that all components of your loading btrfs volume(*) are visible to grub. Otherwise, you''ll end with

...rnel: [<ffffffffa0294740>] ? replay_one_dir_item+0xf0/0xf0 [btrfs] Feb 02 13:59:58 Edge kernel: [<ffffffffa025d9d7>] open_ctree+0x1587/0x1ba0 [btrfs] Feb 02 13:59:58 Edge kernel: [<ffffffff81255091>] ? disk_name+0x61/0xc0 Feb 02 13:59:58 Edge kernel: [<ffffffffa0236ae3>] btrfs_mount+0x633/0x770 [btrfs] Feb 02 13:59:58 Edge kernel: [<ffffffff81165f60>] ? alloc_pages_current+0xb0/0x120 Feb 02 13:59:58 Edge kernel: [<ffffffff81188163>] mount_fs+0x43/0x1b0 Feb 02 13:59:58 Edge kernel: [<ffffffff811a2974>] vfs_kern_mount+0x74/0x110 Feb 02 13:59:58 Edge kernel:...

...s+0x3bd/0x490 [btrfs] [ 68.128434] [<ffffffffa04a3270>] ? replay_one_dir_item+0xf0/0xf0 [btrfs] [ 68.128477] [<ffffffffa0466689>] open_ctree+0x17b9/0x1e80 [btrfs] [ 68.128513] [<ffffffff813555d3>] ? proc_comm_connector+0x33/0x120 [ 68.128551] [<ffffffffa043f456>] btrfs_mount+0x636/0x830 [btrfs] [ 68.128584] [<ffffffff81141cd2>] ? pcpu_alloc+0x7d2/0x9e0 [ 68.128616] [<ffffffff8118f5d9>] mount_fs+0x39/0x1b0 [ 68.128643] [<ffffffff81141ef0>] ? __alloc_percpu+0x10/0x20 [ 68.128676] [<ffffffff811a8c27>] vfs_kern_mount+0x67/0x100 [ 68.12...

...t_buffer_pages+0x55/0xb0 > [ 605.117820] [<ffffffff8122ea05>] ? read_tree_block+0x35/0x60 > [ 605.117980] [<ffffffff8122ffc2>] ? open_ctree+0xd22/0x1440 > [ 605.118140] [<ffffffff812118f0>] ? btrfs_set_super+0x0/0x20 > [ 605.118300] [<ffffffff81212302>] ? btrfs_mount+0x372/0x4e0 > [ 605.118465] [<ffffffff810d7c85>] ? vfs_kern_mount+0x75/0x1b0 > [ 605.118627] [<ffffffff810ee19e>] ? get_fs_type+0x3e/0xd0 > [ 605.118783] [<ffffffff810d7e33>] ? do_kern_mount+0x53/0x130 > [ 605.118942] [<ffffffff810f15b9>] ? do_mount+0x2d9...

...em array for a translation map. We have 3 different pools for search so that logical threads (e.g. name resolution, updating fs_root, looking for translation map) won''t step on each other. Every such pool is represented by structure btrfs_path, which has one "sliding" 4K-buffer. btrfs_mount() looks through super versions and pick up the most recent one. Then chunk_root and tree_root are installed to the global structure btrfs_fs_info. At the end we pick up and install the latest version of fs_tree. btrfs_dir() updates the fs_tree during path walk every time when we jump to another su...

...er_log_trees+0x21b/0x3a0 [btrfs] [ 37.645754] [<ffffffffa0f45220>] ? replay_one_dir_item+0xe0/0xe0 [btrfs] [ 37.645763] [<ffffffffa0f0883d>] open_ctree+0x14ed/0x1ac0 [btrfs] [ 37.645767] [<ffffffff8121e101>] ? disk_name+0x61/0xc0 [ 37.645773] [<ffffffffa0ee5836>] btrfs_mount+0x5b6/0x6a0 [btrfs] [ 37.645776] [<ffffffff8113f400>] ? alloc_pages_current+0xb0/0x120 [ 37.645780] [<ffffffff81163533>] mount_fs+0x43/0x1b0 [ 37.645783] [<ffffffff8117d740>] vfs_kern_mount+0x70/0x100 [ 37.645786] [<ffffffff8117dc64>] do_kern_mount+0x54/0x110 [...

...70 [btrfs] [ 27.165784] [<ffffffffa0136d11>] btrfs_recover_log_trees+0x211/0x300 [btrfs] [ 27.168297] [<ffffffffa01353c0>] ? replay_one_dir_item+0xe0/0xe0 [btrfs] [ 27.170832] [<ffffffffa00fd907>] open_ctree+0x13e7/0x17a0 [btrfs] [ 27.178506] [<ffffffffa00d879e>] btrfs_mount+0x40e/0x5c0 [btrfs] [ 27.212137] RIP [<ffffffffa010b781>] btrfs_add_link+0x161/0x1c0 [btrfs] -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-in...

Hello, Trying to balance a 2TB filesystem on the 3.8.5 kernel: Label: ''p2'' uuid: 01f6cc8b-d305-40e1-bac8-8fdd548f611e Total devices 1 FS bytes used 1.32TB devid 1 size 1.80TB used 1.37TB path /dev/sda2 System: total=4.00MB, used=156.00KB Data+Metadata: total=1.37TB, used=1.32TB I am getting a Segmentation fault in ''btrfs'' utility, and following in

...7ab8>] btrfs_recover_log_trees+0x9f/0x2ff [ 3964.729881] [<ffffffff81206a32>] ? replay_one_buffer+0x235/0x235 [ 3964.729891] [<ffffffff811dcbe5>] open_ctree+0x143d/0x1820 [ 3964.729899] [<ffffffff8128ffcc>] ? string.isra.3+0x3d/0xa4 [ 3964.729911] [<ffffffff811bf3a2>] btrfs_mount+0x36d/0x4cd [ 3964.729920] [<ffffffff810e8412>] ? pcpu_next_pop+0x38/0x45 [ 3964.729942] [<ffffffff8112a102>] ? alloc_vfsmnt+0xa6/0x192 [ 3964.729953] [<ffffffff81116207>] mount_fs+0x64/0x14d [ 3964.729961] [<ffffffff810e94d8>] ? __alloc_percpu+0xb/0xd [ 3964.729971] [&...

...0x150 [btrfs] Jan 24 11:26:42 localhost kernel: [ 14.777319] [<ffffffffa01ca958>] open_ctree+0x1718/0x1da0 [btrfs] Jan 24 11:26:42 localhost kernel: [ 14.777324] [<ffffffff813303e1>] ? disk_name+0x61/0xc0 Jan 24 11:26:42 localhost kernel: [ 14.777333] [<ffffffffa01a3a84>] btrfs_mount+0x614/0x750 [btrfs] Jan 24 11:26:42 localhost kernel: [ 14.777337] [<ffffffff81197273>] mount_fs+0x43/0x1b0 Jan 24 11:26:42 localhost kernel: [ 14.777339] [<ffffffff811b1a87>] ? alloc_vfsmnt+0xd7/0x1b0 Jan 24 11:26:42 localhost kernel: [ 14.777342] [<ffffffff811b1c14>] vf...

...[ 480.864990] Call Trace: [ 480.865019] [<ffffffffa03d1a10>] ? fixup_inode_link_counts+0x150/0x150 [btrfs] [ 480.865061] [<ffffffffa0398a2c>] open_ctree+0x171c/0x1da0 [btrfs] [ 480.865095] [<ffffffff81331461>] ? disk_name+0x61/0xc0 [ 480.865126] [<ffffffffa0371a83>] btrfs_mount+0x613/0x750 [btrfs] [ 480.865160] [<ffffffff81197c43>] mount_fs+0x43/0x1b0 [ 480.865187] [<ffffffff811b2457>] ? alloc_vfsmnt+0xd7/0x1b0 [ 480.865214] [<ffffffff811b25e4>] vfs_kern_mount+0x74/0x110 [ 480.865240] [<ffffffff811b495f>] do_mount+0x21f/0xac0 [ 480.865270]...

Hi, The following patches add support for ext4 and btrfs to PV-GRUB. These patches are taken nearly verbatim from those provided by Fedora and Gentoo. We''ve been using these patches for the PV-GRUB images available in EC2 for some time now with no problems. Changes from v1: - Makefile has been changed to check the exit code from patch - The btrfs patch has been rebased to apply

...x1da/0x2d8 [btrfs] [ 316.549367] [<ffffffffa01ab6a4>] ? replay_one_dir_item+0xb9/0xb9 [btrfs] [ 316.549474] [<ffffffffa017c2ce>] ? open_ctree+0x1300/0x16aa [btrfs] [ 316.549552] [<ffffffff811b8118>] ? ida_get_new_above+0x176/0x198 [ 316.549644] [<ffffffffa01613c2>] ? btrfs_mount+0x370/0x4ca [btrfs] [ 316.549722] [<ffffffff810d3e0d>] ? pcpu_next_pop+0x35/0x41 [ 316.549790] [<ffffffff810d4de8>] ? pcpu_alloc+0x7aa/0x7ec [ 316.549864] [<ffffffff81105705>] ? mount_fs+0x61/0x144 [ 316.549933] [<ffffffff811187ca>] ? vfs_kern_mount+0x61/0xcc [ 316....

I''ve been working to try to improve the write-ahead log''s performance, and I found that the bottleneck addresses in the checksum items, especially when we want to make a random write on a large file, e.g a 4G file. Then a idea for this suggested by Chris is to use sub transaction ids and just to log the part of inode that had changed since either the last log commit or the last

...45.917188] [<f9cdff10>] ? run_one_async_done+0xd0/0xd0 [btrfs] [ 45.917188] [<f9ce23f7>] read_tree_block+0x47/0x50 [btrfs] [ 45.917188] [<f9ce5f5c>] open_ctree+0x13bc/0x1b60 [btrfs] [ 45.917188] [<c030b163>] ? strlcpy+0x33/0x50 [ 45.917188] [<f9cbe89b>] btrfs_mount+0x77b/0x8c0 [btrfs] [ 45.917188] [<c0231ef0>] ? __kmalloc_track_caller+0x80/0x1d0 [ 45.917188] [<c0246351>] mount_fs+0x31/0x180 [ 45.917188] [<c020e3df>] ? __alloc_percpu+0xf/0x20 [ 45.917188] [<c025c6b5>] vfs_kern_mount+0x45/0xc0 [ 45.917188] [<c025e402&gt...