Thread: [Announce] CSSU Testing thread
View Single Post
yarda is offline yarda
2015-06-19 , 14:06
Posts: 28 | Thanked: 46 times | Joined on Dec 2014
#1815
Originally Posted by yarda View Post

2) Also fsck runs on boot on user data and card which delays the boot process a bit. I always shut down the phone through the power button and I don't touch battery / open the phone after the shut down. The filesystem doesn't seem to be corrupt - the fsck from the bootmenu doesn't reveal anything. The same for fsck through USB mass storage (mass storage initiated from the bootmenu). I will also try to remove the card and run fsck on the external machine, but I doubt it helps.
I get to it after while and I think I know where the problem is. The fsck run is now enforced in /etc/default/mount-opts, there is:

Code:
# Call fsck -p for /home at boot time in /etc/event.d/rcS-late
home_fsck="1"

# Call fsck -p for user's partitions (MyDocs, SD cards, ...)
user_fsck="1"
This can slow down the mount process a bit if there are a lot of user files. E.g. from the fsck.logs (/var/log/fsck*):

Code:
2015-06-19 08:47:52  fsck -a /dev/mmcblk1p1
fsck 1.42.5 (29-Jul-2012)
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
/dev/mmcblk1p1: 3073 files, 800191/1942867 clusters

2015-06-19 08:44:08  fsck -a /home
fsck 1.42.5 (29-Jul-2012)
/dev/mmcblk0p2: clean, 34345/131072 files, 390163/524288 blocks
Checking nearly 40000 files on both partitions slows down the boot process and prolongs the mounting/availability of both partitions to about 5 minutes.

Isn't this default settings overkill? There is already mount check in the rcS-late and if the mount command fails, it runs the fsck. So why to enforce it on each boot?
 

The Following 2 Users Say Thank You to yarda For This Useful Post: