Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
/ 2004-04-27 22:16:09 -0700 \ Jason Gray: > It was operator error : ) I was loading the drbd module via running drbd > rather than insmod drbd. This created a loop when trying to add a device to > /dev/nb1. The only other issues I get is with the fsck: > > > datadisk: 'drbd0' fsck /dev/nb0 .. datadisk: ERROR: e2fsck -p -y /dev/nb0 > [8]: > datadisk: ERROR: e2fsck 1.32 (09-Nov-2002) > e2fsck: Invalid argument while trying to open /dev/nb0 > > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 <device> > datadisk: ERROR: e2fsck -p -y /dev/nb0 FAILED > > Is this related to the drbd script using blockdev instead? not at all. what does cat /proc/drbd say? Lars Ellenberg