Skip to main content

Thread: Fsck question


when run read-only fsck on root filesystem errors:

code:
warning!  /dev/sda1 mounted.  warning: skipping journal recovery because doing read-only filesystem check.  /dev/sda1 contains file system errors, check forced.  pass 1: checking inodes, blocks, , sizes  deleted inode 4456450 has 0 dtime.  fix? no    inodes part of corrupted orphan linked list found.  fix? no    inode 4456451 part of orphaned inode list.  ignored.  inode 4456452 part of orphaned inode list.  ignored.  inode 4456453 part of orphaned inode list.  ignored.  inode 4456454 part of orphaned inode list.  ignored.  pass 2: checking directory structure  pass 3: checking directory connectivity  pass 4: checking reference counts  pass 5: checking group summary information  free blocks count wrong (18294656, counted=18294353).  fix? no    inode bitmap differences:  -(4456450--4456454)  fix? no    free inodes count wrong (4781350, counted=4781340).  fix? no      /dev/sda1: ********** warning: filesystem still has errors **********    /dev/sda1: 109274/4890624 files (0.2% non-contiguous), 1242752/19537408 blocks
but i've rebooted server , forced filecheck of root:


read-only fsck still reports errors after reboot. question. can read-only filecheck trusted?

if @ image of boot fsck of root filesystem there's no text of being 'clean'. mean it's not?

no, it's not clean, based on output every time fsck asked if should fix errors or not told not fix them...


Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [all variants] Fsck question


Ubuntu

Comments

Popular posts from this blog

Thread: Can not create raid array: mdadm: no raid-devices specified.

Thread: HOW TO: Package and theme GTK+ / Gtkmm apps in Linux for Windows

Thread: Twinview issues