3 ms·
That's shameful negligence. There's no reason the drive shouldn't be fully consistent seconds after activity on the drive goes idle. What responsible driver wri
by JoeAltmaier 11y ago
That's shameful negligence. There's no reason the drive shouldn't be fully consistent seconds after activity on the drive goes idle. What responsible driver writer would leave uncommitted blocks indefinitely!
Said as a driver writer who always commits blocks on an activity one-shot.
- sp332 11y agoWho said anything about "indefinitely"? It's very possible for a user to pull out the drive within seconds after hitting "save" - or even at the same time.
- JoeAltmaier 11y agoEverybody in the thread were talking about 'indefinitely' - you are forced to hit 'eject' to safely remove USB storage. This is required even if its many seconds or minutes after use.
- deleted 11y ago[deleted]
- sp332 11y agoHm, I thought that was just in case some other process was using the disk. I mean most of the time, you can yank a FAT32-formatted drive out without losing data.
- JoeAltmaier 11y agoOthers on the thread report otherwise. I'm with you; I will take my drive when I'm done, and never am going to ask 'mother may I'. If it fails, I'll file a bug report. Its a minimum standard of function in my viw.