[rtiangha]

For what it's worth, the files in frostschutz's installer and instructions still work on my Glo HD running 3.19.5761. But I didn't run it; I cloned my SD card and while it was still plugged into my Linux machine, I copied his two scripts into rootfs's /sbin directory, and formatted my KOBOeReader partition into ext4 using the default options in gparted (remember, the Glo HD doesn't have an external sd card reader).

Calibre on Ubuntu wouldn't detect the device when connected by default, though. I had to mount the partition first before opening Calibre. And because of permissions (when I first mounted the partition through the file explorer, the permissions on the directory were set to root), I couldn't write anything to it either by default; I went into /media/user/ and changed owner and group to me, and I ran chmod 777 on the directory as well, just in case.

I'm using a 64GB sdcard, my device database is 600MB+ and I have over 3800 books and the file system change definitely made a difference for me. Boot up is so much faster and sending metadata to the device, getting the list of books on the device and backing up the database through Calibre is faster too, sometimes by a factor of two. Keep in mind though that this is through Linux; using an ext driver on Windows or OSX might perform worse than if it were still using FAT32.

Some things seem to lag on the device itself sometimes too, it seems, for example, tapping on something *sometimes* seems to take a smidge longer to display than it did using FAT32. That could be because of the journaling, or maybe it's just psychological (or maybe I just haven't used it long enough). Powering off takes a bit longer too (I assume to sync the journal first before unmounting and shutting down). I'll play around with it a bit more and if I'm feeling motivated, might try running ext2 or ext3 or maybe just ext4 without journaling enabled to see how it performs. But the increase in speed for me with just the file transfers and device operations between it and my Linux machine alone make me strongly consider keeping the device this way. It used to take me 10-15 minutes to sync my device and its large collection with my Linux machine through Calibre and that time was cut in half using ext4. So to me, it's worth it (and again, boot up from Power Off state is so much faster now).

That said, I wonder if it's possible to modify frostschutz's dosfsck script to either probe the partition to figure out what it's formatted with and run the proper utility, or to run e2fsck instead if dosfsck fails, so that way, it wouldn't matter to the device what file system that partition is formatted in (let the Kobo assume it's still FAT32) and will run the disk check whenever it needs to run a disk check under normal operations. Seems kind of silly to have a journaled file system if the device won't file check it every so often (assuming Kobo hard coded it to do that to the FAT32 partition once in a while), although to be fair, I don't know under what circumstances the Kobo would call dosfsck in the first place. Hopefully it would do it on regular intervals or whenever it detects issues with the file system.