Description
These lines happen during the NtReadFile/NtWriteFile apitests on testbot and in various other conditions.
Root cause (at least in the case of these tests) is that the FS reduces file size to 0 before uninitializing the cache for deleted files. The flushing writes are then rejected by fastfat as invalid because they are past the end of the file.
Attachments
Issue Links
- blocks
-
CORE-6931 Fastfat doesn't support FILE_DELETE_ON_CLOSE flag
- Resolved