Re: dasdfmt problems with EMC disk model 9
If this is SLES-7 the fix is on the May Patch CDROM, and/or you should run Y.O.U. to get the patches. Ciao Mark -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Abdullah Al-humaid Sent: 14 October 2002 06:36 To: [EMAIL PROTECTED] Subject: Re: dasdfmt problems with EMC disk model 9 suse 2.4.7 --- "Ferguson, Neale" <[EMAIL PROTECTED]> wrote: > What level of kernel? There was a fix almost a year > ago that addressed this > problem. > > -Original Message- > I am having problems formating EMC disks (Model 9 > equiv.). I never get the prompt back when the format > is complete (or is it not complete.), Any ideas why > this is happening? . Below is the output of the > command: __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com
Re: dasdfmt problems with EMC disk model 9
suse 2.4.7 --- "Ferguson, Neale" <[EMAIL PROTECTED]> wrote: > What level of kernel? There was a fix almost a year > ago that addressed this > problem. > > -Original Message- > I am having problems formating EMC disks (Model 9 > equiv.). I never get the prompt back when the format > is complete (or is it not complete.), Any ideas why > this is happening? . Below is the output of the > command: __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com
NO CONSOLE MSGS when IPLing an OFFLINDR-restored system
I attempted to copy(backup/restore) a RH 7.2 system today using OFFLINDR. (I've done this in the past successfully). The system is being moved from an older mp3000-a20 to an mp3000 h70. The source system was made up of 4 3390 volumes. 1. dasda1 - / 2. dasdb1 - /usr 3. dasdc1 - swap1 4. dasdd1 - swap2 This is what i did: On MP3000-A20 system: 1. updated parmfile to point to my new device address on the target system. 2. ran zipl 3. updated the ipaddr in ifcfg-eth0 4. updated /etc/fstab to remove swap filesystems (because I did not copy those 2 3390s to the tgt system) 5. Issued command swapoff -a 6. updated /etc/chandev to change the lcs0 addrs 7. shutdown the system 8. backed up the system using offlindr ** see note below 1. On mp3000 h70 OFFLINDR restored the 2 3390 volumes 2. IPL'd new target 3. Received NO CONSOLE MSGS, BUT NOTICED THAT THE SYSTEM DID "IPL COMPLETE" and the CPU showed activity. ** NOTE: The source RH 7.2 system had two SWAP FILESYSTEMs on two other 3390s...and I did NOT copy those to the target system. Instead I updated fstab to not mount the swap filesystems. ANY IDEAS??? TIA Dave
Re: Antwort: Max number of dasd devices
Ihno wrote: >According to /usr/src/linux/Documentation/devices.txt the numbers from >231 >.to 254 are allocatet the following way: > >231-239 UNASSIGNED > >240-254 LOCAL/EXPERIMENTAL USE There is a discrepancy between the doc and the code that was implemented for the dasd driver. So, what else is new. 16x256=4096 (nodes 94 and 240-254). zSeries pushes well beyond that in device capability. 4 shark, iceberg, or other dasd subsystem hits this limit quickly nowadays. The current theoretical limit is 256 channels x 256 devices/channel=65,536 on a zSeries. When will SuSE have the devfs as the default for zSeries so we don't have to compile the kernel to use it and get away from the double mapping we have to do between device and device node? It is a real nuisance to try and map 100 devices per LPAR for 7 or 8 LPARs. Then try moving 20 or thirty of those volumes to another LPAR when business needs dictate! W/O devfs, I can vouch that it is both a pain and error prone.
Re: NSS-Support for Linux Kernel under VM
At 23:36 11-10-02, Rick Troth wrote: >That's not a caveat. That's just how life is with NSS: snapshot. >And if we had the STM support in the kernel for 'IPL sys PARM parms' >to work, it would not even be an issue!! Come on Rick. That isn't true with CMS either. Provided you save the NSS early enough it will be before the kernel finds out the virtual machine size etc. If you would not include the dasd= in the NSS you would require each Linux guest to have that on the IPL statement in the CP directory or in the PROFILE EXEC which is not fun either. IPL with initrd like done for SCSI systems is probably the best way to manage this. Rob
Re: dasdfmt problems with EMC disk model 9
What level of kernel? There was a fix almost a year ago that addressed this problem. -Original Message- I am having problems formating EMC disks (Model 9 equiv.). I never get the prompt back when the format is complete (or is it not complete.), Any ideas why this is happening? . Below is the output of the command:
Re: Intel Architecture Emulated with Linux/390?
On Tue, Sep 17, 2002 at 06:24:17AM -0500, Paul Raulerson wrote: > Unless of course, they do a lot of bit manipulation, in which case that rotten Intel >Arch. is inverted and out of order... > -Paul There is a lot of bitmanipulating code in the common code of linux (look at select system-call) which runs without modifications on architectures with different byte-order and different word size. -Ihno > > - Original Message - > From: "David Boyes" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, September 16, 2002 12:11 PM > Subject: Re: Intel Architecture Emulated with Linux/390? > > > > > As I am investigating vendor support for Linux/390, I have run into a > > > question I cannot answer. Vendors want to know if Linux/390 > > > emulates Intel > > > architecture. > > > > No, it does not. > > > > > Apparently, when programming in C, they have to > > > write the > > > application to the specific architecture and that it will not work on > > > non-Intel based systems. > > > > If you're getting crap like this from your vendors, you need new vendors. > > > > Your vendors will have to recompile their applications for the appropriate > > processor architecture, but if they're too clueless to be able to understand > > this, I'd be pretty wary of them in the first place. > > > > -- db > > -- Ihno Krumreich[EMAIL PROTECTED] SuSE Linux AG S390 & zSeries Deutschherrnstr. 15-19+49-911-74053-439 90429 N|rnberghttp://www.suse.de
dasdfmt problems with EMC disk model 9
I am having problems formating EMC disks (Model 9 equiv.). I never get the prompt back when the format is complete (or is it not complete.), Any ideas why this is happening? . Below is the output of the command: zlinux4:~ # dasdfmt -v -p -b 4096 -f /dev/dasdi Retrieving disk geometry... Drive Geometry: 10017 Cylinders * 15 Heads = 150255 Tracks I am going to format the device /dev/dasdi in the following way: Device number of device : 0x225 Major number of device : 94 Minor number of device : 32 Labelling device: yes Disk label : VOL1 Disk identifier : 0X0225 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). Detaching the device... Invalidate first track... cyl 10017 of 10017 |##| 100% formatting tracks complete... Revalidate first track... Reaccessing the device.. . Finished formatting the device. Retrieving dasd information... done Writing empty bootstrap... Writing label... Writing VTOC... done Thanks __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com
Re: Samba Quota function works well with SuSE ?
On Fri, 11 Oct 2002 21:28, you wrote: > On Fri, 2002-10-11 at 14:02, Michiyasu Takada wrote:. > > > As far as I know, Samba 2.2.x has a problem regarding quota with Linus > > kernel, and only Red Hat Linux with Alan Cox patch can handle this > > function. > > This customer is thinking of using SuSE Linux Enterprise Server 7 or 8 > > (which will be available in near future), so they want to know SuSE can > > handle the Samba quota. Please let me know if this works well with SuSE. > > While I'd love your customer to go with Red Hat ;) I'm actually not > aware of such limitations. Even if it were, there's no technical reason you couldn't use the Red Hat source including patches to build a kernel for SuSE. SuSE support might not like it a lot, but that's another matter. -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: Antwort: Max number of dasd devices
On Fri, Oct 11, 2002 at 04:11:28PM -0700, Jim Sibley wrote: > Udo wrote: > > >so additional major numbers (typically descending from 254) are > >allocated > > Doesn't this conflict with the tape major numbers? What is their range? > According to /usr/src/linux/Documentation/devices.txt the numbers from 231 to 254 are allocatet the following way: 231-239 UNASSIGNED 240-254 LOCAL/EXPERIMENTAL USE Ihno -- Ihno Krumreich[EMAIL PROTECTED] SuSE Linux AG S390 & zSeries Deutschherrnstr. 15-19+49-911-74053-439 90429 N|rnberghttp://www.suse.de
Re: Max number of DASD devices
Hi James, I think you have now had sufficient answers to your question, but I'm curious as to why you ask in the first place? Is the question purely academic, or do you envisage some project which requires a lot of DASD space? If it's academic then you have you answers, if it is a space question then the number of DASD devices is only part of the equation. Future CKD DASD will be larger (20+GB), and support for non-CKD devices will allow more generic device types (100+GB) - thus your answer will change approx every 6 months ;-) Ciao Mark -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of James Johnson Sent: 10 October 2002 19:17 To: [EMAIL PROTECTED] Subject: Max number of dasd devices Is there a max number of dasd devices that can be attached to a Linux machine? James Johnson Email: [EMAIL PROTECTED] Systems Programmer Voice: 660-543-8065 Central Missouri State University Fax: 660-543-8123
