[DRBD-user] Porblems starting with drbd

Milind Dumbare milind at linsyssoft.com
Wed Dec 6 14:36:51 CET 2006

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On Wednesday 06 December 2006 18:38, Kamran Nisar wrote:
> could this be related ?
I don't think so, as errors are with hdd.

[snip]
hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[snip]
>
> test1:~ # fdisk -l
>
> Disk /dev/hda: 80.0 GB, 80026361856 bytes
> 255 heads, 63 sectors/track, 9729 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/hda1               1         129     1036161   83  Linux
> /dev/hda2   *         130        9729    77112000   83  Linux
>
> Disk /dev/hdc: 203.9 GB, 203928109056 bytes
> 255 heads, 63 sectors/track, 24792 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/hdc1               1       24792   199141708+  fd  Linux raid
> autodetect
>
> Disk /dev/hdd: 203.9 GB, 203928109056 bytes
> 255 heads, 63 sectors/track, 24792 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/hdd1               1       24791   199133676   fd  Linux raid
> autodetect
>
> Disk /dev/md0: 407.8 GB, 407833804800 bytes
> 2 heads, 4 sectors/track, 99568800 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
why don't you crate smaller partitions. Test them and then go for bigger one.
>
> Disk /dev/md0 doesn't contain a valid partition table
>
>
> =-=-=
>
> On 12/6/06, Milind Dumbare <milind at linsyssoft.com> wrote:
> > On Wednesday 06 December 2006 17:57, Kamran Nisar wrote:
> > > Hi, I am trying to set up drbd with two nodes. After setting up drbd,
> >
> > and
> >
> > > executing drbdadm up all on both the nodes , i executed "drbdadm --
> > > --do-what-I-say primary all" on server1 to make it primary. It started
> >
> > an
> >
> > > initial sync, and i left it overnight to complete. when i came back in
> >
> > the
> >
> > > morning, and executed drbdadm -- connect all on server 1, it gives me
> >
> > the
> >
> > > following error
> > >
> > > test1:~ # drbdadm -- connect all
> > > Child process does not terminate!
> > > Exiting.
> > >
> > >
> > >
> > > the cat /proc/drbd  on both machines is listed below
> > >
> > > test1:~ # cat /proc/drbd
> > > version: 0.7.14 (api:77/proto:74)
> > > SVN Revision: 1989 build by root at test1, 2006-11-30 11:03:07
> > >  0: cs:BrokenPipe st:Secondary/Unknown ld:Inconsistent
> > >     ns:4568 nr:0 dw:0 dr:12676 al:0 bm:196 lo:0 pe:22 ua:2025 ap:0
> > >
> > >
> > >
> > > test2:~ # cat /proc/drbd
> > > version: 0.7.18 (api:78/proto:74)
> > > SVN Revision: 2186 build by lmb at chip, 2006-05-04 17:08:27
> > >  0: cs:WFConnection st:Secondary/Unknown ld:Inconsistent
> > >     ns:0 nr:198672496 dw:198672496 dr:0 al:0 bm:12126 lo:0 pe:0 ua:0
> >
> > ap:0
> >
> > > the config snippet is as below
> > >
> > >
> > >
> > >
> > >
> > >
> > > resource r0 {
> > >
> > >   #
> > >   protocol C;
> > >
> > >
> > > incon-degr-cmd "halt -f";
> > >   startup {
> > >     #
> > >     degr-wfc-timeout 120;    # 2 minutes.
> > >   }
> > >
> > >   disk {
> > >     on-io-error   detach;
> >
> > It seems this is executed to due (see below in dmesg)
> >
> > >     size 300G;
> > >   }
> > >
> > >   net {
> > >   }
> > >
> > >   syncer {
> > >     #
> > >     rate 100M;
> > >
> > >     #
> > >     group 1;
> > >
> > >
> > >     al-extents 257;
> > >   }
> > >
> > >   on test1 {
> > >     device     /dev/drbd0;
> > >     disk       /dev/md0;
> > >     address    192.168.2.61:7788;
> > >     meta-disk  internal;
> > >
> > >   }
> > >
> > >   on test2 {
> > >     device    /dev/drbd0;
> > >     disk      /dev/md0;
> > >     address   192.168.2.62:7788;
> > >     meta-disk internal;
> > >   }
> > > }
> > >
> > >
> > >
> > > ==--=-=-=--=-=-=
> > >
> > > test1:~ # dmesg | tail
> > > ide: failed opcode was: unknown
> > > end_request: I/O error, dev hdd, sector 198676719
> > > hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > > hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=198676735,
> > > high=11, low=14127359, sector=198676727
> >
> > Seems like I/O error here.
> >
> > > ide: failed opcode was: unknown
> > > end_request: I/O error, dev hdd, sector 198676727
> > > hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > > hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=198676735,
> > > high=11, low=14127359, sector=198676735
> > > ide: failed opcode was: unknown
> > > end_request: I/O error, dev hdd, sector 198676735
> > >
> > >
> > >
> > >
> > > =-=-=-=-=



More information about the drbd-user mailing list