similar to: multi-device btrfs volumes

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

I am a relative newcomer to using extlinux. I am running Fedora 20 which means I am using syslinux 4.05. When I noticied that all of your documentation said that booting off ext234 and btrfs was supported, I gave it a try. Indeed, this does work with the boot files and the extlinux directory installed into the btrfs (root) volume. Has any thought been given to supporting supporting

Hi, I know btrfs complicates filesystem lists due to the use of subvolumes. However, I just noticed that the root partition itself ends up being listed twice with list-filesystems, inspect-os, inspect-get-roots, etc... I'm seeing this in version 1.26, but haven't found anything directly resolving this in newer versions. These commands all show the partition listed twice as in the

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

I notice this question on the wiki/faq: https://btrfs.wiki.kernel.org/index.php/UseCases#What_is_best_practice_when_partitioning_a_device_that_holds_one_or_more_btr-filesystems and as it hasn''t been answered, can anyone make any comments on the subject Various things come to mind: a) partition the disk, create an LVM partition, and create lots of small LVs, format each as btrfs b)

Hello everyone. Please, find the patch for Fedora 10 in the attachment(**). The distro-independent package will be put to kernel.org a bit later. I. Loading kernels from btrfs volumes Now you can load kernels and initrds from btrfs volumes composed of many devices. WARNING!!! Make sure that all components of your loading btrfs volume(*) are visible to grub. Otherwise,

I was under the impression that the value of /etc/machine-id was unqiue for every OS installation on a system. This seems to be the case on real hardware. That is, if I install Fedora 19, Fedora 20, and Fedora-rawhide on a system, they will each have a different value for /etc/machine-id. This does not seem to be the case for qemy-kvm-libvirt virtual systems. SOmetimes they are different

I''m wondering if anyone might have any suggestions... We''ve installed CentOS5.2 on 3 servers and have an FC switch, dual-port cards, and FC RAID device. We configured the RAID as two separate logical RAIDs. One is RAID-10 for speed and it hosts Xen VM images as LVs. The rest of the drive is RAID-5 to maximize space and houses a lot of lighter access data on a GFS2 filesystem.

I believe what I am going to write is a bug report. When I finaly did # btrfs send -v /mnt/adama-docs/backups/20130101-192722 | btrfs receive /mnt/tmp/backups to migrate btrfs from one partition layout to another. After a while system keeps saying that "Too many open files in system" and denies access to almost every command line tool. When I had access to iostat I confirmed the

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

I''m currently researching an upgrade to (raid1-ed) btrfs from mostly reiserfs (which I''ve found quite reliable (even thru a period of bad ram and resulting system crashes) since data=ordered went in with 2.6.16 or whatever it was. (Thanks, Chris! =:^)) on multiple md/raid-1s. I have some questions that don''t appear to be addressed well on the wiki, yet, or where

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

We have a problem with btrfs subvolumes, as they can hold a filesystem which can be mounted, but aren't describable using only the name of a block device. Specifically they need at least a block device and a subvolume name. There are several APIs which operate on filesystems which currently describe it using only a block device. I've listed them all below. In all cases, these APIs need

This testscript creates reflinks to files on different subvolumes, overwrites the original files and reflinks, and moves reflinked files between subvolumes. Originally submitted as testcase 302, changes are made based on comments from Eric: http://oss.sgi.com/archives/xfs/2013-03/msg00231.html Two new common/rc functions used in this script (_require_cp_reflink and _verify_reflink) have been

We've currently got a bug in libguestfs which means we can't inspect filesystems in btrfs subvolumes: https://bugzilla.redhat.com/show_bug.cgi?id=824021 This is the default configuration if you select btrfs in F17+. The issue is that it requires an api to fix it, as the return values of inspect_os, inspect_get_filesystems and inspect_get_mountpoints can't express a btrfs

On Friday 17 October 2014 11:25:03 Olaf Hering wrote: > On Thu, Oct 16, Olaf Hering wrote: > > I can probably add a check somewhere to catch the whatever=="@". A > > better fix would be to check if a given subvolume is for the entire > > partition. > > So after talking to David Sterba there is no way to tell if a given > subvolume is for the entire

Mark Haney wrote: > On 09/07/2017 01:57 PM, hw wrote: >> >> Hi, >> >> is there anything that speaks against putting a cyrus mail spool onto a >> btrfs subvolume? >> > I might be the lone voice on this, but I refuse to use btrfs for anything, much less a mail spool. I used it in production on DB and Web servers and fought corruption issues and scrubs

Hello, recently I installed a distribution I want to look at via chroot into a btrfs subvolume on a multidevice btrfs. Now I tried to boot this, the kernel command line in GRUB looks as follows so far: /kernel-2.6.29-rc7-git3 root=/dev/sdb7 rootfstype=btrfs rootflags=device=/dev/sda1,subvol=archroot This gives "VFS: cannot find sdb7 or bad block", like it would when trying to mount