4 ms·
> would report a successful write to an sd card before it was done. To "help" with speed. Sadly USB sticks are handled the same way. The write notification and
by scns 4y ago
> would report a successful write to an sd card before it was done. To "help" with speed.
Sadly USB sticks are handled the same way. The write notification and progress bar are long gone but you won't be able to eject that medium for several minutes.
Don't remember if it is the same on windows, since i use it rarely.
- remram 4y agoThat's not the same, GP was talking about the hardware lying, not buggy software abstractions that affects measurements but don't lose data. If you commit your database journal, you're told it's done and you start overwriting data, but the journal was never persisted... a loss of power will wreck your entire database.
- eptcyka 4y agoJust run `sync`.
- brnt 4y agoDidn't that not quite do what it says on the tin on some filesystems?
- eptcyka 4y agoIf the syscall meant to flush data to disk doesn't do that due to an implementation detail of a filesystem, I think there's nothing the user can reasonably do to ensure their data is safe.
- zabzonk 4y agoway back when, unix admins were recommended to enter "sync" twice. this wasn't anything wrong with the program itself, but the time it took to enter the second sync gave the os to finish flushing its buffers to the hard disk.
- brnt 4y agoOh, for all my love of Linux, I really hate that bit of shitty UI. Then don't show a transfer bar at all.