similar to: [PATCH V3 0/7 ] Btrfs-progs: enhance btrfs subvol list only to show read-only snapshots

"btrfs subvolume list" gets a new option "--fields=..." which allows to specify which pieces of information about subvolumes shall be printed. This is necessary because this commit also adds all the so far missing items from the root_item like the received UUID, all generation values and all time values. The parameters to the "--fields" option is a list of items to

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, enclose a patch to improve the "btrfs subvolume find-new" command. This is a RFC because it is not finished, but it is an usable state and may be discussed. The aim of this patch is: - take in account not only an update of the extent but also an update of the inode and xattr (which includes the acl) - extract the generation reference number directly from a snapshot The new

Setting subvolume/snapshot readonly has been missing for a long time. With this patch, we can set a subvolume/snapshot readonly via: o btrfs subvolume set-ro <path> Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com> --- cmds-subvolume.c | 40 ++++++++++++++++++++++++++++++++++++++++ ioctl.h | 7 +++++++ 2 files changed, 47 insertions(+), 0 deletions(-) diff --git

When mounting a subvolume by name, mountinfo shows the name of the subvolume. When mounting a subvolume using subvolid it does not. Seems like a problem when trying to determine what is mounted. -o subvol=<name> # cat /proc/self/mountinfo | grep vda 43 34 0:29 /home /home rw,relatime shared:29 - btrfs /dev/vda1 rw,seclabel,space_cache 44 34 0:29 /boot /boot rw,relatime shared:30 - btrfs

Hi all, this patch include in /proc/mount the info about which subvolume is mounted and which metadata_ratio value is used. $ cat /proc/mounts rootfs / rootfs rw 0 0 [...] /dev/sdc /tmp/t4 btrfs rw,relatime,metadata_ratio=20 0 0 /dev/sdc /mnt/btrfs btrfs rw,relatime,degraded,metadata_ratio=20,subvol=snap- of-root 0 0 BR G.Baroncelli commit 3d7ea7bbd70a66c4d0f369b2879c503b722e8834 Author:

The kernel patch series just sent (Subject: "Btrfs: scrub: print path to corrupted files and trigger nodatasum fixup") introduces two new ioctls to do in-kernel filesystem path construction. This series provides the corresponding userspace changes, adding two new commands to the btrfs utility: -- btrfs resolve inode [-v] <inode> <path> resolves an <inode> to all

If we change our default subvolume, btrfs receive will fail to find subvolume. To fix this problem, we have three ideas: 1.make btrfs snapshot ioctl support passing source subvolume''s objectid. 2.when we want to using interval subvolume path, we mount it other place that use subvolume 5 as its default subvolume. 3.tell the user to mount the toplevel subvol by himself and run receive

This is the source code of the man page of btrfs. The main changes from my previous patch are: - Rearranged the short command in order to avoid conflicts - Renamed the ''create'' verb is ''subvolume'' Thanks to Daniel for some tweaks on the syntax BR G.Baroncelli diff --git a/man/Makefile b/man/Makefile index 4e8893b..4a90b75 100644 --- a/man/Makefile +++

All - I''ve put together a new integration branch based on Chris''s new master. This includes the userspace patches for qgroups, restriper, and Josef''s restore utility, plus a bunch of other things with mostly minor impact. The shortlog is attached at the end of this email. As always, it''s available from:

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

On Thu, Oct 16, Olaf Hering wrote: > I can probably add a check somewhere to catch the whatever=="@". A > better fix would be to check if a given subvolume is for the entire > partition. So after talking to David Sterba there is no way to tell if a given subvolume is for the entire partition. Also my attempt to "fix" it by using the -o option is unreliable. Richard,

On Fri, Oct 10, Olaf Hering wrote: > Is btrfs subvol support failing just for me? This is an old thread, and it seems the underlying bug is not fixed because guestfs takes the wrong approach, IMO. >From how I understand btrfs, it has the concept of subvolumes. Each one is an entry point for a separate filesystem. In addition to that it has a default subvol which is used if no specific

On Friday 17 October 2014 11:25:03 Olaf Hering wrote: > On Thu, Oct 16, Olaf Hering wrote: > > I can probably add a check somewhere to catch the whatever=="@". A > > better fix would be to check if a given subvolume is for the entire > > partition. > > So after talking to David Sterba there is no way to tell if a given > subvolume is for the entire

This commit adds a command line option to enable sending streams which make use of the new end-cmd semantic if multiple snapshots are sent back-to-back. The goal is to use the <end cmd> as an indication to stop reading the input stream. So far, the receiver could only use EOF to recognize the end. If the new command line option ''-e'' is set, this commit requires a kernel

Older kernels would generally be able to still mount the filesystem with the default subvolume set, but it would result in a different volume being mounted, which could be an even more unpleasant suprise for users. So if you set your default subvolume, you can''t go back to older kernels. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/ctree.h | 4 +++-

Hello, recently I installed a distribution I want to look at via chroot into a btrfs subvolume on a multidevice btrfs. Now I tried to boot this, the kernel command line in GRUB looks as follows so far: /kernel-2.6.29-rc7-git3 root=/dev/sdb7 rootfstype=btrfs rootflags=device=/dev/sda1,subvol=archroot This gives "VFS: cannot find sdb7 or bad block", like it would when trying to mount

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 (@). I encountered this same issue in virt-v2v and posted a question here:

If we change our default subvolume, btrfs receive will fail to find subvolume. To fix this problem, i have two ideas. 1.make btrfs snapshot ioctl support passing source subvolume''s objectid 2.when we want to using interval subvolume path, we mount it other place that use subvolume 5 as its default subvolume. We''d better use the second approach because it won''t bother

Hi Chris, This is the extent of my current queue of Btrfs snapshot/subvol/commit stuff. Most of these were posted several months ago. Can be sent upstream during this merge window? Not having this functionality is becoming a bit of a roadblock for our efforts to keep the Ceph data in a consistent state. These patches are also available from