fsck.ext4 -cc vs -cck options difference?
by czezz from LinuxQuestions.org on (#4QT83)
I am a bit confused with fsck.ext4 man page.
It says:
Code:-c This option causes e2fsck to use badblocks(8) program to do a read-only scan of the device in order to find any bad blocks. If any bad blocks are found, they are added to the bad block inode to prevent them from being allocated to a file or directory. If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test.
-k When combined with the -c option, any existing bad blocks in the bad blocks list are preserved, and any new bad blocks found by running badblocks(8) will be added to the existing bad blocks list.By using just -c or -cc I understand that the bad blocks are mapped and not used anymore.
However, option -ck or -cck is saying that only then badblocks are preserved.
To me it seems like it overlaps each other.
What is the real difference between usinf -cc and -cck? Anyone can explain that better?
It says:
Code:-c This option causes e2fsck to use badblocks(8) program to do a read-only scan of the device in order to find any bad blocks. If any bad blocks are found, they are added to the bad block inode to prevent them from being allocated to a file or directory. If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test.
-k When combined with the -c option, any existing bad blocks in the bad blocks list are preserved, and any new bad blocks found by running badblocks(8) will be added to the existing bad blocks list.By using just -c or -cc I understand that the bad blocks are mapped and not used anymore.
However, option -ck or -cck is saying that only then badblocks are preserved.
To me it seems like it overlaps each other.
What is the real difference between usinf -cc and -cck? Anyone can explain that better?