Re: Oops in btrfs_recover_relocation, kernel 4.8.1

2017-03-11 Thread Hugo Mills
On Fri, Mar 10, 2017 at 12:23:37PM +, Hugo Mills wrote: >Does anyone recall seeing this oops before? Is it something that > can be fixed with a newer kernel? (I'm on a USB stick for this, so a > new kernel is a major undertaking, and I'd like some reasonable > expectation of success if I do

btrfs send non-root

2017-03-11 Thread Sam Bull
I'm getting an error when trying to send a subvolume. I only seem to be able to do this as root. The subvolume was created by the user account, and not root. Could anybody shed some light on why this is failing? Is there a way to get it working? $ btrfs send /var/spool/backups/hacking/2017-03-10 >

Question re. required since btrfs-progs-4.10

2017-03-11 Thread Holger Hoffstätte
Hi, I'm on Gentoo and wanted to update Docker to 17.03.0, which failed when it couldn't build the btrfs driver due to a missing . This worked fine on another machine the other day, so I dug in and found that the only difference was an intermediate update to btrfs-progs 4.10. Sure enough: since 4.1

[PATCH v2] qgroup: Retry after commit on getting EDQUOT

2017-03-11 Thread Goldwyn Rodrigues
From: Goldwyn Rodrigues We are facing the same problem with EDQUOT which was experienced with ENOSPC. Not sure if we require a full ticketing system such as ENOSPC, but here is a fix. Let me know if it is too big a hammer. Quotas are reserved during the start of an operation, incrementing qg->re

[PATCH] qgroup: Change qgroup_meta_rsv to 64bit

2017-03-11 Thread Goldwyn Rodrigues
From: Goldwyn Rodrigues Using an int value is causing qg->reserved range checks to be triggered, and incorrect accounting. This affects exclusive qgroups only. TEST CASE: DEVICE=/dev/vdb MOUNTPOINT=/mnt SUBVOL=$MOUNTPOINT/tmp umount $SUBVOL umount $MOUNTPOINT mkfs.btrfs -f $DEVICE mount /dev