> On Oct 2, 2015, at 10:38 PM, Grzegorz Powiedziuk <gpowiedz...@gmail.com> 
> wrote:
> 
>> 
>> On Oct 2, 2015, at 8:15 PM, Mark Post <mp...@suse.com> wrote:
>> 
>>>>> On 9/30/2015 at 10:59 PM, Grzegorz Powiedziuk <gpowiedz...@gmail.com> 
>>>>> wrote: 
>>> I think I might have found a small bug in latest update for SLES12  so this 
>>> is just a FYI for everyone who made the same mistake I did. 
>> -snip- 
>>> Everything was working fine, until I did an update. Something has changed 
>>> in 
>>> the way LVM recognizes physical  devices and it totally brakes the whole 
>>> system. It breaks all the parts where LVM is being called which includes 
>>> the 
>>> little initrd which is loaded by  zipl during the first stage of boot. 
>> 
>> I was able to reproduce this situation.  I did an install, with /home on a 
>> PV using /dev/dasdb (an EDEV) and not /dev/dasdb1. After updating to the 
>> current maintenance level, pvscan doesn't show any PVs out there.  There 
>> were a total of 259 updates that got applied.  I did the kernel first, since 
>> that's an easy one to isolate.  It didn't cause the problem.  So, not sure 
>> just yet what did.

I did more playing around and I found out that that LVM source I’ve downloaded 
is working fine out from box. These changes I made to the source code were not 
necessary. 
SLES version of LVM has to have some changes. 


So I’ve checked what was installed with latest update for LVM and here it is (I 
guess I should have done it on the first place) :

patch: SUSE-SLE-SERVER-12-2015-314
- LVM2 does not support unpartitioned DASD device which has special             
                                                                                
               │
 │  format in the first 2 tracks and will silently discard LVM2 label           
                                                                                
                 │
 │  information written to it by pvcreate. Mark this type of device as          
                                                                                
                 │
 │  unsupported. (bsc#894202)

and from suse.com
Skip unpartitioned DASD devices, they are not supported. (bsc#894202)

I guess that’s it. They wanted to fix things If I understand this correctly but 
this might put in danger some users with older versions. 

Thanks
Gregory Powiedziuk







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

Reply via email to