Quote:
Originally Posted by knc1
Good point.
That would in effect defeat the policy of setting aside "root only" file system space to recover from "space exhusted" errors.
|
That point (that everything runs as 'root', eating up the reserved area) remains as one possible cause of the common 'bricking' troubles.
The following is not from the Kindle Touch, the following is the file system image that is posted as an 'Upgrade' to v-3.2.1 for the Kindle 2 and Kindle DX.
That post sort of died when the U.S. Department of Justice siezed megaupload.com - no need to go looking for it, it isn't there any longer. Their new site banner tells why.
It can not show what settings where done by the re-packager and what where done by Amazon when the image was created, it does show an example of what to look for.
Code:
knoppix:k321$ tune2fs -l /dev/loop1
tune2fs 1.41.12 (17-May-2010)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 96b81823-9626-43b1-a98b-a8085e28e614
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal needs_recovery
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Unknown (continue)
Filesystem OS type: Linux
Inode count: 13464
Block count: 409600
Reserved block count: 16384
Free blocks: 40056
Free inodes: 9287
First block: 1
Block size: 1024
Fragment size: 1024
Blocks per group: 8112
Fragments per group: 8112
Inodes per group: 264
Inode blocks per group: 33
Last mount time: Mon Feb 20 17:19:00 2012
Last write time: Mon Feb 20 17:19:00 2012
Mount count: 392
Maximum mount count: -1
Last checked: Thu Jan 1 00:00:33 1970
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Journal backup: inode blocks
The file system is externally named "ext2" - but it is not, it is "ext3" with a dirty journal that needs to be recovered.
It has never been file checked nor the journal recovered.
The automatic checking triggers by number of mounts or elapased time are both disabled.
The reserved area for user id 'root' is disabled.
The reserved area for group id 'root' is disabled.
My own, personal opinion -
I would clean up that file system and re-set the reserved areas before I used it to "upgrade" anything I own. But that is just myself thinking out loud.
Note: I had to make two, one line, changes to my copy of the "Kindle Update Tool" python script to open that posted package, the changes should be obvious to anyone else who has a copy that does not support this package code.
The main subject of this thread was about the Kindle Touch problems -
So if some one with access to the KT file system image would do the same check and look for the same sort of problems....