On Sat, 2004-11-20 at 22:47 +0100, Gilles Meier wrote:
> I still got the same errors, here are the output from jfs_debug :
> 
> sup :
> 
>  > sup
>  > sup
> [1] s_magic:            'JFS1'       [15] s_ait2.addr1:      0x00
> [2] s_version:          1            [16] s_ait2.addr2:      0x00001d3a
> [3] s_size:     0x000000001d1b09b0        s_ait2.address:    7482
> [4] s_bsize:            4096         [17] s_logdev:          0x00000000
> [5] s_l2bsize:          12           [18] s_logserial:       0x00000000
> [6] s_l2bfactor:        3            [19] s_logpxd.len:      8192
> [7] s_pbsize:           512          [20] s_logpxd.addr1:    0x00
> [8] s_l2pbsize:         9            [21] s_logpxd.addr2:    0x03a368b0
> [9] pad:                Not Displayed     s_logpxd.address:  61040816
> [10] s_agsize:          0x00080000   [22] s_fsckpxd.len:     1914
> [11] s_flag:            0x10200900   [23] s_fsckpxd.addr1:   0x00
>                          JFS_LINUX    [24] s_fsckpxd.addr2:   0x03a36136
>          JFS_COMMITJFS_GROUPCOMMIT         s_fsckpxd.address: 61038902
>                       JFS_INLINELOG   [25] s_time.tv_sec:     0x419cc59c
>                                       [26] s_time.tv_nsec:    0x00000000
>                                       [27] s_fpack:           ''
> [12] s_state:           0x00000000
>               FM_CLEAN
> [13] s_compress:        0
> [14] s_ait2.len:        4

This looks sane, but the size of the partition needed would be
238472.6875 MB.  ((Address of logpxd * length of logpxd) * 4K)  The
output from parted indicates that the size of the partition would be
238433.21 MB.  There isn't an easy way to shrink the file system by 40
MB, but you may be able to extend the partition using parted.

>  > sup s
> [1] s_magic:            '    '       [15] s_ait2.addr1:    0xff
> [2] s_version:          0            [16] s_ait2.addr2:    0xffffffff
> [3] s_size:     0x0000000000004000        s_ait2.address: 1099511627775
> [4] s_bsize:            256          [17] s_logdev:        0xffffffff
> [5] s_l2bsize:          8            [18] s_logserial:     0xffffffff
> [6] s_l2bfactor:        0            [19] s_logpxd.len:      16777215
> [7] s_pbsize:           85           [20] s_logpxd.addr1:    0xff
> [8] s_l2pbsize:         4            [21] s_logpxd.addr2:    0xffffffff
> [9] pad:                Not Displayed     s_logpxd.address:1099511627775
> [10] s_agsize:          0xffffff05   [22] s_fsckpxd.len:     16777215
> [11] s_flag:            0xffffffff   [23] s_fsckpxd.addr1:   0xff
>        JFS_OS2 JFS_LINUX           [24] s_fsckpxd.addr2:   0xffffffff
>        JFS_COMMIT      JFS_GROUPCOMMIT   s_fsckpxd.address:1099511627775
>          JFS_LAZYCOMMIT  JFS_INLINELOG[25] s_time.tv_sec:     0xffffffff
>          JFS_BAD_SAIT    JFS_SPARSE   [26] s_time.tv_nsec:    0xffffffff
>          DASD_ENABLED    DASD_PRIME   [27] s_fpack:     
> 'ïïïïïïïïïïï'
> [12] s_state:           0xffffffff
>          Unknown State
> [13] s_compress:        -1
> [14] s_ait2.len:        16777215

This does look bad, which can mean that the file system is further
damaged.  But if the primary superblock is good, the secondary isn't
looked at.
-- 
Dave Kleikamp
IBM Linux Technology Center
[EMAIL PROTECTED]

_______________________________________________
Jfs-discussion mailing list
[EMAIL PROTECTED]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion

Reply via email to