SuSE 7.2 distribution unsure as to kernel level..... but it's pry a july/august cut.
I run dasdfmt (with the -p) option per someone's suggestion and I get this SuSE Instsys nokomis:/root # dasdfmt -n 0d18 -b 4096 -l L4D018 -p Note: IBM changed the default behaviour of dasdfmt to use a new, z/OS compatible disk layout that supports up to three partitions. Description of the two layouts: * cdl: formatted dasds can only be read with the newest IBM Code for 2.4 If you use the new cdl disk layout, you have to use 2.4. You have to create at least one partition using fdasd afterwards. * ldl: still supported by YaST and the 2.2.x and 2.4 kernels, you can use it safely, add '-d ldl' to the dasdfmt call for it. Infos: If you do a low level format from the filesystem setup in YaST (F6 - Format), YaST invokes dasdfmt with the -d ldl option to create the old disk layout which automatically has one partition and is also accessible by 2.2.19. fdasd is described in the Linux for S/390 Device Drivers and Installation Commands Manual for Kernel 2.4 at this URL: http://www10.software.ibm.com/developerworks/opensource/linux390/docu.html Press <ENTER> to continue and start dasdfmt -n 0d18 -b 4096 -l L4D018 -p: Drive Geometry: 10017 Cylinders * 15 Heads = 150255 Tracks I am going to format the device d18 in the following way: Device number of device : 0xd18 Major number of device : 94 Minor number of device : 0 Labelling device : yes Disk label : VOL1 Disk identifier : L4D018 Extent start (trk no) : 0 Extent end (trk no) : 150254 Compatible Disk Layout : yes Blocksize : 4096 --->> ATTENTION! <<--- All data in the specified range 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). cyl 10017 of 10017 |##################################################| 100% Finished formatting the device. Top shows dasdmt still running 24 processes: 19 sleeping, 5 running, 0 zombie, 0 stopped CPU states: 0.7% user, 44.8% system, 0.0% nice, 54.4% idle Mem: 1026820K av, 57120K used, 969700K free, 0K shrd, 26996K buff Swap: 0K av, 0K used, 0K free 12056K cached PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND 416 root 16 0 604 604 516 R 4.8 0.0 0:16 dasdfmt 422 root 14 0 1084 1080 900 R 1.9 0.1 0:00 top 216 root 13 0 908 908 552 R 0.9 0.0 4:31 modprobe 1 root 8 0 0 0 0 SW 0.0 0.0 0:04 swapper 2 root 9 0 0 0 0 SW 0.0 0.0 0:00 kmcheck 3 root 9 0 0 0 0 SW 0.0 0.0 0:00 keventd 4 root 19 19 0 0 0 RWN 0.0 0.0 0:01 ksoftirqd_CPU0 Top shows dasdmt still running. The question is why? It ran overnight. 6 hours of CPU time were used and it did not end. I also don't know why modprobe is running....
