Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2010 12:39 PM
тАО05-04-2010 12:39 PM
I have dicovered that a mirrored LVOL between two storage array is actually misconfigured, it means that some parts of the mirror are in one array (the PV1 and PV2 columns), so if one of the array fails, everything fails. This LVOL is created from multiple PVOLs (16 for one array and other 16 for the second array). So I created a second mirror copy in one of the array in order to fix this problem. The thing is that I want to fix this properly and eliminate those misconfigured LEs pointing to the same PV. If I erased those 32 misconfigured PVs, lefting only those 16 new which I am sure are good. After lvreduce, is it everything to be operational?. I've tryed with a small lab and it works, but doing it live for a production system is something else...
Thanks very much for any hint.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2010 01:35 PM
тАО05-04-2010 01:35 PM
Re: LVREDUCE
You should have no problems, but to be sure it would be good that you attached the output of "lvdisplay -v /dev/vgXX/lvolX"
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2010 02:16 PM
тАО05-04-2010 02:16 PM
Re: LVREDUCE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2010 11:20 PM
тАО05-04-2010 11:20 PM
Re: LVREDUCE
lvreduce -m 1 /dev/vgsapdata1_p/lvsapdata1 /dev/dsk/cxtydz
rgs,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-05-2010 12:48 AM
тАО05-05-2010 12:48 AM
SolutionYou have the mirror not well configured. The logical volume has "Allocation non-strict" and this means that mirrors of a logical extent can share the same physical volume, as you can see:
--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2 Status 2 PV3 PE3 Status 3
06398 /dev/disk/disk213 00000 current /dev/disk/disk213 00001 current /dev/disk/disk298 00000 current
This happens from disk213 on. As you have two mirrors, you should "lvreduce" disks of the two firsts columns. After that, you should change the logical volume allocation policy to "strict" and redo the mirror.
# lvreduce -m 1 /dev/vgsapdata1_p/lvsapdata1
# lvchange -s y /dev/vgsapdata1_p/lvsapdata1
And then, redo the mirror with the proper disks. Maybe you want confirmation of this procedure from other forum experts.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-05-2010 05:06 AM
тАО05-05-2010 05:06 AM
Re: LVREDUCE
Thanks very much.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-05-2010 05:09 AM
тАО05-05-2010 05:09 AM
Re: LVREDUCE
# lvreduce -m 0 /dev/vgsapdata1_p/lvsapdata1
Cause leaving a mirror copy is the scenario that doesn't work well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-05-2010 05:35 AM
тАО05-05-2010 05:35 AM
Re: LVREDUCE
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-05-2010 08:30 AM
тАО05-05-2010 08:30 AM
Re: LVREDUCE
move the LV from one array to deired array..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-07-2010 08:24 AM
тАО05-07-2010 08:24 AM