Mailing List Archive: DRBD: Users

drbd error?

Index | Next | Previous | View Threaded

hygylista at jpm

Jan 26, 2005, 12:14 AM

Post #1 of 2 (1487 views)
Permalink

drbd error?

Hi!

I created a drbd device. Started to sync. Then mounted to my home.
------------------------------------------------------------------------

Jan 25 15:05:30 debian kernel: drbd0: Secondary/Secondary -->
Primary/Secondary
Jan 25 15:05:30 debian kernel: drbd0: I am(P):
1:00000002:00000001:00000001:00000001:11
Jan 25 15:05:30 debian kernel: drbd0: Peer(S):
0:00000001:00000001:00000001:00000001:01
Jan 25 15:05:30 debian kernel: drbd0: drbd0_receiver [15686]: cstate
Connected --> WFBitMapS
Jan 25 15:05:30 debian kernel: drbd0: drbd0_receiver [15686]: cstate
WFBitMapS --> SyncSource
Jan 25 15:05:30 debian kernel: drbd0: Resync started as SyncSource (need
to sync 149458172 KB [37364543 bits set]).
Jan 25 15:06:06 debian kernel: kjournald starting. Commit interval 5
seconds
Jan 25 15:06:06 debian kernel: EXT3 FS on drbd0, internal journal
Jan 25 15:06:06 debian kernel: EXT3-fs: mounted filesystem with ordered
data mode.

Than it finished the resync:
----------------------------
Jan 25 16:10:52 debian kernel: drbd0: Resync done (total 3922 sec;
paused 0 sec; 38104 K/sec)
Jan 25 16:10:52 debian kernel: drbd0: drbd0_worker [15683]: cstate
SyncSource --> Connected

And there is an error:
----------------------
Jan 26 01:04:44 debian kernel: attempt to access beyond end of device
Jan 26 01:04:44 debian kernel: drbd0: rw=0, want=299106408,
limit=298916344
Jan 26 01:04:44 debian kernel: EXT3-fs error (device drbd0):
ext3_get_inode_loc: unable to read inode block - inode=18694145,
block=37388300
Jan 26 01:04:44 debian kernel: Aborting journal on device drbd0.
Jan 26 01:04:44 debian kernel: ext3_abort called.
Jan 26 01:04:44 debian kernel: EXT3-fs error (device drbd0):
ext3_journal_start_sb: Detected aborted journal
Jan 26 01:04:44 debian kernel: Remounting filesystem read-only
Jan 26 01:05:22 debian kernel: EXT3-fs error (device drbd0) in
start_transaction: Journal has aborted
Jan 26 01:06:21 debian kernel: EXT3-fs error (device drbd0) in
start_transaction: Journal has aborted

Then I unmount it, try to fsck:
# e2fsck /dev/drbd0
e2fsck 1.35 (28-Feb-2004)
The filesystem size (according to the superblock) is 37397311 blocks
The physical size of the device is 37364543 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? yes

So I cant. Then I stopped drbd, e2fsck successfully /dev/sda0. Then
start drbd:

hygy [at] debia:~$ cat /proc/drbd
version: 0.7.8 (api:77/proto:74)
SVN Revision: 1725 build by root [at] debia, 2005-01-25 15:01:29
0: cs:Connected st:Primary/Secondary ld:Consistent
ns:167204 nr:52 dw:167256 dr:128486 al:365 bm:3 lo:0 pe:0 ua:0 ap:0
1: cs:Unconfigured

mount it again:
Jan 26 08:29:57 debian kernel: EXT3-fs warning (device drbd0):
ext3_clear_journal_err: Filesystem error recorded from previous mount:
IO failure
Jan 26 08:29:57 debian kernel: EXT3-fs warning (device drbd0):
ext3_clear_journal_err: Marking fs in need of filesystem check.
Jan 26 08:29:57 debian kernel: kjournald starting. Commit interval 5
seconds
Jan 26 08:29:57 debian kernel: EXT3-fs warning: mounting fs with errors,
running e2fsck is recommended
Jan 26 08:29:57 debian kernel: EXT3 FS on drbd0, internal journal
Jan 26 08:29:57 debian kernel: EXT3-fs: recovery complete.
Jan 26 08:29:57 debian kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Jan 26 08:31:00 debian kernel: drbd0: Primary/Secondary -->
Secondary/Secondary
Jan 26 08:31:00 debian kernel: drbd0: drbdsetup [26791]: cstate
Connected --> Unconnected
Jan 26 08:31:00 debian kernel: drbd0: drbd0_receiver [15686]: cstate
Unconnected --> BrokenPipe
Jan 26 08:31:00 debian kernel: drbd0: short read expecting header on
sock: r=-512
Jan 26 08:31:00 debian kernel: drbd0: worker terminated
Jan 26 08:31:00 debian kernel: drbd0: asender terminated
Jan 26 08:31:00 debian kernel: drbd0: drbd0_receiver [15686]: cstate
BrokenPipe --> StandAlone
Jan 26 08:31:00 debian kernel: drbd0: Connection lost.
Jan 26 08:31:00 debian kernel: drbd0: receiver terminated
Jan 26 08:31:00 debian kernel: drbd0: drbdsetup [26791]: cstate
StandAlone --> StandAlone
Jan 26 08:31:00 debian kernel: drbd0: drbdsetup [26791]: cstate
StandAlone --> Unconfigured
Jan 26 08:31:00 debian kernel: drbd0: worker terminated

Have anybody any idea what's wrong?

pls help,
thanks
HyGy

_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user

lmb at suse

Jan 26, 2005, 12:56 AM

Post #2 of 2 (1478 views)
Permalink

Re: drbd error? [In reply to]

On 2005-01-26T09:14:06, Hegedus Gabor <hygylista [at] jpm> wrote:

> Then I unmount it, try to fsck:
> # e2fsck /dev/drbd0
> e2fsck 1.35 (28-Feb-2004)
> The filesystem size (according to the superblock) is 37397311 blocks
> The physical size of the device is 37364543 blocks
> Either the superblock or the partition table is likely to be corrupt!
> Abort<y>? yes

You too seem to have created the filesystem on the raw disk and then put
drbd on top. wrong. You should have put drbd on first and then created
the fs on top.

The simplest way to recover would be to start over.

If that's not an option because you don't have a backup of the data:

stop drbd. unmount the filesystem. e2fsck on the lower level device and
have it repair whatever is there. Use resize2fs to shrink the filesystem
by about 132MB to make space for drbd's metadata at the end of the
device. Put drbd on again. fsck the drbd device to make sure all is well
now. Force a full resync.

Sincerely,
Lars Marowsky-Brée <lmb [at] suse>

--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business

_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com