search for: find_and_setup_root

...2 FS bytes used 733.80GB devid 1 size 931.51GB used 369.53GB path /dev/sdd devid 2 size 931.51GB used 369.51GB path /dev/sde Btrfs Btrfs v0.19 Obviously the RAID and the filesystems are still there. I then try to fsck the drives: btrfsck /dev/sde btrfsck: disk-io.c:416: find_and_setup_root: Assertion `!(!root->node)'' failed. I do not understand the error message that is provided. Can someone shed a little light on that message? Thank you. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.ker...

...000003e00072307a: 07f4 bcr 15,%r4 [ 121.415630] 000003e00072307c: eb6ff0480024 stmg %r6,%r15,72(%r15) [ 121.415651] Call Trace: [ 121.415661] ([<000003e000723040>] read_tree_block+0x40/0x7c [btrfs]) [ 121.415763] [<000003e000723868>] find_and_setup_root+0xa8/0xd0 [btrfs] [ 121.415856] [<000003e000726172>] open_ctree+0xb86/0xfe0 [btrfs] [ 121.421161] [<000003e000704734>] btrfs_get_sb+0x2bc/0x508 [btrfs] [ 121.421258] [<00000000000d2c92>] vfs_kern_mount+0xb2/0x168 [ 121.421289] [<00000000000d2dae>] do_kern_mount+0x52/...

...gt;commit_root = NULL; @@ -1116,8 +1116,6 @@ static int __setup_root(u32 nodesize, u32 leafsize, u32 sectorsize, INIT_LIST_HEAD(&root->anon_super.s_list); INIT_LIST_HEAD(&root->anon_super.s_instances); init_rwsem(&root->anon_super.s_umount); - - return 0; } static int find_and_setup_root(struct btrfs_root *tree_root, @@ -2412,7 +2410,7 @@ int write_ctree_super(struct btrfs_trans_handle *trans, return ret; } -int btrfs_free_fs_root(struct btrfs_fs_info *fs_info, struct btrfs_root *root) +void btrfs_free_fs_root(struct btrfs_fs_info *fs_info, struct btrfs_root *root) { spin_l...

Hi all - Here''s my current error handling patchset, against 3.1-rc8. Almost all of this patchset is preparing for actual error handling. Before we start in on that work, I''m trying to reduce the surface we need to worry about. It turns out that there is a ton of code that returns an error code but never actually reports an error. The patchset has grown to 65 patches. 46 of them

...); @@ -666,7 +666,7 @@ static int btree_submit_bio_hook(struct inode *inode, int rw, struct bio *bio, ret = btrfs_bio_wq_end_io(BTRFS_I(inode)->root->fs_info, bio, 1); - BUG_ON(ret); + btrfs_fixable_bug_on(ret); if (!(rw & REQ_WRITE)) { /* @@ -974,7 +974,7 @@ static int find_and_setup_root(struct btrfs_root *tree_root, &root->root_item, &root->root_key); if (ret > 0) return -ENOENT; - BUG_ON(ret); + btrfs_fixable_bug_on(ret); generation = btrfs_root_generation(&root->root_item); blocksize = btrfs_level_size(root, btrfs_root_level(&root-&...

This is a first draft of a subvolume quota implementation. It is possible to limit subvolumes and any group of subvolumes and also to track the amount of space that will get freed when deleting snapshots. The current version is functionally incomplete, with the main missing feature being the initial scan and rescan of an existing filesystem. I put some effort into writing an introduction into

From: Anand <anand.jain@oracle.com> This patch adds creation-time to the snapshot list display, which would help user to better manage the snapshots when number of snapshots grow substantially. This patch is developed and on top of the send/receive btrfs and btrfs-progs repo at git://github.com/ablock84/linux-btrfs.git (send-v2) git://github.com/ablock84/btrfs-progs.git (send-v2)

From: Anand Jain <anand.jain@oracle.com> (This patch is for the review/test not yet for the integration). Here is an implementation of the feature to add label to the subvolume and snapshots. Which would help sysadmin to better manager the subvol and snapshots. This can be done in two ways, one - using attr which is user land only changes but drawback is able to change the label