***** FILE SYSTEM WAS MODIFIED ***** on e2fsck -c (badblocks check)
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Seems that's just how the command works. The man page suggests that nothing would be changed....
From the Man Page (e2fsck)
-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.
I've run it five times on a filesystem, and always get the same output...
root@hydra(Linux)root$ time e2fsck -vc /dev/sda1
e2fsck 1.39 (29-May-2006)
Checking for bad blocks (read-only test): done
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
/boot: ***** FILE SYSTEM WAS MODIFIED *****
76 inodes used (0.03%)
5 non-contiguous inodes (6.6%)
# of inodes with ind/dind/tind blocks: 44/3/0
32712 blocks used (12.34%)
0 bad blocks
1 large file
63 regular files
0 character device files
0 block device files
1 symbolic link (1 fast symbolic link)
In the source of the latest version 1.42.1 the RELEASE-NOTES tell:
Fix a bug in e2fsck where if the free blocks and inodes counts are
incorrect, e2fsck would fix them without printing an error message.
This would cause a "*** FILE SYSTEM WAS MODIFIED ***" message without
any explanation of what was fixed.
Maybe you hit exactly this. But of course, issuing it several times should show it only once.
In the source of the latest version 1.42.1 the RELEASE-NOTES tell:Maybe you hit exactly this. But of course, issuing it several times should show it only once.
Probably the same cause, but different bug. IIRC, the version in CentOS / RHEL would always update the badblock & free inode count. Even if the numbers are basically unchanged, the "update" flags the "MODIFIED" output to be displayed.