search for: fs_tree

...s 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 subvolume. This stuff can be easily adjusted for other grub versions. Attached is the patch against the package grub-0.97-38.fc10.src.rpm that can be found on the fedora mirrors, for example here: http://ucho.ig...

On Fri, Oct 10, Mike Latimer wrote: > On Friday, October 10, 2014 03:07:51 PM Olaf Hering wrote: > > Thanks for the pointers. I will poke around. At least augtool on the > > host seems to behave correctly: > > I don't think this is related to Augeas. Instead, I think it's the naming > convention SUSE uses for the root btrfs subvolume (@). It does not look like

...what I get, there can be any label for this? > The other bug is that mounting subvolumes in such setup fails anyway > because the subvol= argument lacks the absolute path. It was suggested > to use the "subvolume list" option -a and tweak the resulting list. > There is a <FS_TREE> prefix, which shouldnt be there according to > David. Do you have a way to reproduce the above situation (and possibly the root-partition-listed-twice situation too)? I'm not too familiar with btrfs yet, and my couple of simple installation of the latest beta of openSUSE 13.2 didn...

...opts, *orig, *p; @@ -426,6 +428,18 @@ static int btrfs_parse_early_options(const char *options, fmode_t flags, *subvol_objectid = intarg; } break; + case Opt_subvolrootid: + intarg = 0; + error = match_int(&args[0], &intarg); + if (!error) { + /* we want the original fs_tree */ + if (!intarg) + *subvol_rootid = + BTRFS_FS_TREE_OBJECTID; + else + *subvol_rootid = intarg; + } + break; case Opt_device: error = btrfs_scan_one_device(match_strdup(&args[0]), flags, holder, fs_devices); @@ -715,6 +729,7 @@ static int btrfs_get_sb(struct...

..._parse_early_options(const char *options, fmode_t flags, switch (token) { case Opt_subvol: intarg = 0; - match_int(&args[0], &intarg); - if (intarg) - *subvol_objectid = intarg; + error = match_int(&args[0], &intarg); + if (!error) { + /* we want the original fs_tree */ + if (!intarg) + *subvol_objectid = + BTRFS_FS_TREE_OBJECTID; + else + *subvol_objectid = intarg; + } break; case Opt_device: error = btrfs_scan_one_device(match_strdup(&args[0]), -- 1.5.4.3 -- To unsubscribe from this list: send the line "unsubscribe l...

...} break; case Opt_subvolid: - error = match_int(&args[0], &intarg); - if (!error) { - goto out; - } else if (intarg >= 0) { + num = match_strdup(&args[0]); + if (num) { + *subvol_objectid = memparse(num, NULL); + kfree(num); /* we want the original fs_tree */ - if (!intarg) + if (!*subvol_objectid) *subvol_objectid = BTRFS_FS_TREE_OBJECTID; - else - *subvol_objectid = intarg; } else { error = -EINVAL; goto out; -- 1.8.0.1 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in t...

...assume thats the entire thing, and skip it to not set is_root=1? The other bug is that mounting subvolumes in such setup fails anyway because the subvol= argument lacks the absolute path. It was suggested to use the "subvolume list" option -a and tweak the resulting list. There is a <FS_TREE> prefix, which shouldnt be there according to David. Olaf

New option to subvolume list that acts as a global filter and applies the other filters to either live subvolumes or the uncleaned ones. The path to the deleted subvolumes is lost at the deletion time, sample output looks like: ID 259 gen 7 top level 0 path <FS_TREE>/DELETED Signed-off-by: David Sterba <dsterba@suse.cz> --- btrfs-list.c | 24 +++++++++++++++++++++--- btrfs-list.h | 4 ++++ cmds-subvolume.c | 8 +++++++- 3 files changed, 32 insertions(+), 4 deletions(-) diff --git a/btrfs-list.c b/btrfs-list.c index 9411e4d..f3618b9...

Hi! I used to have arch linux running on 1 btrfs partition (sda1, incl. /boot). When switching to 3.2.5 recently the system fails to boot: (after udevd) /etc/rc.sysinit: line 15: 117 Bus error mountpoint -q /proc and so on, no idea. It used to boot with 3.2.4, but 1) I obviously had some corruption in the tree, when I tried to delete a certain file I hit e.g. "kernel BUG at

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)

Hi All, the following patches implement the recursively snapshotting and deleting of a subvolume. To snapshot recursively you must pass the -R switch: # btrfs subvolume create sub1 Create subvolume ''./sub1'' # btrfs subvolume create sub1/sub2 Create subvolume ''sub1/sub2'' # btrfs subvolume snapshot -R sub1 sub1-snap Create a snapshot of

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

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