Re: read-only for no good reason on 4.9.30

2017-09-05 Thread Chris Murphy
On Sun, Sep 3, 2017 at 11:19 PM, Russell Coker wrote: > I have a system with less than 50% disk space used. It just started rejecting > writes due to lack of disk space. What's the error? Is it ENOSPC? Kinda needs kernel messages, and also if it's ENOSPC to have mounted with enospc_debug option.

Re: read-only for no good reason on 4.9.30

2017-09-04 Thread Peter Grandi
> [ ... ] I ran "btrfs balance" and then it started working > correctly again. It seems that a btrfs filesystem if left > alone will eventually get fragmented enough that it rejects > writes [ ... ] Free space will get fragmented, because Btrfs has a 2-level allocator scheme (chunks within devices

Re: read-only for no good reason on 4.9.30

2017-09-04 Thread Henk Slager
On Mon, Sep 4, 2017 at 7:19 AM, Russell Coker wrote: > I have a system with less than 50% disk space used. It just started rejecting > writes due to lack of disk space. I ran "btrfs balance" and then it started > working correctly again. It seems that a btrfs filesystem if left alone will > eve

read-only for no good reason on 4.9.30

2017-09-03 Thread Russell Coker
I have a system with less than 50% disk space used. It just started rejecting writes due to lack of disk space. I ran "btrfs balance" and then it started working correctly again. It seems that a btrfs filesystem if left alone will eventually get fragmented enough that it rejects writes (I've