View Single Post
Old 11-08-2020, 09:19 PM   #26
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,462
Karma: 27757440
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Not using flush for removable storage devices is an *extremely* bad idea. It means it becomes much for likely there is data corruption if the device is accidentally removed, connection interrupted. I'm afraid I am not going to add special support for this to calibre. This bug is anyway a bug in the Kindle firmware/linux kernel, not calibre. Adding a utime() call after fsync is the extent of the workaround I am willing to implement for itin calibre.
kovidgoyal is online now   Reply With Quote