similar to: Non-root can create, but not delete, btrfs snapshots?

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: -

here is my script to rsync a directory to a zfs filesystem, rotate existing snapshots, then create a "latest" snapshot. work to be done - check for an include/exclude list for the rsync command - create a monthly snapshot be careful of possible line wraps #!/bin/sh RSYNC_CMD="/usr/local/bin/rsync -axS --delete-delay --stats" # first argument is the remote server to

This happens on a freshly created btrfs filesystem in a raid10 (4x1TB) configuration with three subvolumes and 1.5 TB data. When I try to snapshot one of the subvolumes (with 100 GB of data), it says that the snapshot creation failed and I get the following error message: btrfs: could not do orphan cleanup -116 After the failure: - The snapshot exists in `btrfs subvolume list'' - The

btrfs_subvolume_create creates only subvolumes. btrfs_subvolume_delete deletes subvolumes or snapshots. Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> --- generator/actions.ml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/generator/actions.ml b/generator/actions.ml index 89332f5..fe492e6 100644 --- a/generator/actions.ml +++ b/generator/actions.ml @@ -10248,19

On Fri, Nov 21, 2014 at 11:35:11AM +0100, Pino Toscano wrote: > On Friday 21 November 2014 13:17:55 Hu Tao wrote: > > btrfs_subvolume_create creates only subvolumes. btrfs_subvolume_delete > > deletes subvolumes or snapshots. > > > > Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> > > --- > > generator/actions.ml | 8 ++++---- > > 1 file changed, 4

On Friday 21 November 2014 13:17:55 Hu Tao wrote: > btrfs_subvolume_create creates only subvolumes. btrfs_subvolume_delete > deletes subvolumes or snapshots. > > Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> > --- > generator/actions.ml | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/generator/actions.ml b/generator/actions.ml

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

While exploring some btrfs maintenance with respect to defragmenting I ran the following commands: # filefrag /path/to/34G.file /path/to/5.7G.file /path/to/34G.file: 2406 extents found /path/to/5.7G.file: 572 extents found Thinking those mostly static files could be less fragmented I ran: # btrfs filesystem defragment -c /path/to/34G.file # btrfs filesystem defragment -c /path/to/5.7G.file and

What happens if you set an individual file inside a subvolume as nocow (chattr +C) and then take a snapshot of that subvolume and modify the file in both? Will btrfs now ignore the nocow attribute completely or will it do "as few copies as possible"? (I''d love to know if it''s possible to visualize the fragmentation of a single file.) -- To unsubscribe from this list:

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

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

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

On 2019-09-30 16:09, Erik via Syslinux wrote: > I am new to syslinux/extlinux. Can I boot from a linux btrfs subvolume? I am > getting "Failed to load ldlinux.c32" when I attempt to boot from a btrfs > subvolume. I can confirm this as a problem. The algorithm for btrfs subvolume search seems to be completely braindead, and at least in the current Linux kernels there are ioctls

On Fri, Nov 21, 2014 at 11:46:37AM +0100, Pino Toscano wrote: > On Friday 21 November 2014 13:17:58 Hu Tao wrote: > > Parameter `qgroupid' is for adding the created subvolume to a qgroup. > > > > Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> > > --- > > daemon/btrfs.c | 10 +++++++++- > > generator/actions.ml | 15 ++++++++------- > > 2

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 +++

Parameter `qgroupid' is for adding the created subvolume to a qgroup. Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> --- daemon/btrfs.c | 10 +++++++++- generator/actions.ml | 15 ++++++++------- 2 files changed, 17 insertions(+), 8 deletions(-) diff --git a/daemon/btrfs.c b/daemon/btrfs.c index a20afca..0f525fa 100644 --- a/daemon/btrfs.c +++ b/daemon/btrfs.c @@ -291,7 +291,7 @@

The current code does not cover all subvolume variants. If a subvolume exists which covers the entire root filesystem the result is two mountables that have is_root set. This leads to failures in virt-ls and other tools because they work only with a single root. Update the btrfs subvolume call to use the "-o" option. This fixes two cases: first it skips the subvolume for the root

virt-filesystem -l tries to get the size of btrfs subvolumes, which results in an error. Teach it to skip the subvolumes. --- cat/filesystems.c | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/cat/filesystems.c b/cat/filesystems.c index f1c2852..f679517 100644 --- a/cat/filesystems.c +++ b/cat/filesystems.c @@ -476,9 +476,27 @@ do_output_filesystems

virt-filesystem -l tries to get the size of btrfs subvolumes, which results in an error. Teach it to skip the subvolumes. --- cat/filesystems.c | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/cat/filesystems.c b/cat/filesystems.c index f1c2852..cfdac86 100644 --- a/cat/filesystems.c +++ b/cat/filesystems.c @@ -476,9 +476,28 @@ do_output_filesystems

On Mon, Nov 24, 2014 at 10:26:50AM +0800, Hu Tao wrote: > On Fri, Nov 21, 2014 at 11:46:37AM +0100, Pino Toscano wrote: > > On Friday 21 November 2014 13:17:58 Hu Tao wrote: > > > Parameter `qgroupid' is for adding the created subvolume to a qgroup. > > > > > > Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> > > > --- > > >