Because of the bad superblocks.  My testing hadn't produced this error so
I assumed something was wrong.  At this point I tried to recover.

On 11/13/10 2:26 AM, "JoKoT3" <[email protected]> wrote:

>Hello,
>
>Why haven't you used resize2fs ?
>
>
>
>On Sat, Nov 13, 2010 at 2:43 AM, Syn, Joonho <[email protected]> wrote:
>
>> Apologies in advance for the long mail:
>> 2 mail servers running these services via heartbeat
>> -mount by label mail-store
>> -shared ip
>> -postfix
>> -http
>> -mailman
>>
>> was attempting to increase the size of the shared partition using the
>>below
>> procedure but when trying to fsck the disk I got bad superblocks.
>>
>> -stop heartbeat services on standby node
>> -stop heartbeat services on active node (which should stop all services
>>in
>> order, including unmounting of the shared partition)
>> -increase size of partition on san
>> -rescan iscsi node on standby node
>> -rescan iscsi node on formerly active node
>> -remove the journal of the ext3 partition "tune2fs ­O ^has_journal [my
>> device]"
>> -delete and recreate the partition using fdisk
>> -check the newly expanded partition for errors "fsck ­n [my device]
>>
>> At this point the fsck returned a "bad superblock error".  I tested
>>using a
>> similar setup but without heartbeat and did not get any corruption.  Any
>> ideas as to what led to my bad superblocks?
>> _______________________________________________
>> Linux-HA mailing list
>> [email protected]
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
>>
>
>
>
>-- 
>Jonathan Gibert
>System & Network Engineer
>Linagora Professional Services
>http://www.linagora.com
>_______________________________________________
>Linux-HA mailing list
>[email protected]
>http://lists.linux-ha.org/mailman/listinfo/linux-ha
>See also: http://linux-ha.org/ReportingProblems

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to