[DRBD-user] drbd (0.7.22) module takes longer that UDEV_TIMEOUT to load

Lars Ellenberg lars.ellenberg at linbit.com
Fri Aug 3 16:58:47 CEST 2007

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, Aug 02, 2007 at 01:47:22PM +1000, Oliver Hookins wrote:
> Hi,
> 
> we're running drbd 0.7.22 on RHEL4 x86_64, kernel is 2.6.9-55.0.2.ELsmp and
> it seems on reboot we are hitting the limit of UDEV_TIMEOUT in the init
> script (which is set to 10 seconds), before /dev/drbd0 is created. We get
> messages like the below:
> 
> Aug 1 20:30:10 testpc drbd: Starting DRBD resources:
> Aug 1 20:30:10 testpc kernel: drbd: initialised. Version: 0.7.22
> (api:79/proto:74)
> Aug 1 20:30:10 testpc kernel: drbd: SVN Revision: 2554 build by
> build at dreadnought.anchor.net.au, 2007-08-01 16:01:54
> Aug 1 20:30:10 testpc kernel: drbd: registered as block device major 147
> 
> then later
> 
> Aug 1 20:30:20 testpc drbd: can not open /dev/drbd0:
> Aug 1 20:30:20 testpc drbd: [ d0
> Aug 1 20:30:20 testpc drbd: No such file or directory
> Aug 1 20:30:20 testpc drbd:
> Aug 1 20:30:20 testpc drbd: cmd /sbin/drbdsetup /dev/drbd0 disk
> /dev/testpc/drbd internal -1 --on-io-error=pass_on failed!
> Aug 1 20:30:20 testpc drbd: can not open /dev/drbd0: No such file or
> directory
> Aug 1 20:30:20 testpc rc: Starting drbd: failed
> 
> After the machine has finished booting and we can log in, /dev/drbd0 exists
> and we can start drbd with 'service drbd start' as normal and everything
> works. Is this a bug in the drbd kernel module or udev?

use static device nodes then, or static udev rules.
or increase that timeout...


-- 
: Lars Ellenberg                            Tel +43-1-8178292-0  :
: LINBIT Information Technologies GmbH      Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe    http://www.linbit.com :
__
please use the "List-Reply" function of your email client.



More information about the drbd-user mailing list