On 22.11.2016 15:16 Martin Raiber wrote: > ... > Interestingly, > after running "btrfs check --repair" "df" shows 0 free space (Used > 516456408 Available 0), being inconsistent with the below other btrfs > free space information. > > btrfs fi usage output: > > Overall: > Device size: 512.00GiB > Device allocated: 512.00GiB > Device unallocated: 1.04MiB > Device missing: 0.00B > Used: 492.03GiB > Free (estimated): 19.59GiB (min: 19.59GiB) > Data ratio: 1.00 > Metadata ratio: 2.00 > Global reserve: 512.00MiB (used: 326.20MiB) > > Data,single: Size:507.98GiB, Used:488.39GiB > /dev/mapper/LUKS-CC-9a6043feb9d946269555a71ec0742c8b 507.98GiB > > Metadata,DUP: Size:2.00GiB, Used:1.82GiB > /dev/mapper/LUKS-CC-9a6043feb9d946269555a71ec0742c8b 4.00GiB > > System,DUP: Size:8.00MiB, Used:80.00KiB > /dev/mapper/LUKS-CC-9a6043feb9d946269555a71ec0742c8b 16.00MiB > > Unallocated: > /dev/mapper/LUKS-CC-9a6043feb9d946269555a71ec0742c8b 1.04MiB Looking at the code, it seems df shows zero if the available metadata space is smaller than the used global reserve. So this file system might be out of metadata space.
smime.p7s
Description: S/MIME Cryptographic Signature
