With a DATA_ONLY or NONE_ONLY device, metadata overcommits against
chunks that cannot be allocated: once the other devices are full the
transaction aborts with ENOSPC, the filesystem goes read-only, and
-writes that had returned success but were not yet committed are lost.
+files whose writes had returned success but were not fsynced are lost.
With a METADATA_ONLY device nothing is lost, because data reservations
never overcommit and the write fails with ENOSPC; only df Avail is too
high. The patch shares the hint rules between the allocator and the
chunks. Write 64 MiB files until ENOSPC, then create 2000-byte files
from four writers until each gets ENOSPC, sync, balance the metadata,
remount and read everything back. Without the patch the metadata fill
-aborts the transaction and the files created since the last commit are
-lost; with it the fill ends in ENOSPC and every file reads back.
+aborts the transaction and files that were not fsynced are lost; with
+it the fill ends in ENOSPC and every file reads back.
Switching the third device to DATA_ONLY after the data fill gives the
same abort and loss. With the third device METADATA_ONLY instead, the
data fill ends in a clean ENOSPC either way, but without the patch df
metadata to a clean ENOSPC. Classification: **ENOSPC transaction abort with loss of acked data**
(corrected 2026-11-12; the 10-18 text said "not loss of acked data").
The 24125 lost files were created, written and closed with success
-returns but never fsynced, and were not yet committed when the first
-abort hit. A plain write() that returned success is acked, so this is
+returns but never fsynced (whether a commit had covered them was not
+recorded; measurement pending, 2026-11-12). A plain write() that returned success is acked, so this is
silent loss of acked data, the outcome patch 12 prevents. What survived:
every data file synced before the metadata phase (43/43) verifies, and no
file that had been fsynced or covered by a completed sync was lost. Mechanism, from the code: the per-profile available