On Thu, Dec 19, 2019 at 3:34 PM Remi Gauvin <remi@xxxxxxxxxxxxxx> wrote: > > On 2019-12-19 4:43 p.m., Chris Murphy wrote: > > It's bogus. > > > >> # Free (estimated): 134.13GiB (min: 134.13GiB) > > > Perhaps not. > > Lots of free space, but it's *all* allocated. > > > # Device size: 7.27TiB > # Device allocated: 7.27TiB > > Metadata,DUP: Size:21.50GiB, Used:14.31GiB > # /dev/<mydev> 43.00GiB > # > # System,DUP: Size:8.00MiB, Used:864.00KiB > # /dev/<mydev> 16.00MiB > > # Unallocated: > # /dev/<mydev> 1.00MiB > True. The more recent cases of enospc seem to happen with plenty of unused space in allocated block groups available. As is the case here. It's possible a newer kernel will produce helpful error reporting, and additionally mount with enospc_debug mount option. -- Chris Murphy
