On Tue, May 26, 2015 at 06:08:20PM +, Hugo Mills wrote:
> > The btrfs filesystem on my newly installed laptop has managed to
> > hose itself rather thoroughly, and it's now in a state where it
> > works okay if you don't write too much to it, but if you do, it
> > starts returning -ENOSPC on a
On Tue, May 26, 2015 at 12:50 PM, Calvin Walton
wrote:
> On Tue, 2015-05-26 at 12:18 -0600, Chris Murphy wrote:
>> Oh yeah easy to miss, but obvious once pointed out:
>>
>> > Data, single: total=227.94GiB, used=58.16GiB
>>
>> I thought we had automatic deallocation of unused chunks but I guess
>>
On Tue, 26 May 2015 12:18:40 -0600, Chris Murphy wrote:
> Oh yeah easy to miss, but obvious once pointed out:
>
>> Data, single: total=227.94GiB, used=58.16GiB
>
> I thought we had automatic deallocation of unused chunks but I guess
> it hasn't landed yet.
It did (in 3.18 IIRC), but that doesn'
On Tue, 2015-05-26 at 12:18 -0600, Chris Murphy wrote:
> Oh yeah easy to miss, but obvious once pointed out:
>
> > Data, single: total=227.94GiB, used=58.16GiB
>
> I thought we had automatic deallocation of unused chunks but I guess
> it hasn't landed yet.
We do have automatic deallocation of un
Oh yeah easy to miss, but obvious once pointed out:
> Data, single: total=227.94GiB, used=58.16GiB
I thought we had automatic deallocation of unused chunks but I guess
it hasn't landed yet.
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a m
On Tue, May 26, 2015 at 08:36:34PM +0300, Lennert Buytenhek wrote:
> Hi!
>
> The btrfs filesystem on my newly installed laptop has managed to
> hose itself rather thoroughly, and it's now in a state where it
> works okay if you don't write too much to it, but if you do, it
> starts returning -ENOS
On Tue, May 26, 2015 at 11:50:00AM -0600, Chris Murphy wrote:
> Before wiping I suggest making an image with btrfs-image. And then
> also see if any additional messages appear with the enospc_debug mount
> option. And also see if there's any correlation between the journald
> reported failures (th
Before wiping I suggest making an image with btrfs-image. And then
also see if any additional messages appear with the enospc_debug mount
option. And also see if there's any correlation between the journald
reported failures (the specific .journal file) and whether it's +C by
using lsattr. Fedora 2
Hi!
The btrfs filesystem on my newly installed laptop has managed to
hose itself rather thoroughly, and it's now in a state where it
works okay if you don't write too much to it, but if you do, it
starts returning -ENOSPC on a random subset of your filesystem
operations until you let it cool down
