[DRBD-user] CentOS 4.6 udev problem with DRBD

Ken Dechick kend at medent.com
Fri May 22 15:40:05 CEST 2009

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

> ?? Yes once I remove the udev rule for drbd the whole "wierd" links 
> things goes away, and all my devices work as expected again. So 
> without relying on udev what were most people doing to create the 
> /dev/drbd0 at boot? Can I do something as simple as adding a mknod 
> command in /etc/rc.d/rc.local? I have one last question: upon a reboot 
> my primary node does not come up as primary, I have to issue an 
> 'drbdadm primary r0' to get it to come up. Is this normal?

>> We've did some tests under 4.7 and could not reproduce what you are 
>> seeing (well, and 4.8 is just around the corner).

I wonder if this is perhaps a kernel issue? We run a customized version of CentOS kernel 2.6.9-67.0.22. Why customized?? Well, there is a lot of stuff in the standard kernel we will never ever use, so we chop out what we don't need in order to provide a more streamlined kernel. We run this same kernel on a couple of different IBM xSerie4s servers. Before I give up on RHEL/CentOS 4 perhaps I should install the official CentOS 4.6 kernel and try all this again! If anyone thinks a may be onto something with the kernel, I would be happy to post my kernel .config for you to look at.

> ?? I can work around the udev thing I am sure, but for many reasons I 
> think I am going to try all of this under CentOS 5.2 x86_64.

>> Is there any reason why you like to stay behind one version of what is 
>> there?

We develop software for medical practice management. With an installed client base of 3000+ servers change comes slow, I try to have as few OS and kernel versions out there as possible to make it easier to support. We have just started to gear up for the move to 64bit Linux. I have been testing CentOS 5.3 x86_64 the last few days and progress is going well, but I only handle supporting the servers - our programming dept could probably answer this question better. Everytime we have moved to a new distro in the past, it meant a whole ton of changes for them. Just bumping up to a newer gcc causes issues, let alone the dramatic changes in kernel from 2.6.9 to 2.6.18!
So it isn't that I "like" to stay with an older distro - it is needed from a support standpoint.

>> Ralph

Kenneth M DeChick
Linux Systems Administrator
Community Computer Service, Inc.
(315)-255-1751 ext154
kend at medent.com
-- -- -- -- -- -- -- -- -- -- --
"You canna change the laws of physics, Captain; I've got to have thirtyminutes! "

This message has been scanned for viruses and dangerous content by MailScanner &amp; ClamAV. <BR>
This message and any attachments may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use <BR>
of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail <BR>
or the information contained herein is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by e-mail, and permanently <BR>
delete this e-mail. <BR>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20090522/3d65e926/attachment.htm>

More information about the drbd-user mailing list