qcow2 becomes 37P in size while qemu crashes

2016-07-22 Thread Chris Murphy
Here is the bug write up so far, which contains most of the relevant details. https://bugzilla.redhat.com/show_bug.cgi?id=1359325 Here are three teasers to get you to look at the bug: 1. [root@f24m ~]# ls -lsh /var/lib/libvirt/images total 57G 1.5G -rw-r-. 1 qemu qemu 1.5G Jul 21 10:54

Re: Send-recieve performance

2016-07-22 Thread Libor Klepáč
Hello, Dne pátek 22. července 2016 14:59:43 CEST, Henk Slager napsal(a): > On Wed, Jul 20, 2016 at 11:15 AM, Libor Klepáč wrote: > > Hello, > > we use backuppc to backup our hosting machines. > > > > I have recently migrated it to btrfs, so we can use send-recieve for > >

Re: [PATCH 1/2] Btrfs: be more precise on errors when getting an inode from disk

2016-07-22 Thread J. Bruce Fields
On Fri, Jul 22, 2016 at 12:40:26PM +1000, NeilBrown wrote: > On Fri, Jul 22 2016, J. Bruce Fields wrote: > > > On Fri, Jul 22, 2016 at 11:08:17AM +1000, NeilBrown wrote: > >> On Fri, Jun 10 2016, fdman...@kernel.org wrote: > >> > >> > From: Filipe Manana > >> > > >> > When we

Re: [PATCH] btrfs-progs: Make RAID stripesize configurable

2016-07-22 Thread Austin S. Hemmelgarn
On 2016-07-22 12:06, Sanidhya Solanki wrote: On Fri, 22 Jul 2016 10:58:59 -0400 "Austin S. Hemmelgarn" wrote: On 2016-07-22 09:42, Sanidhya Solanki wrote: +*stripesize=*;; +Specifies the new stripe size for a filesystem instance. Multiple BTrFS +filesystems mounted in

Re: [PATCH] btrfs-progs: Make RAID stripesize configurable

2016-07-22 Thread Sanidhya Solanki
On Fri, 22 Jul 2016 10:58:59 -0400 "Austin S. Hemmelgarn" wrote: > On 2016-07-22 09:42, Sanidhya Solanki wrote: > > +*stripesize=*;; > > +Specifies the new stripe size for a filesystem instance. Multiple BTrFS > > +filesystems mounted in parallel with varying stripe size

Re: [PATCH] btrfs-progs: Make RAID stripesize configurable

2016-07-22 Thread Austin S. Hemmelgarn
On 2016-07-22 09:42, Sanidhya Solanki wrote: Adds the user-space component of making the RAID stripesize user configurable. Updates the btrfs-documentation to provide the information to users. Adds parsing capabilities for the new options. Adds the means of transfering the data to kernel space.

Re: Send-recieve performance

2016-07-22 Thread Martin Raiber
On 20.07.2016 11:15 Libor Klepáč wrote: > Hello, > we use backuppc to backup our hosting machines. > > I have recently migrated it to btrfs, so we can use send-recieve for offsite > backups of our backups. > > I have several btrfs volumes, each hosts nspawn container, which runs in > /system

Re: [PATCH] btrfs: Change RAID stripesize to a user-configurable option

2016-07-22 Thread Sanidhya Solanki
Applies to v4.7rc7 release kernel. Sanidhya -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[PATCH] btrfs: Change RAID stripesize to a user-configurable option

2016-07-22 Thread Sanidhya Solanki
Adds the kernel component of making the RAID stripesize user configurable. Updates the kernel ioctl interface to account for new options. Updates the existing implementations of RAID stripesize in metadata. Make the stripesize an user-configurable option. Convert the existing metadata option of

[PATCH] btrfs-progs: Make RAID stripesize configurable

2016-07-22 Thread Sanidhya Solanki
Adds the user-space component of making the RAID stripesize user configurable. Updates the btrfs-documentation to provide the information to users. Adds parsing capabilities for the new options. Adds the means of transfering the data to kernel space. Updates the kernel ioctl interface to account

Re: Send-recieve performance

2016-07-22 Thread Henk Slager
On Wed, Jul 20, 2016 at 11:15 AM, Libor Klepáč wrote: > Hello, > we use backuppc to backup our hosting machines. > > I have recently migrated it to btrfs, so we can use send-recieve for offsite > backups of our backups. > > I have several btrfs volumes, each hosts nspawn

[PATCH] btrfs: do not background blkdev_put()

2016-07-22 Thread Anand Jain
From: Anand Jain At the end of unmount/dev-delete, if the device exclusive open is not actually closed, then there might be a race with another program in the userland who is trying to open the device in exclusive mode and it may fail for eg: unmount /btrfs; fsck