[DRBD-user] fsck problem
deborah.ellis at lmco.com
Thu Jan 19 21:02:44 CET 2006
Thank Diego, I will try it
From: Diego Julian Remolina [mailto:diego.remolina at ibb.gatech.edu]
Sent: Thursday, January 19, 2006 2:31 PM
To: jlarrea at gadisa.es
Cc: Ellis, Deborah; drbd-user at linbit.com
Subject: Re: [DRBD-user] fsck problem
I had a similar problem when I first started working with drbd long ago, and it was due to the fact
that I had formated the partition on the real device and not the drbd device. This occurs
specifically if you are using internal metadata.
If you are using internal metadata, then you should format the drbd partition again so that things
work fine and the last 128MB of the partition are kept untouch for the metadata.
1. Backup all data to another partition
2. With drbd up format the drbd partition mke2fs -j /dev/drbdX
-j if you want ext3.
3. put all data back in the partition.
That should take care of it.
jlarrea at gadisa.es wrote:
> Are you fsck'ing the physical device or the /dev/drbdx device?
> -----drbd-user-bounces at lists.linbit.com escribió: -----
> >Para: drbd-user at linbit.com
> >De: "Ellis, Deborah"
> >Enviado por: drbd-user-bounces at lists.linbit.com
> >Fecha: 19/01/2006 16:15
> >Asunto: [DRBD-user] fsck problem
> >I installed drbd and am using the tool LifeKeeper to do a manual
> >failover of nfs from 1 server to another server. The drbd-drbd0
> >fails over, but I get an error message that states that there is a
> >bad superblock on /dev/drbd0. I then run fsck on the device and get
> >the following message
> >The file sysem size( according to the superblock) is 2441494 blocks
> >The physical size of the device is 2408726 blocks
> >Either the superblock or partition table is likely to be corrupt!
> >Do you have any idea on how to fix this problem?
> >Thanks in advance for your help
> >drbd-user mailing list
> >drbd-user at lists.linbit.com
> drbd-user mailing list
> drbd-user at lists.linbit.com
More information about the drbd-user