Hi! > Is that considered ok? Should fsck restart itself or report > 'filesystem still has errors' in this case? It definitely should in this case: Free inodes count wrong (22999, counted=23011). Fix? yes delme.fsck.damaged: ***** FILE SYSTEM WAS MODIFIED ***** delme.fsck.damaged: 2053/25064 files (0.1% non-contiguous), 97825/100000 blocks Second check... e2fsck 1.42.12 (29-Aug-2014) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences: +18015 Fix? yes Free blocks count wrong for group #2 (36, counted=35). Fix? yes Free blocks count wrong (2175, counted=2174). Fix? yes delme.fsck.damaged: ***** FILE SYSTEM WAS MODIFIED ***** delme.fsck.damaged: 2053/25064 files (0.2% non-contiguous), 97826/100000 blocks Fsck lied about its success (result = 1) pavel@amd:~/misc$ cp delme.fsck.original-damaged delme.report-2 (I can make the images public. Yes, it is artificial test.) Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
