similar to: Re: [PATCH 0/3 V3] btrfs: a new tool to manage a btrfs filesystem

Currently the resize command is under filesystem, and takes a path to the mounted filesystem. This seems wrong to me. Shouldn''t it be under device, and take a path to a device to resize? Otherwise, how can a resize operation when you have multiple devices make any sense? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to

The following series implement a way to generate the help messages and the btrfs man page from the sources comments for the "btrfs" commanda . The syntax and the detailed help of every subcommand are stored in the comments before the function which implements the subcommand. The fact that the help messages and the man page are generated from the same source should help to avoid

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

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

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

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

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

Hi all, the commands "btrfs filesystem show" and "btrfs device scan" look at the /dev directory (and it subdirectories) for every block devices. This is a slow process because floppy and cdrom are also checked. Moreover, as highlighted by Helmut, if udev is not used, the /dev directory is populated by high number of non-existant devices, which slow the process. My patch

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 all, below a configuration for udev/initramfs which I propose to scan the block devices looking for a multi-volume btrfs filesystem. Btrfs has the capability to span a file-system on multiple device. In order to do that, the involved devices have to be "registered" in the kernel. In order to do that there are two options: # btrfs device scan <device> (or the old

Hi Seto, please could you update also the man page too ? Why it was not provided a way to clear a *single* flag ? To me it seems a bit too long to clear all the flag (btrfs mount-option clear) and then set the right one. As user interface I suggest something like chmod: btrfs mount-option set +ssd,skip_balance -nodatacow /dev/sdX or btrfs mount-option set =ssd,skip_balance,nodatacow

Hello, I added a new disk into our RAID5 array, it looks like this: md2 : active raid5 sdd4[3] sde4[4] sda4[0] sdc4[2] sdb4[1] 3767274240 blocks level 5, 64k chunk, algorithm 2 [5/5] [UUUUU] # btrfs fi sh Label: none uuid: 5534d2e7-be31-49c7-8ab7-90c5ab8afe18 Total devices 1 FS bytes used 2.24TB devid 3 size 2.63TB used 2.63TB path /dev/md2 # mount ... /dev/md2 on /home type btrfs

Fedora provides yum-fs-snapshot. If installed, on each package installation or update a snapshot of all btrfs filesystems is taken, so it is possible to revert the installation/update. Suppose an update failed and I want to get back: with # btrfs subvolume set-default yum-snapshot-whatever / I define which snapshot to use at the next boot. After rebooting I decide I really want to stay with

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 |

Hi, I wanted to create a new btrfs fs for my backups. When trying to mkfs.btrfs for that device, I''m getting "error checking /dev/loop2 mount status" With strace I see where the problem is: lstat("/dev/disk/by-id/ata-INTEL_SSDSA2M160G2GC_CVPO939201JX160AGN-par", 0x7fffa30b3cf0) = -1 ENOENT (No such file or directory) The problem is there is something missing

Hi, I am compiling a tiny linux kernel 2.6.10 to be used together with linuxbios. The boot phase will go as follows: linuxbios->tiny linux kernel->initramfs The initramfs shall use dhcp to get it's address and then tftp a full featured kernel. This kernel must be started through kexec. I use a tweaked networkdriver in the kernel and cannot use a normal PXE boot. Which files should I

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:

Hi, I''m hitting this issue - sda5 is a normal device, nothing to do with loop, encryption etc. # mkfs.btrfs /dev/sda5 WARNING! - Btrfs v0.19-35-g1b444cd-dirty IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using error checking /dev/sda5 mount status Is there something I can do to resolve this? Thank you Lubos -- To unsubscribe from this list: send the line

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