On Tue, Jan 14, 2025 at 09:48:36AM -0500, Stefan Monnier wrote: > > After running for several hours, it refused to continue due to "no space > > left on device". > > I've confirmed the problem trying to save a text file there, same error. > > Hmm... I don't see anything amiss in the data you sent, so I'm afraid > I don't know what's going on. Have you tried to delete one of the files > you just wrote (just to see if other modifications still work, > rather than the system behaving as if it's read-only)?
Thing is, if I've been following along correct, a "touch" in this state also returns ENOSPC. So either the file system is in a funny state, or the ntfs driver has some limitations this side of NTFS. Two things might be interesting: - anything in the kernel logs while the error happens? - does the ENOSPC also happen when appending to one of the files on that file system (this might help to discriminate between "too many entries" or "not enough available space")? > Any message about your NVMe device (or its filesystem) in dmesg? Yep: kernel messages would be the next interesting thing. Cheers -- t
signature.asc
Description: PGP signature
