On 2017年12月15日 16:36, Ian Kumlien wrote:
> On Fri, Dec 15, 2017 at 6:34 AM, Roman Mamedov <r...@romanrm.net> wrote:
>> On Fri, 15 Dec 2017 01:39:03 +0100
>> Ian Kumlien <ian.kuml...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Running a 4.14.3 kernel, this just happened, but there should have
>>> been another 20 gigs or so available.
>>>
>>> The filesystem seems fine after a reboot though
>>
>> What are your mount options, and can you show the output of "btrfs fi
>> df" and "btrfs fi us" for the filesystem? And what does
>> "cat /sys/block/sdb/queue/rotational" return.
> 
> It's a btrfs raid1 mirror of two ssd:s
> 
> mount options was:
> defaults,acl,noatime,space_cache,autodefrag,compress=lzo
> 
> btrfs fi df /
> Data, RAID1: total=459.25GiB, used=372.42GiB
> Data, single: total=8.00MiB, used=0.00B
> System, RAID1: total=8.00MiB, used=80.00KiB
> System, single: total=4.00MiB, used=0.00B
> Metadata, RAID1: total=6.00GiB, used=3.69GiB

Both meta and data has a lot of space let.

> Metadata, single: total=8.00MiB, used=0.00B
> GlobalReserve, single: total=512.00MiB, used=0.00B
> 
> btrfs fi us /
> Overall:
>     Device size: 930.54GiB
>     Device allocated: 930.53GiB
>     Device unallocated:   20.05MiB
>     Device missing:      0.00B
>     Used: 752.22GiB
>     Free (estimated):   86.84GiB (min: 86.84GiB)
>     Data ratio:       2.00
>     Metadata ratio:       2.00
>     Global reserve: 512.00MiB (used: 0.00B)
> 
> Data,single: Size:8.00MiB, Used:0.00B
>    /dev/sdb2    8.00MiB
> 
> Data,RAID1: Size:459.25GiB, Used:372.42GiB
>    /dev/sdb2 459.25GiB
>    /dev/sdc2 459.25GiB
> 
> Metadata,single: Size:8.00MiB, Used:0.00B
>    /dev/sdb2    8.00MiB
> 
> Metadata,RAID1: Size:6.00GiB, Used:3.69GiB
>    /dev/sdb2    6.00GiB
>    /dev/sdc2    6.00GiB
> 
> System,single: Size:4.00MiB, Used:0.00B
>    /dev/sdb2    4.00MiB
> 
> System,RAID1: Size:8.00MiB, Used:80.00KiB
>    /dev/sdb2    8.00MiB
>    /dev/sdc2    8.00MiB
> 
> Unallocated:
>    /dev/sdb2   24.00KiB
>    /dev/sdc2   20.02MiB

Well, at least no new chunk can be allocated.


In v4.15, Josef introduced a new inode reservation system, which I think
it would enhance metadata related reservation.

If you're hitting the problem quite frequently, please consider to try
v4.15-rc* to see if it solves the problem.

Despite of that, there should be no damage to your fs.
(except some unwritten data in buffer)

Thanks,
Qu

> 
> And as expected:
> cat /sys/block/sdb/queue/rotational
> 0
> 
>> I wonder if it's the same old "ssd allocation scheme" problem, and no
>> balancing done in a long time or at all.
> 
> I had something similar happen on a laptop a while ago - took a while
> before i could get it back in order
> (in that case i think it was actually a oops --- it kept saying "no
> space left" and switched to read only even
> if you removed a lot of data, invalidated the space cache and so on)
> --
> 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
> 

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to