Yeah, the "root=" looks like it will cause you problems.  When you IPL from
this volume, dasdo1 will be your "old" root volume, hence giving you the
smaller file system.

When you're going to do things the way you did, and re-address the minidisks
so that they look like your current system, you need to have your parmfile,
fstab, etc., remain the same also.

Mark Post

-----Original Message-----
From: Scully, William [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 26, 2002 9:52 AM
To: [EMAIL PROTECTED]
Subject: Re: Enlarging Root File System


Here's my zipl configuration file.  Note that we normally boot off the 201
(/dev/dasda1) device, and the new larger disk was added at address 20E
(/dev/dasd01).  To put the new disk into production I swapped 201 and 20E
via the VM Directory.


[defaultboot]
default=ipl

[ipl]
target=/mnt/boot/zipl
image=/mnt/boot/kernel/image
#ramdisk=/boot/initrd
parameters="dasd=0200-21f root=/dev/dasdo1 noinitrd"

[dumptape]
target=/boot
dumpto=/dev/rtibm0


It was placed into production using the command:  zipl -c /etc/zipl.new.root
On further investigation (and from a suggestion off-list from Willem
Konynenberg) I suspect that I have the "parameters" value incorrect, as this
seems to be the only explaination of what's gone wrong here.  Since I'm
working with a production server I can't bounce and test at will.  (The
changes must be scheduled.)  If someone can confirm this suspicion that
would be very helpful to me.

Thanks!

-----Original Message-----
From: Ihno Krumreich [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 26, 2002 3:43 AM
To: [EMAIL PROTECTED]
Subject: Re: Enlarging Root File System


Hello,

how have you called zipl?
can you show us the zipl.conf please?

regards

Ihno

On Sun, Aug 25, 2002 at 07:53:28PM -0400, Scully, William wrote:
> For Mark Post and anyone else with some ideas, here's some details from a
-heavily- edited console log.  To restate the problem, the 201 disk, which
was substantially increased in size, has no additional free space when
mounted as root.  But mount it at /mnt and it's 63% full.
>
>
>
> IPL 201
>
> dasd:initializing...
> dasd:Registered successfully to major no 94
> dasd(eckd):ECKD discipline initializing
> dasd(eckd):0201 on sch 6: 3390/0A(CU:3990/01) Cyl:1000 Head:15 Sec:224
> dasd(eckd):0201 on sch 6: 3390/0A(CU:3990/01): Configuration data read
> dasd(eckd):020E on sch 5: 3390/0A(CU:3990/04) Cyl:650 Head:15 Sec:224
> dasd(eckd):020E on sch 5: 3390/0A(CU:3990/04): Configuration data read
>
> dasd:waiting for responses...
> dasd(eckd):/dev/dasdb(94:4),0201@0x6:(4kB blks): 720000kB at 48kB/trk
compatible disk layout
> dasd(eckd):/dev/dasdo(94:56),020e@0x5:(4kB blks): 468000kB at 48kB/trk
classic disk layout
>
> df
> Filesystem           1k-blocks      Used Available Use% Mounted on
> /dev/dasdb1             453292    420672      9224  98% /
> /dev/dasdo1             453292    420672      9224  98% /mnt
>
> cat /proc/dasd/devices
> 0201(ECKD) at ( 94:  4) is dasdb:active at blocksize: 4096, 180000 blocks,
703 MB
> 020e(ECKD) at ( 94: 56) is dasdo:active at blocksize: 4096, 117000 blocks,
457 MB
>
> shutdown -h now
>
> DEF 201 1201
> DASD 1201 DEFINED
> DEF 20E 201
> DASD 0201 DEFINED
> DEF 1201 20E
> DASD 020E DEFINED
> IPL 201
>
> dasd:initializing...
> dasd:Registered successfully to major no 94
> dasd(eckd):ECKD discipline initializing
> dasd(eckd):0201 on sch 5: 3390/0A(CU:3990/04) Cyl:650 Head:15 Sec:224
> dasd(eckd):0201 on sch 5: 3390/0A(CU:3990/04): Configuration data read
> dasd(eckd):020E on sch 6: 3390/0A(CU:3990/01) Cyl:1000 Head:15 Sec:224
> dasd(eckd):020E on sch 6: 3390/0A(CU:3990/01): Configuration data read
> dasd:waiting for responses...
> dasd(eckd):/dev/dasdb(94:4),0201@0x5:(4kB blks): 468000kB at 48kB/trk
classic disk layout
> dasd(eckd):/dev/dasdo(94:56),020e@0x6:(4kB blks): 720000kB at 48kB/trk
compatible disk layout
>
> mount /dev/dasdo1 /mnt
>
> df
> Filesystem           1k-blocks      Used Available Use% Mounted on
> /dev/dasdb1             453292    420636      9260  98% /
> /dev/dasdo1             708568    420476    252100  63% /mnt
>
> cat /proc/dasd/devices
> 0201(ECKD) at ( 94:  4) is dasdb:active at blocksize: 4096, 117000 blocks,
457 MB
> 020e(ECKD) at ( 94: 56) is dasdo:active at blocksize: 4096, 180000 blocks,
703 MB

--
Ihno Krumreich            [EMAIL PROTECTED]
SuSE Linux AG             S390 & zSeries
Deutschherrnstr. 15-19    +49-911-74053-439
90429 N|rnberg            http://www.suse.de

Reply via email to