Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My SLES 9 SP3 system has 4096 /dev/sd* files: 256 'major' files each with 16 'minior files. I need to create more sd files, so that my system can handle more than 256 disks. I thought that Linux 2.6 kernel systems were supposed to just do this automatically, but this isn't happening.
The 2.4 kernel had a limitation on the device major numbers allowed(1-255) but I thought that limit no longer existed in the 2.6 kernels. Normally you would create a device file with the mknod command(see man mknod) which, for block devices, would have the syntax:
# mknod <device name> -b Major Minor
Have you tried creating a device file with mknod? If it refuses to go ,it could be a kernel limitation.
Thanks for the reply. Yes, mknod works just fine. But I want to fix the problem the 'right way', and understand why SLES 9 didn't just create more sd files automagically. Any ideas?
You would have to carefully parse through all your init scripts to find that and then properly edit them to get the desired number of device files. The init scripts never anticipated anyone would need more that 256 drives and are set up that way by default. I'd just run the necessary mknod commands out of rc.local so you get your extra device files on every boot without potentially screwing up your init scripts.
Last edited by kilgoretrout; 01-10-2007 at 02:19 PM.
Here's the solution to my problem. In SLES 9 SP3, chkconfig boot.udev is off by default. This means that udevstart is not run by default, and so will not create additional /dev/sd* files if needed. So, when I ran udevstart, poof!, all the additional /dev/sd entries were created. And, using 'chkcondig boot.udev on' will allow this to happen automatically.
FYI, 'chkconfig boot.udev' is on by default in SLES 10.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.