Re: Moving zLinux to a bigger disk - solved

2018-07-04 Thread Jan Höppner
Hi Donald,

> Just FYI... I spent many hours tinkering with VM DRR and Linux dd and
> different experiments of formatting etc etc. I had a case open with Red
> Hat, which they eventually pretty much gave up on and gave me the source
> code for fdasd and dasdfmt (which is where I learned of the --mode expand
> option in the first place. It’s not in the man pages.)
> 

that made me worry for a second. I just checked on a fresh RHEL7.5
installation and the modes option is fully documented in the man pages.

Regards,
Jan

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: Moving zLinux to a bigger disk - solved

2018-06-29 Thread Donald Russell
Peter,
THANK YOU !! Using fdasd option u fixed it up. I was then able to expand
the file system and I now have a happy RHEL system on a mod-27 with lots of
spare space.

Just FYI... I spent many hours tinkering with VM DRR and Linux dd and
different experiments of formatting etc etc. I had a case open with Red
Hat, which they eventually pretty much gave up on and gave me the source
code for fdasd and dasdfmt (which is where I learned of the --mode expand
option in the first place. It’s not in the man pages.)

Like so many things, when you know how, it’s simple. Once again, the
informal, no-charge listserv community out-performs the paid-for official
support. TGFL - Thank God For Listserv.  LOL

Thanks again.
Donald Russell


On Fri, Jun 29, 2018 at 05:01 Peter Oberparleiter 
wrote:

> On 29.06.2018 00:10, Donald Russell wrote:
> > On Thu, Jun 28, 2018 at 14:27 Donald Russell 
> wrote:
> >> The dasdfmt -b 4096 --mode=expand worked great.   Started formatting the
> >> disk at track 150240 as expected.  But then fdasd choked saying only the
> >> first 10016 cylinders are formatted so I can’t create the new larger
> >> partition.
> >>
> >> How can I coerce fdasd into doing the right thing? Whatever fdasd is
> >> looking at for that cylinder count I expected dasdfmt to update.
> >>
> >> Where is that data, maybe I can just zap it with some other tool like
> cms
> >> pipe read/write track.
>
> fdasd is looking at the DASD's VTOC, specifically at the format 5 DSCB
> that is supposed to list free space extents on the volume. The 'dasdfmt
> --mode expand' call doesn't add the newly formatted extent to this DSCB,
> therefore fdasd assumes that that it is not formatted.
>
> This is a bug/limitation in dasdfmt/fdasd and we plan to fix this in a
> future version of s390-tools.
>
> In the meantime, you can try the following:
>
> # fdasd /dev/dasd...
> u ('re-create VTOC re-using existing partition sizes')
> y ('yes')
> w ('write table to disk and exit')
>
> You need to perform these steps TWICE, or fdasd will terminate with a
> "BUG..." statement when you try to create/change partitions afterwards.
>
>
> Regards,
>   Peter Oberparleiter
>
> --
> Peter Oberparleiter
> Linux on Z Development - IBM Germany
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/