Hi Mark,

Indeed I didn't expect SP3 would be entitled for it, but SP4 might. We do have 
a support agreement. So we could go that path or move into SLES12 SP1 asap. I 
guess the latter would be even a better option. We do plan for SLES12 and this 
server would be one of the first to go into the new version anyway.

Thanks for explaining the patch comment. Good to know it still works for LDL 
disks.

Actually I had to get the lvm2 package from another SP3 source disk and 
installed it with rpm. We are now back on the SP3 base version and the LVM is 
mounted once again.

Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
Berry van Sleeuwen

-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Post
Sent: Tuesday, July 05, 2016 7:18 PM
To: [email protected]
Subject: LVM on unpartitioned disks (Was: RE: SLES12 + EDEV + bug)

>>> On 7/1/2016 at 07:55 PM, "van Sleeuwen, Berry"
>>> <[email protected]>
wrote:
> I have been looking for the fix for bug 948859. Indeed I found an
> update in the SLES12 SP1 fixes. Might this fix become available for SLES11 as 
> well?

SLES11 SP3 is out of support unless your site purchased Long-Term Servicepack 
Support.

If you don't have LTSS, but you have a support agreement, you might be able to 
get a fix for this in SLES11 SP4.

> Also, the comment in the patch states: "Allow creation of PVs on
> unpartitioned DASD devices formatted with CDL. (bsc#948859,
>   bsc##946217)". Is the only for CDL disks and not for LDL disks?

What the comment says is actually "Only not support unpartitioned DASD device 
with CDL formatted. (bnc#948859#946217)"  Which, when you unwind the statement, 
means LDL formatted DASD volumes will be supported, whether a partition was 
used (/dev/dasd?1) or not (/dev/dasd?).  CDL formatted volumes will only be 
supported if a partition was used.

> Today I have updated an SLES11 SP3 and I can't access the LVM anymore.
> This is an LVM based on unpartitioned LDL formatted disks.

If you don't have a support agreement and can't get a fix that way, you can 
revert the update to lvm2:
zypper in --oldpackage lvm2-${version}
where ${version} is the prior version you had installed.


Mark Post

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
[email protected] 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/
This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, Atos’ liability cannot be triggered for the message 
content. Although the sender endeavours to maintain a computer virus-free 
network, the sender does not warrant that this transmission is virus-free and 
will not be liable for any damages resulting from any virus transmitted. On all 
offers and agreements under which Atos Nederland B.V. supplies goods and/or 
services of whatever nature, the Terms of Delivery from Atos Nederland B.V. 
exclusively apply. The Terms of Delivery shall be promptly submitted to you on 
your request.

Reply via email to