Runs fsck agressively on sdcard

[vpelletier]

How to reproduce:

• get an sdcard (vfat-formated)
• put files with broken short names (for some reason, this happens with asus T700F on latest firmware)
• put sdcard in kobo
• get kobo to notice the corruption (I could not reliably reproduce this, happened once when changing margins while having an ebook opened, another time just when changing page)

Result: All ebooks from the sdcard (supposedly all with corrupted short names) are renamed, and cannot be read without fixing the SD card content from another device.

What is expected: On FS corruption, kobo should just warn that there is a problem with the sd card and refuse to modify it further (remount read-only). Optionally, kobo should expose more SD card controls: format, eject (=umount), and display when it detects an inserted sdcard (otherwise it's quite difficult to tell what's going on when ebooks just disappear).

[edit] This was noticed on a new koboglo, freshly set up: 2.2.1 (r44772, 09/11/12) [/edit]

[gtalusan]

Hi Vincent

If you upgrade to the latest firmware for your Kobo Touch/Glo/Mini then fsck is already run on the SD card.

On 2012-11-30, at 1:05 AM, Vincent Pelletier notifications@github.com wrote:

How to reproduce:

get an sdcard (vfat-formated) put files with broken short names (for some reason, this happens with asus T700F on latest firmware) put sdcard in kobo get kobo to notice the corruption (I could not reliably reproduce this, happened once when changing margins while having an ebook opened, another time just when changing page) Result: All ebooks from the sdcard (supposedly all with corrupted short names) are renamed, and cannot be read without fixing the SD card content from another device.

What is expected: On FS corruption, kobo should just warn that there is a problem with the sd card and refuse to modify it further (remount read-only). Optionally, kobo should expose more SD card controls: format, eject (=umount), and display when it detects an inserted sdcard (otherwise it's quite difficult to tell what's going on when ebooks just disappear).

\ Reply to this email directly or view it on GitHub.

[vpelletier]

It is run, yes, and this is an issue in my opinion. I would prefer it to:

• tell me there was something wrong with the sdcard
• maybe, offer me the possibility to run fsck and/or mkfs on it

In the same feature vein:

• give the possibility to eject the card safely (my corruption case was external to the kobo, but I guess it can easily be caused by the kobo if the card is removed at the wrong time)
• display a notification that an sdcard was indeed detected: until I had access to another device to read the sdcard, I could not tell whether the kobo did not detect it or it was detected but without anything usable in it. such notification icon could easily carry also the "sdcard present, but there is something wrong so I'm not reading it" hint I mentioned above

Just for the record, after getting access to a computer to copy files to a fresh mkfs'ed sdcard, the card works perfectly in the kobo, several books, sync and dictionaries install later. I am very happy of my kobo glo now that I overcame the two issues I reported on this tracker.