Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, 15 Jun 2004 18:24:18 +0200 Lars Ellenberg <Lars.Ellenberg at linbit.com> threw this fish to the penguins: > / 2004-06-15 12:08:37 -0400 > \ george young: > > [drbd 0.6.10, SuSE 8.3 x86 linux, 2.4.20, lsi megaraid scsi 320-2] > > nodes are "pig-app" and "pig-db". > > > > One of the disks on node "pig-db" failed, (RAID 5, so no crash), so I > > forced pig-db to secondary for both drbd file systems and rebooted pig-db without > > drbd. After replacing the disk, and wiping and reconfiguring the RAID > > box(don't ask why...), I need to bring the system back up as drbd secondary. > > > > Starting drbd seems fine: ... > > May 9 16:00:14 pig-db drbd: 'drbd_db' SyncingQuick finished, issue drbdsetup /dev/nb1 secondary_remo > > SyncingQuick assumes you have "almost" up-to-date data on the lower > level disk. you actually have a blank disk. drbd has no way to know that, > so you must tell it... > > > I do "datadisk drbd_home start", which switches drbd_home partition to primary and mounts it: ... > > May 9 17:38:46 pig-db datadisk: 'drbd_db' activated > > > > But I get a stream of kernel errors, like: > > is_tree_node: node level 0 does not match to the expected one 1 ... > either (now) do drbdsetup /dev/nbX replicate (on the Secondary!, > out-of-date node! not on the other...) > or (before you "drbd start" it) do rm /var/lib/drbd/* ^^^^^^^^^^^^^^^^^^ This worked perfectly, thanks much! -- George -- "Are the gods not just?" "Oh no, child. What would become of us if they were?" (CSL)