Problem with file system

Thu Oct 25 11:35:28 UTC 2007

Hi Chris,

I unmounted /dev/sda2 and ran fsck.ext3. this was the complete o/p
===========================

root at 172:/root> fsck.ext3 /dev/sda2  -v -n
e2fsck 1.40.2 (12-Jul-2007)
/dev/sda2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 1505 has imagic flag set.  Clear? no
Inode 1505, i_blocks is 2561936855, should be 0.  Fix? no
Inode 15393 has compression flag set on filesystem without compression
support.  Clear? no
Deleted inode 164029 has zero dtime.  Fix? no
Inode 1463073 is in use, but has dtime set.  Fix? no
Inode 1463073 has imagic flag set.  Clear? no
Inode 1463073 has compression flag set on filesystem without compression
support.  Clear? no
Inode 1463073 has INDEX_FL flag set but is not a directory.
Clear HTree index? no
HTREE directory inode 1463073 has an invalid root node.
Clear HTree index? no
Error reading block 4294967295 (Invalid argument).  Ignore error? no
HTREE directory inode 1463073 has an invalid root node.
Clear HTree index? no
HTREE directory inode 1463073 has an invalid root node.
Clear HTree index? no
Inode 1463073, i_blocks is 4294967295, should be 0.  Fix? no
Deleted inode 1685409 has zero dtime.  Fix? no
Inode 1835553 is in use, but has dtime set.  Fix? no
Inode 1835553 has illegal block(s).  Clear? no
Illegal block #0 (310724603) in inode 1835553.  IGNORED.
Illegal block #1 (837540054) in inode 1835553.  IGNORED.
Illegal block #2 (3716133180) in inode 1835553.  IGNORED.
Illegal block #3 (2359092648) in inode 1835553.  IGNORED.
Illegal block #4 (155050197) in inode 1835553.  IGNORED.
Illegal block #5 (2295681145) in inode 1835553.  IGNORED.
HTREE directory inode 1835553 has an invalid root node.
Clear HTree index? no
Error reading block 310724603 (Invalid argument).  Ignore error? no
HTREE directory inode 1835553 has an invalid root node.
Clear HTree index? no
HTREE directory inode 1835553 has an invalid root node.
Clear HTree index? no
Inode 1835553 is a zero-length directory.  Clear? no
Inode 1835553, i_size is 1155516870, should be 0.  Fix? no
Inode 1835553, i_blocks is 2500161256, should be 0.  Fix? no

Pass 2: Checking directory structure
Entry 'pdf_fontmgr_cidfonttypes.ps'
in /SYSROM_SRC/mfp/PRF/rbdisk0/PostScript (1835102) has an incorrect
filetype (was 1, should be 2).
Fix? no
Directory inode 1835553 has an unallocated block #6.  Allocate? no
Directory inode 1835553 has an unallocated block #7.  Allocate? no
Directory inode 1835553 has an unallocated block #8.  Allocate? no
Directory inode 1835553 has an unallocated block #9.  Allocate? no
Directory inode 1835553 has an unallocated block #10.  Allocate? no
Directory inode 1835553 has an unallocated block #11.  Allocate? no

Pass 3: Checking directory connectivity
'..'
in /SYSROM_SRC/mfp/PRF/rbdisk0/PostScript/pdf_fontmgr_cidfonttypes.ps
(1835553) is <The NULL inode> (0), should
be /SYSROM_SRC/mfp/PRF/rbdisk0/PostScript (1835102).
Fix? no

Pass 4: Checking reference counts
Inode 1505 (...) is an illegal socket.
Clear? no
Unattached inode 1505
Connect to /lost+found? no
Unattached zero-length inode 10209.  Clear? no
Unattached inode 10209
Connect to /lost+found? no
Inode 15393 (...) has invalid mode (0177777).
Clear? no
Unattached inode 15393
Connect to /lost+found? no
Inode 16673 (...) has invalid mode (0177777).
Clear? no
Unattached inode 16673
Connect to /lost+found? no
Inode 32801 (...) has invalid mode (0177777).
Clear? no
Unattached inode 32801
Connect to /lost+found? no
Inode 33313 (...) has invalid mode (0177777).
Clear? no
Unattached inode 33313
Connect to /lost+found? no
Inode 49185 (...) has invalid mode (0177777).
Clear? no
Unattached inode 49185
Connect to /lost+found? no
Inode 49697 (...) has invalid mode (0177777).
Clear? no
Unattached inode 49697
Connect to /lost+found? no
Inode 65569 (...) has invalid mode (0177777).
Clear? no
Unattached inode 65569
Connect to /lost+found? no
Inode 66081 (...) has invalid mode (0177777).
Clear? no
Unattached inode 66081
Connect to /lost+found? no
Inode 1463073 (...) has invalid mode (00).
Clear? no
Unattached inode 1463073
Connect to /lost+found? no
WARNING: PROGRAMMING BUG IN E2FSCK!
        OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[1835553] is 44779, inode.i_links_count is 1.  They
should be the same!
Inode 1835553 ref count is 1, should be 1.  Fix? no

Pass 5: Checking group summary information
Block bitmap differences:  -(305650--305665) -359594 -(359611--360268)
-(3701464--3701466)
Fix? no
Inode bitmap differences:  +1505 +10209 +15393 +16673 +32801 +33313
+49185 +49697 +65569 +66081 -164029 +1463073
Fix? no
Directories count wrong for group #112 (17, counted=18).
Fix? no

/dev/sda2: ********** WARNING: Filesystem still has errors **********

   15162 inodes used (0.50%)
      81 non-contiguous inodes (0.5%)
         # of inodes with ind/dind/tind blocks: 1370/52/0
  605645 blocks used (10.05%)
       0 bad blocks
       1 large file

   11831 regular files
     886 directories
       0 character device files
       0 block device files
       0 fifos
4294967294 links
    2436 symbolic links (2414 fast symbolic links)
       0 sockets
--------
   15150 files

Here is the log from tail /var/log/kern.log
=============================================

Oct 25 17:16:53 172 kernel: [  267.117373] attempt to access beyond end
of device
Oct 25 17:16:53 172 kernel: [  267.117396] sda2: rw=0, want=13777058744,
limit=48195000
Oct 25 17:16:53 172 kernel: [  267.117404] attempt to access beyond end
of device
Oct 25 17:16:53 172 kernel: [  267.117411] sda2: rw=0, want=16416658088,
limit=48195000
Oct 25 17:16:53 172 kernel: [  267.117419] attempt to access beyond end
of device
Oct 25 17:16:53 172 kernel: [  267.117425] sda2: rw=0, want=15853339616,
limit=48195000
Oct 25 17:16:53 172 kernel: [  267.117432] attempt to access beyond end
of device
Oct 25 17:16:53 172 kernel: [  267.117439] sda2: rw=0, want=30048438328,
limit=48195000

-
Ameet

On Thu, 2007-10-25 at 12:05 +0200, Christian Kujau wrote:
> Ameet,
> 
> On Thu, October 25, 2007 11:18, Ameet Nanda wrote:
> > The error I got after tar runs for sometime was :
> 
> Please post the errors from your system log (usually /var/log/messages,
> /var/log/kern.log or the like).
> 
> > on doing a fsck.ext3 i get the result as:
> > --------------------------------------------------------------
> > /dev/sda2: ********** WARNING: Filesystem still has errors **********
> 
> Did you unmount /dev/sda2 before running fsck.ext3? Please do, and then
> post the *whole* output of the "fsck.ext3 -v" run, not just the results.
> 
> C.