Re: btrfs forced readonly + errno=-28 No space left

2016-04-25 Thread Martin Svec
Dne 22.4.2016 v 23:00 Nicholas D Steeves napsal(a): > On 21 April 2016 at 18:44, Chris Murphy wrote: >> On Thu, Apr 21, 2016 at 6:53 AM, Martin Svec wrote: >>> Hello, >>> >>> we use btrfs subvolumes for rsync-based backups. During backups btrfs

Re: btrfs forced readonly + errno=-28 No space left

2016-04-25 Thread Martin Svec
Dne 22.4.2016 v 0:44 Chris Murphy napsal(a): > On Thu, Apr 21, 2016 at 6:53 AM, Martin Svec wrote: >> Hello, >> >> we use btrfs subvolumes for rsync-based backups. During backups btrfs often >> fails with "No space >> left" error and goes to readonly mode (dmesg output is

Re: btrfs forced readonly + errno=-28 No space left

2016-04-22 Thread Nicholas D Steeves
On 21 April 2016 at 18:44, Chris Murphy wrote: > On Thu, Apr 21, 2016 at 6:53 AM, Martin Svec wrote: >> Hello, >> >> we use btrfs subvolumes for rsync-based backups. During backups btrfs often >> fails with "No space >> left" error and goes to

Re: btrfs forced readonly + errno=-28 No space left

2016-04-21 Thread Chris Murphy
On Thu, Apr 21, 2016 at 6:53 AM, Martin Svec wrote: > Hello, > > we use btrfs subvolumes for rsync-based backups. During backups btrfs often > fails with "No space > left" error and goes to readonly mode (dmesg output is below) while there's > still plenty of > unallocated

RE: btrfs forced readonly + errno=-28 No space left

2016-04-21 Thread E V
>we use btrfs subvolumes for rsync-based backups. During backups btrfs often >fails with "No >space >left" error and goes to readonly mode (dmesg output is below) while there's >still plenty of >unallocated space I have the same use case and the same issue with no real solution that I've found.