Ken, Which nodes in /dev/ come pre-defined is entirely up to the Linux distributor. In your case, SUSE decided to stop at /dev/dasdz?. As others have pointed out, that doesn't prevent you from defining your own. Just remember when you upgrade to a new platform that you need to check this to see if more (or fewer) nodes have been predefined by the distribution creator.
Note that if you use what is called "devfs" that device nodes are created automagically by the system. Most people don't do that, and so they must be created manually or via a script by the distribution creator, or the system administrator. Your Linux folks might have been "spoiled" by Linux distributors creating so many /dev/hd? entries that they've never had to do their own, but still they should have already been aware of this. The difference between dasda1 and dasda2 is the same as between /dev/hda1 and /dev/hda2. They're different partitions on the disk drive. On 2.4-based Linux/390 systems, when you run dasdfmt, the default is to use CDL mode, which means that you _must_ run fdasd to create at least 1 partition, with the option of creating a maximum of three partitions. Those partitions, when they have file systems put on them, are referenced as /dev/dasd?1 /dev/dasd?2 /dev/dasd?3 If you only create one partition, you only need the /dev/dasd?1 device node. This feature is most useful in LPAR installs, since it means you don't need to dedicate entire 3390-? disks to any particular file system. This can be used in z/VM as well, but since you can already carve DASD up into arbitrarily sized chunks, not as useful. You are specifying "-d ldl", though, which means none of this applies. You only get 1 partition, /dev/dasd?[?]1. When you go to make a file system on that volume, you need to specify /dev/dasd?[?]1, and not just /dev/dasd?[?], since that is the volume descriptor, not the file system node. So, /sbin/mkfs.ext3 -b 4096 /dev/dasdaa is incorrect. It should be this: /sbin/mkfs.ext3 -b 4096 /dev/dasdaa1 Just to be even more wordy, this can also be done like this: mke2fs -j -b 4096 /dev/dasdaa1 Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ken Vance Sent: Thursday, April 22, 2004 12:22 PM To: [EMAIL PROTECTED] Subject: more than 26 disks Hi, We were adding a large number of disks to our SuSE8 image. Normally, it adds the dasd as "dasda", "dasdb", etc. When we added disk 27, it adds the dasd as "dasdaa". Here is the log when the devices were added: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390/0A(CU:3990/01) Cyl:3338 Head:15 dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390/0A(CU:3990/01) Cyl:3338 Head:15 dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: DIAG210 returned VRDCRCCL = 04, VRDC dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: XRC_supported reset because of missi dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390/0A(CU:3990/01): Configuration d Apr 22 13:00:02 linvm01 kernel: debug: dasdz: new level 3 Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390 Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: DIAG 82 dasd(eckd): /dev/dasdy ( 94: 96),[EMAIL PROTECTED]: (4kB blks): 2403360kB at 48kB/trk li Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: XRC_ Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdaa ( 94:104),[EMAIL PROTECTED]: 3390 Apr 22 13:00:02 linvm01 kernel: dasd(eckd): /dev/dasdy ( 94: 96),[EMAIL PROTECTED]: (4kB debug: dasdaa: new level 3 The Linux administration group then formatted and made a file system on the various dasd volumes. He had a problem when he went to format the "dasdaa" volume. It could not find the "dasdaa" device. He created it, and then he could format it. When he tried to make a files system, it again failed. When he creates the filesystem, he specifies the dasd without a number, ie. "dasdj", "dasdk", etc. I noticed in Mark Post's presentation , he has the following: > 2.4.x Kernels > mke2fs -b 4096 /dev/dasd?1,2,3 > mke2fs -b 4096 /dev/dasda1 > mke2fs -b 4096 /dev/dasda2 > mke2fs -b 4096 /dev/dasda3 What is the difference betweem 1, 2, and 3. Also, why did the system not create the "dasdaa", and "dasdaa1" information? Is there something special we must do when we reach disk number 27? Are the numbers used if you partition the drive into smaller areas? We only have one area on the disk, so I would guess that it would be the "1". Here is the log: linvm01:~ # dasdfmt -b 4096 -d ldl -f /dev/dasdaa dasdfmt: Unable to open device /dev/dasdaa: No such file or directory This was true: linvm01:~ # ls -la /dev/dasda* brw-rw---- 1 root disk 94, 0 Nov 6 2002 /dev/dasda brw-rw---- 1 root disk 94, 1 Nov 6 2002 /dev/dasda1 brw-rw---- 1 root disk 94, 2 Nov 6 2002 /dev/dasda2 brw-rw---- 1 root disk 94, 3 Nov 6 2002 /dev/dasda3 And then (checking major/minor numbers before) linvm01:~ # mknod -m 660 /dev/dasdaa b 94 104 linvm01:~ # ls -la /dev/dasdaa brw-rw---- 1 root root 94, 104 Apr 22 17:27 /dev/dasdaa linvm01:~ # chown root:disk /dev/dasdaa linvm01:~ # ls -la /dev/dasdaa brw-rw---- 1 root disk 94, 104 Apr 22 17:27 /dev/dasdaa Afterwards dasdformat runs without complains. linvm01:~ # dasdfmt -b 4096 -d ldl -f /dev/dasdaa Drive Geometry: 3338 Cylinders * 15 Heads = 50070 Tracks I am going to format the device /dev/dasdaa in the following way: Device number of device : 0x274 Labelling device : yes Disk label : LNX1 Disk identifier : 0X0274 Extent start (trk no) : 0 Extent end (trk no) : 50069 Compatible Disk Layout : no Blocksize : 4096 --->> ATTENTION! <<--- All data of that device will be lost. Type "yes" to continue, no will leave the disk untouched: yes Formatting the device. This may take a while (get yourself a coffee). Finished formatting the device. Rereading the partition table... ok When I tried a mkfs it failed. linvm01:/ # /sbin/mkfs.ext3 -b 4096 /dev/dasdaa mke2fs 1.28 (31-Aug-2002) mkfs.ext3: No such device while trying to determine filesystem size linvm01:/ # ls -la /dev/dasdaa brw-rw---- 1 root disk 94, 104 Apr 22 17:27 /dev/dasdaa linvm01:/ # Thanks, Ken Vance Amadeus ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
