From Blink-Dev: Daniel Bratell: > Just curious, what happens if someone tries to exploit this by writing very far ahead? Austin Sullivan: > Great question, Daniel. This was brought up in the GitHub issue which requested this feature (https://github.com/WICG/file-system-access/issues/262#issuecomment-771601594). I'll quote the response by mek@: > Behavior wise it should be no different than calling truncate with a very large size to resize the file. For files in the origin private file system either operation will fail with a quota exceeded error (since the empty space is still counted against quota). For files on the local file system, I imagine it does indeed depend on the underlying file system implementation. It is my understanding that pretty much every major file system today supports sparse files transparently (ntfs, apfs, and most linux file systems), although I haven't tested how exactly they behave. I don't think this will reveal more of the underlying system then other operations already do. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/600#issuecomment-779670310
Received on Tuesday, 16 February 2021 08:26:11 UTC