>> Is it some kind of NVMe temp garbage overhead? No, it's a problem at the ntfs-3g level, not the NVMe level.
> Possibly. I haven't been following the thread very attentively and have no > particular expertise, but maybe you are running to an issue similar to > the one described in the link below where the garbage collection of the > NVMe's internal index of space usage doesn't happen fast enough: > > https://github.com/FOGProject/fogproject/issues/421#issuecomment-1507351213 That comment is very confused about the way SSDs work: all that garbage-collection work is completely hidden (save for their performance effects). The error message you see can be found in https://github.com/tuxera/ntfs-3g/blob/edge/libntfs-3g/mft.c but I'm not sufficiently familiar with NTFS nor with that code to figure out what's really going on. >From what I could find, the MFT (Master File Table) sounds similar to a table of inodes, and it should grow as needed, so it seems like "no free mft record" should never occur, but maybe that's not implemented in ntfs-3g or something? I suggest you file it as a bug report with the ntfs-3g guys. Stefan
