Comment 4 for bug 1582728

Hi Frank,

I used ickdsf cpvol format under Zvm (which is what cpfmtxa calls) to format the dasd as perm space (entire volume) before I used it in my Ubuntu guest. This volume is a mod 9.

From Maint630:

Ickdsf
Console
Console
Cpvol format unit(d700) verify(ahd700) volid(ahd700)

Once Ubuntu is fully installed and you log back in, dasdfmt works fine, it's just during the installation process.

I've also bypassed the issue by doing a cms format on the minidisk before I installed Ubuntu on the disk, this causes Ubuntu to think the disk is already lowlevel formatted and proceeds with the install with no issues. (Still can't do a dasdfmt , but it uses the dasd for the install)

From Maint630:

Link ahubovpn 200 999 mw
Format 999 k (blksize 4096

The problem with this is, if I don't have z/VM in the environment and I'm using ECKD dasd then I have no way of low level formatting it before I install Ubuntu.

The minidisk statement I used for this guest is listed below:

  MDISK 0200 3390 0001 END AHD700 MR RAH WAH MAH

I can recreate this issue at any time, so if you need the output from the ickdsf run or any additional output please let me know.

I'm using the distro I downloaded from this link - http://partners.ubuntu.com/ibm , it's dated April 20 2016.

Thanks,

Andy Hartman

Senior Consultant
Mainline Information Systems
Cell/Phone: 440.785.4890
Email: <email address hidden>

Notice: This e-mail and files transmitted with it are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you are not one of the named recipient(s) or otherwise have reason to believe that you received this message in error, please immediately notify sender by e-mail, and destroy the original message.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Frank Heimes
Sent: Tuesday, May 17, 2016 4:20 PM
To: Andrew Hartman <email address hidden>
Subject: [Bug 1582728] Re: DASDFMT fails with a buffer overflow error

We have similar MDISK setups in our machine, but mostly 3390 0001 10016 (so mod9s), but did not saw such a overflow situations yet.
We cpfmtxa format our disks once and label them (but with perm 0-end) - are you using cpfmtxa too ?
So 'sudo dasdfmt -b 4096 -f /dev/dasdf' recently worked for me ...

Looks like your 9336 EDEV devices (a and b) are fine.

Please can you paste your MDISK settings of the user direct (at least for the disk 0200), the 'lsdasd -a' output and the output of 'dasdfmt --version'?

Thanks

Nevertheless a buffer overflow is not acceptable ...

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1582728

Title:
  DASDFMT fails with a buffer overflow error

Status in Ubuntu on IBM z Systems:
  New
Status in s390-tools package in Ubuntu:
  New

Bug description:
  During installation, either through the menu or in an ssh session ,
  dasdfmt fails with a buffer overflow error and does not format the
  dasd volume. The volume is a z/VM minidisk - defined as 1 to end, this
  is common in this environment. The DASD volume was formatted from z/VM
  as a minidisk volume. These are the same steps taken for other
  distributions running under z/VM. I've attached some screen shots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1582728/+subscriptions
This e-mail and files transmitted with it are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you are not one of the named recipient(s) or otherwise have reason to believe that you received this message in error, please immediately notify sender by e-mail, and destroy the original message.