[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Invalid superblock after e2fsck



Hi,

I have the original filesystem (on a logical volume) "intact" because I've
always worked on snapshots.

The filesystem has less than 2^31 blocks. This system has been correctly
running for four years and corruption become because of a hardware problem
with a SAN device.

The output of dumpe2fs -h /dev/storage/cabina is:

dumpe2fs 1.41.9 (22-Aug-2009)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          607db553-3dc2-4304-9059-37eb99f1047b
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal resize_inode filetype sparse_super
large_file
Filesystem flags:         signed_directory_hash 
Default mount options:    (none)
Filesystem state:         clean with errors
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              1038548992
Block count:              2077085696
Reserved block count:     0
Free blocks:              220295654
Free inodes:              1004004295
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      877
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16384
Inode blocks per group:   512
Filesystem created:       Fri Jul  7 16:45:37 2006
Last mount time:          Wed Jan 20 11:53:00 2010
Last write time:          Thu Feb 11 10:16:13 2010
Mount count:              65
Maximum mount count:      35
Last checked:             Sat Jul 15 05:53:09 2006
Check interval:           15552000 (6 months)
Next check after:         Thu Jan 11 04:53:09 2007
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          128
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      94a8b51f-6ba4-484d-bb92-167cb75c3eb6
Journal backup:           inode blocks
Journal size:             32M

Thanks you!

> What is the blocksize of your filesystem?  RHEL4 should be safe for
> 2^31 blocks, which -should- get you to 8T at 4k blocks.
> 
> dumpe2fs -h info would show us (long as you have an intact superblock
> somewehre...)
> 
> But if you were beyond 2^31 blocks I imagine you'd have hit troubles
early
> on.
> 
> -Eric

-- 
  Albert Sellarès        GPG id: 0x13053FFE
  http://www.wekk.net    whats jabber org   
  Linux User: 324456


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]