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
Forums
Discussions
Discussions
Discussions
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
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
10-22-2007 04:41 AM
10-22-2007 04:41 AM
lvm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2007 04:46 AM
10-22-2007 04:46 AM
Re: lvm
"Strict allocation" simply means that the mirrored extents of a logical volume must reside on different physical disks or physical volume groups.
Mirroring is a high-availablity technique. If you allowed mirrored extents to reside on the same physical disk, failure of that disk would render ALL of the data unavailable. That's not "high availability".
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2007 04:47 AM
10-22-2007 04:47 AM
Re: lvm
Check this link out.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1118436
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2007 04:47 AM
10-22-2007 04:47 AM
Re: lvm
That should explain it fully.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2007 01:51 PM
10-22-2007 01:51 PM
Re: lvm
=================
The purpose of disk mirroring is to have the data stored on more than one disk
in case of a disk failure. The lvcreate command sets the "strict" allocation
policy by default. This means that mirrors of a logical extent cannot share
the same physical volume.
The default value can be overidden by using the "-s" option with the lvcreate
(1M) or lvchange(1M) commands. The possible values for the "-s" option are:
1)y Set a strict allocation policy. Mirrors of a logical extent cannot share the same physical volume. This is the default policy.
2)g Set a PVG-strict allocation policy. Mirrors of a logical extent cannot share the same physical volume group. To learn more about physical volume groups see the vgcreate(1M) man page.
3)n Do not set a strict or a PVG-strict allocation policy. Mirrors of a logical extent can share the same physical volume group.
WK