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

Re: [Linux-cluster] Unformatting a GFS cluster disk




Hi Bob,


We now have gfs2_edit up and running and have been able to get an idea of how the ondisk structure works.. We are modifying values as you suggest then running fsck. We are finding that after running fsck the values we have modified have been reverted back to before our change..

Maybe we're changing the wrong thing? Here's what we are doing.. Is this something like the right track?


 
-------------
 
number of Resource Groups: 584
 
# gfs2_edit -p rindex /san2/sda.backup |more
-----------
RG #1
 ri_addr               0                   0x0
 ri_length             0                   0x0
 ri_data0              0                   0x0
 ri_data               0                   0x0
 ri_bitbytes           65827               0x10123
-----------

 

RG#1 - rsrc grp hdr 65827

 
before editing:
Block #65827    (0x10123)     of 39321600 (0x2580000)  (rsrc grp hdr)
(p.1 of 6)
10123000 01161970 00000002 00000000 00000000 [...p............]
10123010 000000C8 00000000 00000000 0000FFF8 [................]
10123020 00000000 00000000 00000000 00000000 [................]
10123030 00000000 00000000 00000000 00000000 [................]
10123040 00000000 00000000 00000000 00000000 [................]
10123050 00000000 00000000 00000000 00000000 [................]
10123060 00000000 00000000 00000000 00000000 [................]
10123070 00000000 00000000 00000000 00000000 [................]
10123080 00000000 00000000 00000000 00000000 [................]
10123090 00000000 00000000 00000000 00000000 [................]
101230A0 00000000 00000000 00000000 00000000 [................]

 
updated:
Block #65827    (0x10123)     of 39321600 (0x2580000)  (rsrc grp hdr)
(p.1 of 6)
10123000 01161970 00000002 00000000 00000000 [...p............]
10123010 000000C8 00000000 00000000 0000FFF8 [................]
10123020 0000FFFF 00000000 00000000 00000000 [................]
10123030 00000000 00000000 00000000 00000000 [................]
10123040 00000000 00000000 00000000 00000000 [................]
10123050 00000000 00000000 00000000 00000000 [................]
10123060 00000000 00000000 00000000 00000000 [................]
10123070 00000000 00000000 00000000 00000000 [................]
10123080 FFFFFFFF FFFFFFFF 00000000 00000000 [................]
10123090 00000000 00000000 00000000 00000000 [................]
101230A0 00000000 00000000 00000000 00000000 [................]

 
 
 
ran fsck after used inodes value update, results:
 
[...]
ondisk and fsck bitmaps differ at block 66276
Succeeded.
ondisk and fsck bitmaps differ at block 66277
Succeeded.
ondisk and fsck bitmaps differ at block 66278
Succeeded.
ondisk and fsck bitmaps differ at block 66279
Succeeded.
RG #2 used inode count inconsistent: is 65528 should be 0




Regards,
Damon.
Working to protect human rights worldwide

DISCLAIMER
Internet communications are not secure and therefore Amnesty International Ltd does not accept legal responsibility for the contents of this message. If you are not the intended recipient you must not disclose or rely on the information in this e-mail. Any views or opinions presented are solely those of the author and do not necessarily represent those of Amnesty International Ltd unless specifically stated. Electronic communications including email might be monitored by Amnesty International Ltd. for operational or business reasons.

This message has been scanned for viruses by Postini.
www.postini.com





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