fsck on ext3 after 20 mounts reports i_blocks=n should be m

fsck on ext3 after 20 mounts reports i_blocks=n should be m

[bert hubert]

Hi people,

My laptop which runs 2.5.6 today decided to fsck / because it had been
mounted 20 times. During those 20 times I think it had in the order of 5
unclean shutdowns (empty battery mostly), all of them running 2.5.6
according to 'last'.

The fsck reports, from what I can recall:

inode X i_blocks=n, should be m. FIXED

About 8 of these. M is always smaller than n. The difference appeared to be
always a multiple of 8. One case was '32, should be 24'. Another was '80,
should be 8'. Larger differences were reported too.

The fs appears to work just fine though. If there is any other information
you need, just let me know.

# tune2fs -l /dev/hda1
tune2fs 1.27 (8-Mar-2002)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          0a30dec8-3356-43a6-a9cd-f26e86fc5321
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal filetype needs_recovery sparse_super
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              611648
Block count:              1220932
Reserved block count:     61046
Free blocks:              167112
Free inodes:              455973
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16096
Inode blocks per group:   503
Last mount time:          Fri Apr  5 23:45:33 2002
Last write time:          Fri Apr  5 23:45:33 2002
Mount count:              1
Maximum mount count:      20
Last checked:             Fri Apr  5 23:45:22 2002
Check interval:           15552000 (6 months)
Next check after:         Wed Oct  2 23:45:22 2002
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:		  128
Journal UUID:             <none>
Journal inode:            351
Journal device:	          0x0000
First orphan inode:       36051

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO

Re: fsck on ext3 after 20 mounts reports i_blocks=n should be m

[Kurt Roeckx]

On Fri, Apr 05, 2002 at 11:56:47PM +0200, bert hubert wrote:
> Hi people,
> 
> My laptop which runs 2.5.6 today decided to fsck / because it had been
> mounted 20 times. During those 20 times I think it had in the order of 5
> unclean shutdowns (empty battery mostly), all of them running 2.5.6
> according to 'last'.
> 
> The fsck reports, from what I can recall:
> 
> inode X i_blocks=n, should be m. FIXED

This happens when your fs was full.  Andrew Morton mailed a patch
to the list a few days ago.


Kurt

Re: fsck on ext3 after 20 mounts reports i_blocks=n should be m

[bert hubert]

On Sat, Apr 06, 2002 at 02:11:09AM +0200, Kurt Roeckx wrote:

> > The fsck reports, from what I can recall:
> > 
> > inode X i_blocks=n, should be m. FIXED
> 
> This happens when your fs was full.  Andrew Morton mailed a patch
> to the list a few days ago.

Thank you. It had indeed been full. 

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO