Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Valdas R wrote:
> Hello
>
> I'm struggling for last couple days to get my sync
> working. I have to server one of then runs CentOS
> kernel 2.6.17.8, with read ahead patch, another one
> CentOS 2.6.17.13, Drbd version: 0.7.21
> config file for looks like this:
>
> on primary {
> device /dev/drbd0;
> disk /dev/cciss/c1d0p1;
> -------------> xfs file system
> address 192.168.0.105:7788;
> meta-disk /dev/cciss/c1d0p3[0];
> ----------------> ext3 file system
>
> }
>
> on secondary{
> device /dev/drbd0;
> disk /dev/sdb1;
> ---------------------> xfs
> address 192.168.0.106:7788;
> meta-disk /dev/sdb2[0];
> ----------------------->xfs
> }
>
>
> i make secondary server Stand Alone and primary:
>
> after that
>
> mount /dev/drbd0 /test_dir/
> mount: /dev/drbd0: can't read superblock
>
> and dmesg:
>
> Filesystem "drbd0": Disabling barriers, not supported
> by the underlying device
> attempt to access beyond end of device
> drbd0: rw=0, want=245762304, limit=220319968
> I/O error in filesystem ("drbd0") meta-data dev drbd0
> block 0xea608ff ("xfs_read_buf") error 5 buf
> count 512
> XFS: size check 2 failed
> Filesystem "drbd0": Disabling barriers, not supported
> by the underlying device
> attempt to access beyond end of device
> drbd0: rw=0, want=245762304, limit=220319968
> I/O error in filesystem ("drbd0") meta-data dev drbd0
> block 0xea608ff ("xfs_read_buf") error 5 buf
> count 512
> XFS: size check 2 failed
>
>
> I was wondering if it's because drbd-meta dir file
> system is different on primary server or some other
> issue ?
>
Hmnn
in a word YES, although not in the way you mean
meta data uses a 'raw' partition, not a fileystem
unmount /dev/cciss/c1d0p3
and /dev/sdb2
and try again
--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.