View Single Post
Old 08-16-2011, 03:46 AM   #94
rjcroy
Bibliophile
rjcroy ought to be getting tired of karma fortunes by now.rjcroy ought to be getting tired of karma fortunes by now.rjcroy ought to be getting tired of karma fortunes by now.rjcroy ought to be getting tired of karma fortunes by now.rjcroy ought to be getting tired of karma fortunes by now.rjcroy ought to be getting tired of karma fortunes by now.rjcroy ought to be getting tired of karma fortunes by now.rjcroy ought to be getting tired of karma fortunes by now.rjcroy ought to be getting tired of karma fortunes by now.rjcroy ought to be getting tired of karma fortunes by now.rjcroy ought to be getting tired of karma fortunes by now.
 
rjcroy's Avatar
 
Posts: 167
Karma: 1147338
Join Date: Jun 2010
Location: New Zealand
Device: Sony PRS-T3, Kobo Touch
Quote:
Originally Posted by cutterjohn42 View Post
Yep, AFAIC it's a borked fw, as in someone is likely not closing files properly. In the Google dev blogs they ended up writing up an entire section as to how devs should open/close files and dbs and also part of the reason that they are switching to ext4 in newer releases top hopefully, help mitigate some of these problems.
... I download EVERYTHING over WiFi, through the browser plus IIRC when I was xferring stuff I just pulled the uSD and used my nb's builtin card reader.
This is a good point, like p_a_smith, etc.
It was the ext4 story that made me lean toward the unmounting as the cause in the first place. Certainly ext4 has made programmers who relied on the 5 second flush of ext3 to clean up their act.

But if your Kobo internal flash has not been written to by another computer then it can't be external app like ADE or Calibre or Kobo Desktop causing the file corruption.
rjcroy is offline   Reply With Quote