LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices

Reply
 
Search this Thread
Old 03-16-2012, 02:33 PM   #1
alpha01
Member
 
Registered: Jul 2008
Location: Orange County
Distribution: Ubuntu/Debian, CentOS, RHEL, FreeBSD, OS X
Posts: 75

Rep: Reputation: 19
***** FILE SYSTEM WAS MODIFIED ***** on e2fsck -c (badblocks check)


Hello,

Does anyone know why a "FILE SYSTEM WAS MODIFIED" message gets displayed every time I run a badblocks check in any of our unmounted Logical Volume partition?

Code:
[root@server ~]# e2fsck -c /dev/mapper/Vol-Log-t
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
 
/t: ***** FILE SYSTEM WAS MODIFIED *****
/t: 1693444/62226432 files (2.0% non-contiguous), 66853179/124446720 blocks
 
Old 03-18-2012, 12:06 AM   #2
xeleema
Member
 
Registered: Aug 2005
Location: D.i.t.h.o, Texas
Distribution: Slackware 13.x, rhel3/5, Solaris 8-10(sparc), HP-UX 11.x (pa-risc)
Posts: 987
Blog Entries: 4

Rep: Reputation: 249Reputation: 249Reputation: 249
Greetingz!

Seems that's just how the command works. The man page suggests that nothing would be changed....

From the Man Page (e2fsck)
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.
I've run it five times on a filesystem, and always get the same output...
Code:
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
       3 directories
       0 character device files
       0 block device files
       0 fifos
       0 links
       1 symbolic link (1 fast symbolic link)
       0 sockets
--------
      67 files

real    0m12.99s
user    0m0.09s
sys     0m0.46s
 
Old 03-18-2012, 09:04 AM   #3
Reuti
Senior Member
 
Registered: Dec 2004
Location: Marburg, Germany
Distribution: openSUSE 13.1
Posts: 1,320

Rep: Reputation: 252Reputation: 252Reputation: 252
In the source of the latest version 1.42.1 the RELEASE-NOTES tell:
Quote:
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.
 
Old 03-19-2012, 05:27 AM   #4
xeleema
Member
 
Registered: Aug 2005
Location: D.i.t.h.o, Texas
Distribution: Slackware 13.x, rhel3/5, Solaris 8-10(sparc), HP-UX 11.x (pa-risc)
Posts: 987
Blog Entries: 4

Rep: Reputation: 249Reputation: 249Reputation: 249
Quote:
Originally Posted by Reuti View Post
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.
 
Old 03-22-2012, 05:35 PM   #5
alpha01
Member
 
Registered: Jul 2008
Location: Orange County
Distribution: Ubuntu/Debian, CentOS, RHEL, FreeBSD, OS X
Posts: 75

Original Poster
Rep: Reputation: 19
Thanks for the feedback guys. I feel much confident now that it's not a hard drive issue.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How to check the last modified time of the file. anandg111 Linux - Newbie 5 01-05-2012 04:55 PM
Please help me write shell script to check the modified date of a file. thinhnguyenduy79 Linux - Newbie 1 06-17-2011 04:14 AM
smbclient check file modified before 'get' hattori.hanzo Linux - Newbie 1 10-28-2010 09:09 AM
[SOLVED] Root file sys check on JFS during boot fails with e2fsck message catkin Slackware 2 02-21-2010 05:29 AM
When and how to use e2fsck and badblocks Silly22 Linux - Newbie 5 05-29-2002 03:28 PM


All times are GMT -5. The time now is 06:36 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration