similar to: Resizing a btrfs managed partition

Thanks for the quick reply! But I still have problems with btrfsctl: > stat /dev/btrfs-control File: `/dev/btrfs-control'' Size: 0 Blocks: 0 IO Block: 4096 block special file Device: ch/12d Inode: 659848 Links: 1 Device type: a,3e Access: (0644/brw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2010-01-09 11:31:15.757979602 +0100

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

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, I have two guest vm instance running CentOS 5 with ext3 partition. I will like to reduce 1 VM harddisk space and using the 'release' harddisk space to add onto my second VM. Basically I need to know how can I reduce and increase an ext3 partition in CentOS KVM. I did a search and basically i can do it by booting the VM using Knoppix and use Gparted to reduce and increase the

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 All, I feel this is the most simple question but I am currently going around and round in circles and searches keep bringing me up Windows tools!! :-( I have a 512MB USB drive that has a 12MB FAT16 partition on it. How can I resize this 12MB partition to grow and fill the whole 512MB drive? Just in case I am being stupid, here is what I am doing... :-) I would like a quick USB drive that

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

Greetings - I had a logical volume that was running out of space on a virtual machine. I successfully expanded the LV using lvextend, and lvdisplay shows that it has been expanded. Then I went to expand the filesystem to fill the new space (# resize2fs -p /dev/vde1) and I get the results that the filesystem is already xx blocks long, nothing to do. If I do a # df -h, I can see that the

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

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, I was wondering if there was a way to extend (ie: grow) a PV that is part of a Volume Group? I currently have a partition on my HD that is being used as a PV for my Volume Group, but would like to make it larger. I have the space on my drive to extend my partition, but using standard tools (ex: gparted, Partition Magic, etc) would likely end up corrupting the data on in the Logical Volumes

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

[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

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

I''ve filed this bug under util-linux, because I think wipefs isn''t deleting all btrfs metadata it could. But ultimately it appears to be a btrfs bug because nothing else sees the stale volume. https://bugzilla.redhat.com/show_bug.cgi?id=889888#c15 btrfs-progs-0.20.rc1.20121017git92d9eec-1.fc18.x86_64 e2fs-progs-1.42.5-1.fc18.x86_64 kernel 3.7.1-2 Brand new 80GB virtual disk,

On Sun, 07 June 2015 at 14:14 zulu, Robert Nichols wrote: > It's generally recommended to use Windows tools to do NTFS re-sizing. I tend to disagree with that advice... I would recommend http://gparted.org/livecd.php over the microsoft-supplied tools, in a heartbeat. Boot off that Live image on a CD or thumbdrive (or use the version of GPartEd included with the System Rescue Live CD

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

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

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

Can anybody tell me if quota information is journaled ? After bad-shutdown the quota info is correctly or I need run quotacheck ?