Holger,

I'm curious why you say that.  He did a tar from the original file system to
the new file system.  The metadata should have already been in place from
the mke2fs command against the new volume.  Other people have used this
process multiple times without this kind of problem showing up.

Mark Post

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


Folks,

You will have to extend your ext2 filesystem as well, since the ext2
metatdata are
not automatically aware of the volume expansion.
Check http://sourceforge.net/projects/ext2resize/ for additional
information-

Best Regards
        Holger Smolinski
--
Dr. Holger Smolinski, Tech. Planning (Storage I/O) for Linux on zSeries
IBM Deutschland Entwicklung GmbH,Schönaicher Str. 220, 71032 Böblingen
FAX: +49-7031-16-3456, Tel. +49-7031-16-4652


|---------+---------------------------->
|         |           Ihno Krumreich   |
|         |           <[EMAIL PROTECTED]>   |
|         |           Sent by: Linux on|
|         |           390 Port         |
|         |           <[EMAIL PROTECTED]|
|         |           IST.EDU>         |
|         |                            |
|         |                            |
|         |           26.08.02 09:42   |
|         |           Please respond to|
|         |           Linux on 390 Port|
|         |                            |
|---------+---------------------------->
 
>---------------------------------------------------------------------------
---------------------------------------------------|
  |
|
  |       To:       [EMAIL PROTECTED]
|
  |       cc:
|
  |       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