Dusting off old brain cells, but we saw one case where we had duplicate pv's happen that I am 100% sure was not our fault.
I ended up using the command to alter the uuid and make it all happy. SP2 is old - you are missing a lot of maintenance, probably fixes. Get on SP4. Marcy -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Post Sent: Tuesday, September 06, 2011 3:45 PM To: [email protected] Subject: Re: [LINUX-390] Found duplicate PV in Guest Linux SUSE 10 >>> On 9/5/2011 at 08:53 PM, Victor Hugo Ochoa Avila <[email protected]> >>> wrote: > Hello to the group. > In a Guests Linux with Suse 10 SP2 when run the vgscan command I get the > following error: > > Found duplicate PV 6p351Kfhs3GMsdtgfljqkvA9Gn32pvC7: using /dev/dasdp1 not > /dev/dasdf1 > > What is the appropriate filter to avoid this error > > My filter is: > > filter = [ "r|/dev/.*/by-path/.*|", "r|/dev/.*/by-id/.*|", "a/.*/" ] > > and my dasd list is: > > > Bus-ID Status Name Device Type BlkSz Size Blocks > ============================================================================ > 0.0.0501 active dasda 94:0 FBA 512 2048MB 4194304 > 0.0.0500 active dasdb 94:4 FBA 512 4608MB 9437184 > 0.0.0502 active dasdc 94:8 FBA 512 2048MB 4194304 > 0.0.0504 active dasdd 94:12 FBA 512 1536MB 3145728 > 0.0.0503 active dasde 94:16 FBA 512 2048MB 4194304 > 0.0.0400 active dasdf 94:20 FBA 512 80MB 163840 > 0.0.0505 active dasdg 94:24 FBA 512 1536MB 3145728 > 0.0.0506 active dasdh 94:28 FBA 512 1536MB 3145728 > 0.0.0600 active dasdi 94:32 FBA 512 1536MB 3145728 > 0.0.0601 active dasdj 94:36 FBA 512 1024MB 2097152 > 0.0.0602 active dasdk 94:40 FBA 512 2048MB 4194304 > 0.0.0603 active dasdl 94:44 FBA 512 5120MB 10485760 > 0.0.0604 active dasdm 94:48 FBA 512 5120MB 10485760 > 0.0.0605 active dasdn 94:52 FBA 512 2048MB 4194304 > 0.0.0606 active dasdo 94:56 FBA 512 10240MB 20971520 > 0.0.0607 active dasdp 94:60 FBA 512 2048MB 4194304 > 0.0.0608 active dasdq 94:64 FBA 512 2048MB 4194304 > 0.0.0609 active dasdr 94:68 FBA 512 2048MB 4194304 > 0.0.0610 active dasds 94:72 FBA 512 2048MB 4194304 > 0.0.0611 active dasdt 94:76 FBA 512 2048MB 4194304 > 0.0.0612 active dasdu 94:80 FBA 512 2048MB 4194304 > 0.0.0613 active dasdv 94:84 FBA 512 2048MB 4194304 > 0.0.0614 active dasdw 94:88 FBA 512 2048MB 4194304 > 0.0.0615 active dasdx 94:92 FBA 512 2048MB 4194304 > 0.0.0616 active dasdy 94:96 FBA 512 2048MB 4194304 > 0.0.0617 active dasdz 94:100 FBA 512 2048MB 4194304 > 0.0.0618 active dasdaa 94:104 FBA 512 2048MB 4194304 > 0.0.0619 active dasdab 94:108 FBA 512 8191MB 16777200 > 0.0.0620 active dasdac 94:112 FBA 512 431MB 884720 > 0.0.0621 active dasdad 94:116 FBA 512 17407MB 35651568 > 0.0.0622 active dasdae 94:120 FBA 512 1455MB 2981872 > > Change the filter in this way, but I keep getting the error > > filter = [ "r|/dev/.*/by-path/.*|", "r|/dev/.*/by-id/.*|", > "a|/dev/mapper/*|", "a/.*/" ] > > > What would be the correct filter for the linux guest? You shouldn't be getting duplicate PV messages in the first place. Trying to change the LVM filter isn't going to help. You need to figure out why you have two disks with the same UUID, but they're of different sizes. 0.0.0400 active dasdf 94:20 FBA 512 80MB 163840 0.0.0607 active dasdp 94:60 FBA 512 2048MB 4194304 Something is very wrong there. The only ways I can think of to get duplicate PVs is by not having multipathing set up right, or cloning minidisks and having them both active on the guest. I guess another possibility is that you've got a minidisk defined incorrectly in z/VM. You might have some overlapping extents. What does running diskmap against the user directory show you? Why do you have so many DASD volumes in the first place? They look like z/VM EDEVs from a storage array. Why not just make them big enough to hold what you need? 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/ ---------------------------------------------------------------------- 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/
