Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Thu, 2004-01-29 at 20:07, Lars Ellenberg wrote:
> / 2004-01-29 16:47:55 +0100
> \ matthias zeichmann:
> > status quo is:
> > machine atem holds all the ha services and all drbd devices in a sane
> > state. [0]
> > machine kaelte has been freshly rebuild with new (larger) disks. some
> > drbd devices were partitioned to hold more diskspace [1]. drbd devices
> > are formatted ext3 and hold no data.
[...]
> > Plan a:
> [nonsense]
>
> plan C: hook up all disk in one box, an do
> dd if=/dev/good/data of=/dev/new/disk,
wont work in our case (1 channel hardware raid 1)
> plan A:
> with minimal downtime I think it should work like this:
it doesnt in my improvised test setup.
beton holds a device /dev/sda13 with 1992300kB (good data)
mz holds a device /dev/hda7 with 9612100kB (no data but bigger disk)
i tried this:
set disk-size on beton in drbd.conf to 1992300
on mz to 9612100
i used the output of 'df -k' for the values of disk-size
drbd is running on beton with /dev/nb0 mounted and a little data on it
------------->8-----------------------------------------------------------
Jan 30 13:25:34 beton kernel: drbd: initialised. Version: 0.6.10+cvs
(api:64/proto:62)
Jan 30 13:25:50 beton kernel: drbd0: blksize=1024 B
Jan 30 13:25:50 beton kernel: klogd 1.4.1, ---------- state change
----------
Jan 30 13:25:50 beton kernel: Loaded 151 symbols from 9 modules.
Jan 30 13:25:50 beton kernel: drbd0: blksize=4096 B
Jan 30 13:25:50 beton kernel: kjournald starting. Commit interval 5
seconds
Jan 30 13:25:50 beton kernel: EXT3 FS 2.4-0.9.17, 10 Jan 2002 on
drbd(43,0), internal journal
Jan 30 13:25:50 beton kernel: EXT3-fs: mounted filesystem with ordered
data mode.
------------->8-----------------------------------------------------------
[start drbd on mz]
Jan 30 13:30:10 mz kernel: drbd: initialised. Version: 0.6.10+cvs
(api:64/proto:62)
Jan 30 13:30:11 mz kernel: drbd0: Creating state file
Jan 30 13:30:11 mz kernel: "/var/lib/drbd/drbd0"
Jan 30 13:30:11 mz kernel: klogd 1.4.1, ---------- state change
----------
Jan 30 13:30:11 mz kernel: Loaded 500 symbols from 24 modules.
Jan 30 13:30:11 mz kernel: drbd0: Your size hint is bogus!change it to
1991632
Jan 30 13:30:11 mz kernel: drbd0: Connection lost.
[message repeated until i stop drbd]
------------->8-----------------------------------------------------------
Jan 30 13:30:11 beton kernel: drbd0: Your size hint is bogus!change it
to 2024158
Jan 30 13:30:11 beton kernel: drbd0: Connection lost.
------------->8-----------------------------------------------------------
second try:
disk-size unspecified on beton, on mz still 9612100:
------------->8-----------------------------------------------------------
Jan 30 14:34:40 beton kernel: drbd0: blksize=1024 B
Jan 30 14:34:40 beton kernel: drbd0: blksize=4096 B
Jan 30 14:34:40 beton kernel: drbdX: No bitmap!Maybe you need to specify
the device size?
------------->8-----------------------------------------------------------
Jan 30 14:38:39 mz kernel: drbd0: Creating state file
Jan 30 14:38:39 mz kernel: "/var/lib/drbd/drbd0"
Jan 30 14:38:39 mz kernel: klogd 1.4.1, ---------- state change
----------
Jan 30 14:38:39 mz kernel: Loaded 500 symbols from 24 modules.
Jan 30 14:38:39 mz kernel: drbd0: Your size hint is bogus!change it to
2024158
Jan 30 14:38:39 mz kernel: drbd0: Connection lost.
------------->8-----------------------------------------------------------
beton:root# cat /proc/drbd
version: 0.6.10+cvs (api:64/proto:62)
0: cs:WFConnection st:Primary/Unknown ns:25080 nr:0 dw:12 dr:36017 pe:0
ua:0
NEEDS_SYNC
beton:root#
------------->8-----------------------------------------------------------
as above but disk-size on mz set to recommended value of 2024158
------------->8-----------------------------------------------------------
Jan 30 14:44:59 beton kernel: drbd0: Synchronisation started blks=15
------------->8-----------------------------------------------------------
Jan 30 14:44:59 mz kernel: drbd: initialised. Version: 0.6.10+cvs
(api:64/proto:62)
Jan 30 14:44:59 mz kernel: drbd0: Creating state file
Jan 30 14:44:59 mz kernel: "/var/lib/drbd/drbd0"
Jan 30 14:44:59 mz kernel: klogd 1.4.1, ---------- state change
----------
Jan 30 14:44:59 mz kernel: Loaded 500 symbols from 24 modules.
Jan 30 14:44:59 mz kernel: drbd0: Connection established. size=2024158
KB / blksize=4096 B
------------->8-----------------------------------------------------------
Jan 30 14:47:56 beton kernel: drbd : BitMap too small!
Jan 30 14:47:59 beton last message repeated 7891 times
Jan 30 14:47:59 beton kernel: drbd0: Synchronisation done.
------------->8-----------------------------------------------------------
now i can fail over to mz but this is not the desired effect because i
have lost the additional diskspace.
kernels are handmade: 2.4.19 on beton and 2.4.24 on mz, both uniproc
without highmem. beton being an athlon 700 and mz a pIII 700.
drbd is freshly compiled from cvs.
i also managed to trigger some oopses on mz but on a kernel with the
ck-patchset; i guess you are not interested in drbd running on these...
btw: is current cvs compatible with 0.6.7 to allow painless upgrade?
api on 0.6.7 was 63...
> Now you _could_ just start drbd on atem, and it _should_ work.
i dont even get so far...
did i miss something?
i dont like the idea of switching to
> plan B:
because there is no easy way to go back if something goes wrong...
m
--
This .sig may not be reproduced, in whole or in part, by any means,
including but not limited to: Mechanical reprints, electronic storage or
scanning, theatrical release, musical ballads, word of mouth, sign
language, braille, pantomime, hetero- or asexual reproduction, genetic
engineering, or inclusion in other .sigs.