Re: Thinly provisioned dasd and SuSE

2021-05-07 Thread Jan Höppner
On 06/05/2021 19:55, Christer Solskogen wrote:
> On Thu, May 6, 2021 at 5:13 PM Jan Höppner  wrote:
> 
>> On 06/05/2021 09:00, Christer Solskogen wrote:
>>> When installing SuSE (15SP2) I cannot use the installer to format a 3390
>>> which is thinly provisioned from the disk system. The installer will fail
>>> when formatting.
>>> I can do a dasdfmt manually with "-M full" before starting the
>>> installation, and that will work. Is this a known bug?
>>
>> Hi Christer,
>>
>> I suspect there is still an issue with parallel formatting and
>> thin-provisioned DASD devices in SLES15SP2. Do you have any logs
>> or more details how this failure is expressed?
>>
>> I'll get in touch with Mark from Suse as he fixed the parallel
>> formatting in SP3. I reckon we need these changes for SP2, too.
>>
>>
> I suspect it's a bug in dasdfmt, because "-M full" is supposed to be the
> default (according to the man page), but without that option
> it will use quick instead.
> 

For thin-provisioned devices the default is -M quick as only the first
two tracks of a DASD need to be formatted to store the necessary meta
information like the VTOC etc. The rest of the DASD is wiped during
this initialisation step (See man 8 dasdfmt also).

About the failure again, I was probably wrong with my first assumption
that it is related to the parallel formatting. I suspect something else
and already forwarded the necessary information to Suse via our service
process.
However, this is still pure speculation as we'd need more data (e.g. logs)
to analyse the issue properly. And as this occurred in the SLES installer
I'd recommend to file a bug against Suse to clarify the problems you're
facing.

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://www2.marist.edu/htbin/wlvindex?LINUX-390


Re: Thinly provisioned dasd and SuSE

2021-05-06 Thread Jan Höppner
On 06/05/2021 09:00, Christer Solskogen wrote:
> When installing SuSE (15SP2) I cannot use the installer to format a 3390
> which is thinly provisioned from the disk system. The installer will fail
> when formatting.
> I can do a dasdfmt manually with "-M full" before starting the
> installation, and that will work. Is this a known bug?

Hi Christer,

I suspect there is still an issue with parallel formatting and
thin-provisioned DASD devices in SLES15SP2. Do you have any logs
or more details how this failure is expressed?

I'll get in touch with Mark from Suse as he fixed the parallel
formatting in SP3. I reckon we need these changes for SP2, too.

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://www2.marist.edu/htbin/wlvindex?LINUX-390


Re: dasdfmt assistance

2018-07-10 Thread Jan Höppner
On 09.07.2018 21:25, Frank M. Ramaekers wrote:
> Same result:
>
> dasdfmt -b 4096 -d cdl  -k -p -y -f /dev/dasdi
> Try 'dasdfmt --help' for more information.
>
> Frank M. Ramaekers Jr.
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark 
> Post
> Sent: Monday, July 9, 2018 2:22 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: dasdfmt assistance
>
 On 7/9/2018 at 02:39 PM, "Frank M. Ramaekers"  
 wrote:
>> This response doesn't offer much help.  Can anyone assist?
>> dasdfmt -b 4096 -d cdl -f /dev/dasdi -k -p -y Try 'dasdfmt --help' for
>> more information.
>
> Does this work better?
> dasdfmt -b 4096 -d cdl  -k -p -y -f /dev/dasdi
>
>
> Mark Post
>

Hi,

just to clear things up, the option -f/--device was deprecated
for quite some time and got removed with s390-tools 1.37.1:

https://www.ibm.com/developerworks/linux/linux390/s390-tools-1.37.1.html

Also, I agree that the message "Try --help..." isn't very helpful.
There should be a bit more logic to it and tell the user what
option was wrongly specified (will look into it).

I saw that you were able to resize your volume. Are your dasdfmt issues
solved? If not, let me know.

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-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/