Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
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 : 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? Jason -----Original Message----- From: drbd-user-admin at lists.linbit.com [mailto:drbd-user-admin at lists.linbit.com]On Behalf Of Lars Ellenberg Sent: Tuesday, April 27, 2004 10:08 PM To: DRBD Subject: Re: [DRBD-user] creating resource on nb1 / 2004-04-27 20:15:04 -0700 \ Jason Gray: > I'm getting an error when trying to create a device on /dev/nb1: > > can not open device: No such device. > > I tried re-creating the block device like this: > > mknod -m 660 /dev/nb1 b 43 1 > > and it doesn't seem to respond. However, if I change the block minor value > to 0 then it works however, it conflicts with /dev/nb0. Has anyone else had > this issue. maybe you loaded the module with minor_count=1 ? how many minors show up in /proc/drbd ? if only "0:", then you need to reload the module. Lars Ellenberg _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user