similar to: R: Re: Subvolumes and /proc/self/mountinfo

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:

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, following the thread about the BTRFS_IOC_TREE_SEARCH ioctl [1], I made a patch which try to address the problem of restarting the ioctl. In the current solution is the application during the restart of the search to fill the min_* fields in the "struct btrfs_ioctl_search_key". In general the values set are the last one returned "+1". But doing so we reduce the

Hello, This is the second attempt to bring in cross subvolume reflinks into btrfs. The first attempt was NAKed due to missing vfs mount checks and a clear description of what btrfs subvolumes are and probably also why cross subvolume reflinks are ok in the case of btrfs. This version of the patch comes from David and is in SUSE kernels since a long time, so it is tested and working. The patch

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

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

>From 03115f064be2e074d84f4e2105d2cdebde10f6ba Mon Sep 17 00:00:00 2001 From: Yi Yang <yi.y.yang at intel.com> Date: Tue, 12 Jul 2011 14:53:50 +0800 Subject: [PATCH] Use a general way to get the default subvolume for btrfs --- extlinux/btrfs.h | 105 +++++++++++++++++++ extlinux/main.c | 304 ++++++++++++++++++++++++++++++++++++++++++++++++------ 2 files changed, 377 insertions(+),

Hi Anthony, I think that for you may be interested to read this thread http://kerneltrap.org/mailarchive/linux-btrfs/2009/11/20/6588643/thread and to read a my blog about this argument http://kreijack.blogspot.com/2010/01/linux-btrfs-example-of-layout.html Regards Goffredo >----Messaggio originale---- >Da: anthony@extof.me >Data: 19/05/2010 8.50 >A:

Add a mount option user_subvol_rm_allowed that allows users to delete a (potentially non-empty!) subvol when they would otherwise we allowed to do an rmdir(2). We duplicate the may_delete() checks from the core VFS code to implement identical security checks (minus the directory size check). Signed-off-by: Sage Weil <sage@newdream.net> --- fs/btrfs/ctree.h | 1 + fs/btrfs/ioctl.c |

Hello all, in IRC we had a discussion on how we could solve sending live subvolumes and how to send subvolumes without the need to administrate/keep old snapshots for incremental sends. One of the ideas was to introduce "sendshots", which are basically snapshots where no refs are counted for file data. This means, that when file data is changed in the sendshot origin, we do not consume

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, this is a new attempt to improve the output of the command "btrfs fi df". The previous attempt received a good reception. However there was no a general consensus about the wording. Moreover I still didn''t understand how btrfs was using the disks. A my first attempt was to develop a new command which shows how the disks

On Sun, Feb 21, 2010 at 8:40 AM, Goffredo Baroncelli <kreijack@gmail.com> wrote: >       filesystem resize [+/-]<size>[gkm]|max <filesystem> -filesystem resize [+/-]<size>[gkm]|max <filesystem> +filesystem resize [+/-]<size>[gkm]|max <dev> This command works on devices, not paths. >              Resize a filesystem identified by <path>.  The

The code to parse btrfs subvol entries in /etc/fstab failed if the entry had more than one comma-separated option, for example: /dev/sda4 /home btrfs rw,user,subvol=foo 0 0 This commit fixes that code to use Augeas correctly. Fixes commit 7ba0e10501f23358c38939930d613bf2393d744d. Reported by: Zhongfu Li https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1615337 ---

Hi Thomas, >----Messaggio originale---- >Da: thomas@kupper.org >Data: 22/01/2010 10.48 >A: "Leszek Ciesielski"<skolima@gmail.com> >Cc: "linux-btrfs"<linux-btrfs@vger.kernel.org> >Ogg: Re: mount command not honoring rootflags passed > > >On 22 Jan 2010, at 10:40, Leszek Ciesielski wrote: > >> On Fri, Jan 22, 2010 at 10:30 AM,

Hi, I have a box with / and /home being subvolumes from the same btrfs filesystem. /etc/fstab: UUID=c0686... / btrfs subvol=root,x-systemd.device-timeout=0 1 1 UUID=c0686... /home btrfs subvol=home,x-systemd.device-timeout=0 1 1 ... / is initially mounted readonly by the initramfs, and then after switching to the real system, /home is attempted to be mounted in parallel with /

Hi Li, >----Messaggio originale---- >Da: lizf@cn.fujitsu.com >Data: 30/11/2010 8.03 >A: <kreijack@libero.it> >Cc: <linux-btrfs@vger.kernel.org> >Ogg: Re: [PATCH 5/5] btrfs: Add ioctl to set snapshot readonly/writable > >Goffredo Baroncelli wrote: >> Hi Li, >> >> On Monday, 29 November, 2010, Li Zefan wrote: >>> This allows us to set

We want ''btrfs subvolume list'' only to list readonly subvolumes, this patch set introduces a new option ''r'' to implement it. You can use the command like that: btrfs subvolume list -r <mnt> Changelog v2 -> v3: - re-implement list_subvols() - re-implement this read-only subvolume list function based on the new list_subvols() Changelog v1 -> v2: -

Hi all, I suffered a lot for the terrific performance of aptitude on a BTRFS filesystem. I don''t think that BTRFS is a slow filesystem, but it seems that some aptitude (or dpkg) patterns are capable to highlight the btrfs slowness in some corner case. In order to alleviate this problem, I wrote a small script which calls aptitude with the LD_PRELOAD libeatmyadata library. And now I

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

Hi, on my system the klibc/ash ( 0.197 ) doesn't compile: [ghigo@therra ash]$ pwd /home/ghigo/klibc/klibc-0.197/ash [ghigo@therra ash]$ make [...] gcc -Wp,-MD,.arith_lex.d -mregparm=3 -DREGPARM=3 -march=i386 -Os -g -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -D__KLIBC__ -DBITSIZE=32 -I../include/arch/i386 -I../include/bits32 -I../include