- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: lvextend: Error detected when reading from fil...
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
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
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
07-05-2011 03:26 PM - edited 07-05-2011 03:33 PM
07-05-2011 03:26 PM - edited 07-05-2011 03:33 PM
What gives with this? I only found one post on this and it lead to a doc that does not exist anymore.
I unmounted it. remove the lv and recreated it with the new larger size. But what gives with the error message.
Never seen this one before.
#lvextend -l 256 /dev/vgTDMlog/lvmirrlogA
lvextend: Error detected when reading from file "/etc/lvmpvg".
#vgdisplay -v /dev/vgTDMlog
--- Volume groups ---
VG Name /dev/vgTDMlog
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 4
Open LV 4
Max PV 20
Cur PV 2
Act PV 2
Max PE per PV 1016
VGDA 4
PE Size (Mbytes) 16
Total PE 1078
Alloc PE 512
Free PE 566
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
--- Logical volumes ---
LV Name /dev/vgTDMlog/lvoriglogA
LV Status available/syncd
LV Size (Mbytes) 2048
Current LE 128
Allocated PE 128
Used PV 1
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2011 04:54 PM
07-05-2011 04:54 PM
Re: lvextend: Error detected when reading from file "/etc/lvmpvg".
suggest you try the command specifying the disk you want to extend to. Not providing the information lets lvextend pick the disk and you might not be happy with the results.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2011 10:02 PM
07-05-2011 10:02 PM
Re: lvextend: Error detected when reading from file "/etc/lvmpvg".
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2011 07:48 AM
07-06-2011 07:48 AM
Re: lvextend: Error detected when reading from file "/etc/lvmpvg".
Hello,
May be you may check if the allocation policy of
the logical volume is PVG-strict/*
# lvdisplay /dev/XXXX/YYYY |grep Allocation
if so then you can turn off this kind of allocation
(lvchange) or play with an /etc/lvmpvg file.
Hope it helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2011 01:54 PM
07-06-2011 01:54 PM
Re: lvextend: Error detected when reading from file "/etc/lvmpvg".
Steven, I tried the command:
lvextend -l 256 /dev/vgTDMlog/lvoriglogB /dev/dsk/c2t0d4
And got the same error message. Accroding to the vgdisplay I should be able to increase it.
I have free extents. And if I want it to be total size 256 then I should put 256 or 128??
LV Name /dev/vgTDMlog/lvoriglogB
LV Status available/syncd
LV Size (Mbytes) 2048
Current LE 128
Allocated PE 128
Used PV 1
--- Physical volumes ---
PV Name /dev/dsk/c2t0d3
PV Name /dev/dsk/c4t0d3 Alternate Link
PV Status available
Total PE 539
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c2t0d4
PV Name /dev/dsk/c4t0d4 Alternate Link
PV Status available
Total PE 539
Free PE 182
Autoswitch On
Proactive Polling On
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2011 01:55 PM - edited 07-06-2011 01:56 PM
07-06-2011 01:55 PM - edited 07-06-2011 01:56 PM
Re: lvextend: Error detected when reading from file "/etc/lvmpvg".
Torsten, There is no /etc/lmvpvg file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2011 02:02 PM
07-06-2011 02:02 PM
Re: lvextend: Error detected when reading from file "/etc/lvmpvg".
Cortes, yes PVG-strict is on. What does this mean?
Out of four lv's in the vg two are strict and two are PVG-strict.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2011 02:11 PM
07-06-2011 02:11 PM
Re: lvextend: Error detected when reading from file "/etc/lvmpvg".
Cortes. That did it.
lvchange -s y /dev/vgTDMlog/lvoriglogB
#lvextend -l 256 /dev/vgTDMlog/lvoriglogB
Logical volume "/dev/vgTDMlog/lvoriglogB" has been successfully extended.
Volume Group configuration for /dev/vgTDMlog has been saved in /etc/lvmconf/vgTDMlog.conf
LV Name /dev/vgTDMlog/lvoriglogB
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 256
Allocated PE 256
Used PV 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2011 05:53 AM
07-08-2011 05:53 AM
SolutionHi,
Nice to know that you solved your problem.
The "allocation policy" of the logical volume determines
how the free extents are assigned.
You may have a look to lvcreate man page for a few details.
man lvcreate:
~~
g Set a PVG-strict allocation policy.
Mirrors of a logical extent cannot share
the same physical volume group. A PVG-
strict allocation policy cannot be set on a
logical volume in a volume group that does
not have a physical volume group defined.
~~
If PVG-strict allocation policy is set, the /etc/lvmpvg file used is
the one on the system where the command is issued.
~~
Albertino