similar to: Still Problems with /dev/btrfs-control

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, Let me know if this is the wrong place to ask... I''m using Fedora 12 x86_64, mostly with the newer 21.6.32 kernel, and have a single btrfs filesystem within a 120Gb partition. I''d like to extend the space btrfs can use. One option is presumably add a new device to btrfs, but I was hoping to simple resize the existing partition to say 160Gb. With ext4 I might do

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

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

Hello, I''ve just pulled btrfs-progs from the new git repo git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git However, when I come to make it fails like so: gcc -Wp,-MMD,./.btrfsctl.o.d,-MT,btrfsctl.o -Wall -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -g -Werror -Os -c btrfsctl.c gcc -g -Werror -Os -o btrfsctl btrfsctl.o ctree.o disk-io.o radix-tree.o extent-tree.o

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

[root@btrfs progs-unstable]# btrfsctl -A /dev/sdb ioctl returns 0 [root@btrfs progs-unstable]# btrfsctl -A /dev/sdc ioctl returns 0 /dev/sdb has a btrfs, while /dev/sdc is blank. What''s that output supposed to mean ? Is it a bug ? -- 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

E.g. btrfsctl -r -4000m /dev/sda5 results in: ioctl:: Inappropriate ioctl for device Distribution: Ubuntu 10.10 Kernel: 2.6.35-22-generic According to the Synaptic Package manager, the version of btrfs-tools is 0.19+20100601-3 Other information that can be of interest: - I started Ubuntu on a live CD - before invoking the btrfsctl command I invoked apt-get update. I have googled but have not

Conclusion: DO NOT USE SOFTWARE RAID-1 WITH EXT3 I've started with this conclusion cause i am positive that raid-1 and ext3 are causing data corruption. I've upgraded from 7.1 to 7.2 and from the first date i run into data corruption problems @ least once per day (i was monitoring once per day only) after 7 days we bought a brand new server cause the previous was very old and i thought

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

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 |

Good afternoon btrfs, I have been having issues with snapshots not reading the whole file tree below them. I have installed new btrfs-progs from git://git.darksatanic.net/repo/btrfs-progs-unstable.git made and installed them. My tree is: /Btrfs | |__ nfs1 | |__ data |

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

In snapshot destroy the dentry used for parent was the snapshot dentry itself. Remove d_invalidate since always return EBUSY, making possible to remove a snapshot using the btrfsctl -D option. Signed-off-by: Rui Miguel Silva <rmfrfs@gmail.com> --- fs/btrfs/ioctl.c | 7 ++----- 1 files changed, 2 insertions(+), 5 deletions(-) diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c index

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

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

I found userspace tool, btrfsctl, uses BTRFS_VOL_NAME_MAX, and it also looks that this one is more proper. Kill BTRFS_PATH_NAME_MAX since no one will use it. Signed-off-by: WANG Cong <wangcong@zeuux.org> Cc: Chris Mason <chris.mason@oracle.com> --- diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c index c2aa33e..f229950 100644 --- a/fs/btrfs/ioctl.c +++ b/fs/btrfs/ioctl.c @@ -472,7

Hi all, I am using a single volume across two devices sdb7 and sda1, initially created on sdb7, and added sda1 using btrfs-vol later. The fstab entry: /dev/disk/by-id/scsi-SATA_ST31000333AS_9TE12DSC-part7 /mnt/btrfs btrfs defaults 1 2 Now after boot I get: ---- device fsid c4822885057410c-d2d65a83c2f15fb4 devid 1 transid 73034 /dev/sdb7 btrfs: failed to read chunk tree on sdb7 ---- So I have

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 man/btrfsctl.8.in Signed-off-by: Goldwyn Rodrigues <rgoldwyn@gmail.com> --- man/btrfsctl.8.in | 45 +++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 45 insertions(+), 0 deletions(-) create mode 100644 man/btrfsctl.8.in diff --git a/man/btrfsctl.8.in b/man/btrfsctl.8.in new file mode 100644 index 0000000..e11f46a --- /dev/null +++ b/man/btrfsctl.8.in @@ -0,0 +1,45 @@