similar to: Suggestion for sticky-compression mount setting (default mount options)

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 create two subvolumes (meego_root and meego_home) in btrfs root directory. And set meego_root as default mount subvolume. After we remount btrfs, meego_root is mounted to top directory by default. Then when we try to mount meego_home (subvol=meego_home) to a subdirectory, it failed. The problem is when default mount subvolume is set to meego_root, we search meego_home in meego_root but can not

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

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

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

I was looking through some of the archives and notice a patch submitted to implement: btrfs subvolume show <path-to-subvolume> command. I also noticed that is does not appear to be in the git. This looks like a useful capability. I was trying to find out what the UUID was for a newly created subvolume and have not found out how to do that. Gene -- To unsubscribe from this

Hello, We are using btrfs filesystems in our infrastructure and, at some point of time, they start refusing to create new subvolumes. Each file system is being quota initialized immediately after its creation (with "btrfs quota enable") and then all subfolders under the root directory are created as subvolumes (btrfs subvolume create). Over time, these subvolumes may also be

Glück Auf! I use now kernel 3.2. The filesystem was originally created under 2.6.39 on 1 whole hdd, mounted with "noatime,nodiratime,inode_cache". I use it for backups: rsync the whole system to a subvolume, snapshot it and then delete some tempfiles in the snapshot, which are 90% of the full-backup, all once a day. In figures: on this 1 TB hdd is the full-backup with around 600 GiB 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:

Alex pointed out the consequences after a transaction is not committed when a subvolume is deleted, so in case of a crash before an actual commit happens will let the subvolume reappear. Original post: http://www.spinics.net/lists/linux-btrfs/msg22088.html Josef''s objections: http://www.spinics.net/lists/linux-btrfs/msg22256.html While there''s no need to do a full commit for

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. petrb@bots-bnr1:/mnt$ btrfs subvolume delete ext2_saved/ Delete subvolume ''/mnt/ext2_saved'' ERROR: cannot delete ''/mnt/ext2_saved'' this is not really very descriptive. It would be really cool if it told me why it can''t delete it. For example: Permission denied. Cannot delete ... Disk write error. Cannot delete Descriptive error messages

Hi, a recent Ubuntu upgrade killed my system. Luckily I had done a btrfs snapshot before, so I set the particular subvolume as default using # btrfs subvolume set-default 261 /mnt from a rescue system and was back up in no time. I then mounted the original volume with subvolid=0 and repaired it. So far so good. However, I fail to set the default volume back to the original. # btrfs subvolume

I''m wondering is space really freed after deleting large subvolume? Will space be immediately available to other data like other subvolumes? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Hi Everyone, Recently i created a snapshot of an existing volume which had some amount of data. Now that after creating the snapshot i have tried deleting the same snapshot. But i am getting ENOTEMPTY for "rmdir". But when i see the actual files inside are deleted not the parent directory. From the code it looks like if (inode->i_size >

Good morning Btrfs list, I am trying to create a subvolume of a directory tree (approximately 1.1 million subvolumes under nfs1). The following error is thrown and without the wiki I don''t know what argument is needed. I am running kernel 3.1.0-rc4. [root@btrfs ~]# btrfs sub snapshot /btrfs/nfs1/ /btrfs/snaps/ Invalid arguments for subvolume snapshot [root@btrfs ~]# btrfs sub list

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

As of the latest updates to anaconda and grub2 for Fedora 18, it is now possible to install with /boot as a btrfs subvolume. The way that grub2 is handling this is the "reach down" to the files it needs as if the subvolume was a directory. Is this OK? At this point I am not worried about snapshots or any other complexities. If the subvolume name is known. should grub2 be able to

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 |