Hi,
The good news is that you don't need to kill the cat with a 2.4.x Kernel
(SuSE or Redhat).
This is what I did when I added DASD 200 to my system:
echo "set device range=0200 on">>/proc/dasd/devices
Then I initialized the device with dasdfmt formatted it with fdasd added it
to my rootvg volume group, extended my logical volume for root, extended
the filesystem on it, EVERYTHING on a running System.
Great fun!!!!!
(Of course you will have to change the parmfile as well)
Mit freundlichen Gr��en,
Frank Warzecha
-------------------------------------
Frank Warzecha,
Team Betriebssysteme
RZNet AG, Kerpen, Germany
>>>>>>>>>>>>>>>Neue Telefon Nummer: >>>>>>>>Tel:02273-603172
http://www.rznet.de
"Dennis G.
Wicks" An: [EMAIL PROTECTED]
<[EMAIL PROTECTED] Kopie:
> Thema: Re: Add DASD
Gesendet von:
Linux on 390
Port
<[EMAIL PROTECTED]
ARIST.EDU>
17.01.02 19:01
Bitte antworten
an Linux on 390
Port
The bad news is that you have to "kill the cat" one more time.
So, add 150-15f, and maybe 250-25f and any other addresses you like
while you are at it.
Running silo doesn't hurt the system. It is the boot you have to do to
get the new parm file in the kernel that kills the system!
Good Luck!
Dennis
Steve Guthrie <[EMAIL PROTECTED]> on 01/17/2002 11:18:06 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Dennis Wicks/infosvcs/CDG)
Subject: Re: Add DASD
OK, I'm tracking the parmfile now. The dasdfmt (dasdfmt -f /dev/dasde -b
4096) command returns "dasdfmt: error opening device /dev/dasde: Invalid
argument" after I add it to the parmfile and reboot. How does one see this
device without running silo? How does one add this device with silo on a
working system without killing the cat?
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of
Coffin Michael C
Sent: Thursday, January 17, 2002 9:42 AM
To: [EMAIL PROTECTED]
Subject: Re: Add DASD
If you haven't already, add a range of DASD addresses to your parmfile
(i.e.
if your current system uses only devices 150-151 and that's all you have in
there, code it up for 150-15f so that you have some spare addresses for the
future and don't need to rerun silo just to add dasd).
By the way, the dynamic attach/detach support in RH 7.2 (2.4 kernel) looks
great! I've been attaching and detaching dasd to running Linux systems
without difficulty (a HUGE improvement, in 2.2 kernels you needed to reboot
the server to recognize the devices!).
Michael Coffin, VM Systems Programmer
Internal Revenue Service - Room 6030
1111 Constitution Avenue, N.W.
Washington, D.C. 20224
Voice: (202) 927-4188 FAX: (202) 622-6726
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: Post, Mark K [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 17, 2002 10:27 AM
To: [EMAIL PROTECTED]
Subject: Re: Add DASD
For a 2.2 system, you'll need to
1. Update your parmfile
2. Re-run silo
3. Reboot
4. dasdfmt the volume
5. mke2fs the volume
6. Mount the volume somewhere (say /mnt)
6. copy all the data from /opt to the new volume (various methods to do
this)
7. compare /opt to the new /mnt
8. rm -rf /opt/*
9. umount /mnt
10. mount the new volume on /opt
11. Update /etc/fstab with the new information
Mark Post
-----Original Message-----
From: Steve Guthrie [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 17, 2002 10:12 AM
To: [EMAIL PROTECTED]
Subject: Add DASD
How does one add DASD after installation? I have a spare DASD device with
512 MB I would like to mount on /opt. Any suggestion for Suse 2.2.16
running under VM?
Stephen J. Guthrie
Regional Sales Manager
Mantissa Corporation
2200 Valleydale Road
Birmingham, AL 35244
(800) 438-7367
