Except /proc/dasd/devices only includes the device nodes, not the partitions. True, the partitions are just +1, +2, and +3 from those, but it bears mentioning.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Hall, Ken (IDS DCS PE) Sent: Friday, December 17, 2004 7:55 AM To: [EMAIL PROTECTED] Subject: Re: LVM, SuSE, going over 26 volumes - ARRGH The best place to accurately determine the major and minor nodes you need is /proc/dasd/devices. I have a script that builds the nodes from that file, and someone posted an even slicker one here a while back. > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Matt Lashley/SCO > Sent: Thursday, December 16, 2004 3:55 PM > To: [EMAIL PROTECTED] > Subject: [LINUX-390] LVM, SuSE, going over 26 volumes - ARRGH > > > Looks like the mknod script I was using doesn't create all > the nodes that > I needed. After a quick read of the Device Drivers manual > and a browse of > the archives it dawned on me to run mknod specifically for the dasdaf1 > device. > > mknod -m 660 /dev/dasdaf1 b 94 125 > > scodw2:/data/BI_MySql_Scripts # pvcreate /dev/dasdaf > dasdaf dasdaf1 > scodw2:/data/BI_MySql_Scripts # pvcreate /dev/dasdaf1 > pvcreate -- physical volume "/dev/dasdaf1" successfully created > > - Matt http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
