LVM-partitioned DASD cannot be formatted when returning from "Partition disk" screen

[bugproxy]

== Comment: #0 - Michael Roesch - 2016-02-11 05:08:12 ==
An LVM-partitioned DASD cannot be formatted if you have not chosen to do so on first-time selecting the DASD for installation.

Reproduction:

- Select DASD (which I used for an installation with LVM before)
- Format the Device -> no
- Finish
- Partitioning method: manual

- Menu "Partition disks":
DASD 0.0.5d32 (ECKD) - 7.4 GB IBM S390 DASD drive
> #1 500.0 MB ext2
> #2 6.9 GB K lvm
> 49.2 kB FREE SPACE
LVM VG rootVG, LV rootLV - 6.9 GB Linux device-mapper (linear)
> #1 6.9 GB ext4

- Go Back

- Select "Configure direct access storage devices (DASD)"

- Select previous DASD again; DASD is displayed as 0.0.5d32 (online)

- Format the device -> Yes

- Error:

Installation step failed
An installation step failed. You can try to run the failing item again from the menu, or skip it and choose something
else. The failing step is: Configure direct access storage devices (DASD)

/proc/partitions looks like this:

major minor #blocks name

   1 0 40000 ram0
   1 1 40000 ram1
   1 2 40000 ram2
   1 3 40000 ram3
   1 4 40000 ram4
   1 5 40000 ram5
   1 6 40000 ram6
   1 7 40000 ram7
   1 8 40000 ram8
   1 9 40000 ram9
   1 10 40000 ram10
   1 11 40000 ram11
   1 12 40000 ram12
   1 13 40000 ram13
   1 14 40000 ram14
   1 15 40000 ram15
  94 0 7212240 dasda
  94 1 488304 dasda1
  94 2 6723792 dasda2
 252 0 6721536 dm-0

I have attached the syslog that was created during my test.

== Comment: #8 - Hendrik Brueckner <email address hidden> - 2016-02-26 03:19:28 ==
Opened the below Debian bug report and attached the problem fixes:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815918

[bugproxy (bugproxy)]

Default Comment by Bridge

[Dimitri John Ledkov (xnox)]

s390-dasd (0.0.35ubuntu1) xenial; urgency=low

  * Merge from Debian unstable. Remaining changes:
    - Bump s390-dasd menu item, to be before disk-detect.

s390-dasd (0.0.35) unstable; urgency=low

  * Team upload

  [ Hendrik Brueckner ]
  * dasdfmt: detect format status and improve handling (Closes: #815918)
    - report user error if disk is in use
    - detect and properly handle already formatted DASDs
    - correct and improve <Go back> handling
  * Detect if a DASD is already configured. (Closes: #815912)

  [ Updated translations ]
  * French (fr.po) by Christian Perrier
  * Japanese (ja.po) by Kenshi Muto
  * Portuguese (Brazil) (pt_BR.po) by Adriano Rafael Gomes
  * Portuguese (pt.po) by Miguel Figueiredo

s390-dasd (0.0.34) unstable; urgency=medium

  [ Colin Watson ]
  * Use HTTPS for Vcs-* URLs, and link to cgit rather than gitweb.

  [ Hendrik Brueckner ]
  * dasd-config: always list available DASDs for selection and configuration
    (Closes: #666399)

 -- Dimitri John Ledkov <email address hidden> Mon, 07 Mar 2016 12:13:59 +0000

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-03-10 03:43 EDT-------
I have just tried to reproduce this problem in expert mode using an LVM-partitioned DASD. When trying to low-level format the DASD, the error message now is clear and says that the disk is in use and could be a member of an LVM volume group.
In my opinion, the problem is fixed.