On Mon, 5 Jan 2004, Mike Lovins wrote: > Can someone explain what has happened and what to do to get it right? > The problem is that I have 91 dasd devices defined and formated on my > system. But if I look in /dev I find dasda, dasda1, dasda2, dasda3, > dasdb, dasdb1,dasdb2, dasdb3, dasdc, and so on to dasdz, dasdz1, dasdz2, > and finally dasdz3 but this is not all my dasd. If I do a cat on > /proc/dasd/devices it shows all the dasd all the way to dasdcm, that is > the last one I should have and it points to /dev/dasdcm and that does > not exist.
Create them ;-) It appears that your distro only has the first 26 disk devices available (a thru z). To get up to cm, you will need to use the mknod command to create the /dev nodes to support aa thru cm. The trick will be getting the right major/minor node numbers to use on the mknod command. Look at the output of /proc/dasd/devices: the major/minor node numbers the DASD driver is using to address each DASD are shown (e.g. "0200(ECKD) at (94 : 4) is dasdb ... " in /proc/dasd/devices means that dasdb is at major 94, minor 4). Use these numbers to create the node. # cd /dev # mknod dasdaa b <majaa> <minaa> # mknod dasdaa1 b <majaa> <minaa+1> # mknod dasdaa2 b <majaa> <minaa+2> # mknod dasdaa3 b <majaa> <minaa+3> # mknod dasdab b <majab> <minab> # mknod dasdab1 b <majab> <minab+1> ... and so on ISTR more detail on this in the list archives. Specifically, once the assigned major number of 94 runs out of minors (somewhere around dasdbl), what major number to use next? Cheers, Vic
