1753875 Members
7587 Online
108809 Solutions
New Discussion юеВ

Re: Can't lvextend

 
SOLVED
Go to solution
Terrence
Regular Advisor

Re: Can't lvextend

It doesn't say contiguous.

#lvdisplay -v /dev/data/u01 |more
--- Logical volumes ---
LV Name /dev/data/u01
VG Name /dev/data
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule striped
LV Size (Mbytes) 28000
Current LE 7000
Allocated PE 7000
Stripes 2
Stripe Size (Kbytes) 4
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c4t0d0 3500 3500
/dev/dsk/c6t0d1 3500 3500
Joseph C. Denman
Honored Contributor

Re: Can't lvextend

I'm not sure of the problem????? Someone can help you but, The rabbit comment:::

When you assign more than 7 points to a post, a rabbit shows up on the post. Most forum users will think the issue has been resolved. You probably want to start a new post and paste the info from this one into it.

...jcd...
If I had only read the instructions first??
Steven E. Protter
Exalted Contributor

Re: Can't lvextend

Shalom,

lvdisplay will show you.

It says allocation strict.

Which probably means my lvchange command will work.

Try it, it can't hurt anything.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Joseph C. Denman
Honored Contributor

Re: Can't lvextend

YEP, Steven is correct. Check out your allocation line.

...jcd...
If I had only read the instructions first??
Patrick Wallek
Honored Contributor

Re: Can't lvextend

I think that is incorrect. I don't think strict has anything to do with this.

If you look at the man page for lvcreate you will see that '-S y', which is the default, really only affects mirrors. To summarize the man page: "Mirrors of a logical extent cannot share the same physical volume." So since this is not mirrored the strict allocation policy really has no effect.

You could try doing an 'lvchange -S n /dev/data/u01' but I don't think it would help.

I think the basis of the error is the "Couldn't retrieve the list of the physical volumes...."

I'm not sure why that is coming up especially when vgdisplay looks OK and you said /etc/lvmtab looks OK. If you have a support contract it may be time to involve HP as well.
Terrence
Regular Advisor

Re: Can't lvextend

lvchange did not solve the issue. Here is my lvmtab:

#strings /etc/lvmtab
/dev/vg00
/dev/dsk/c1t2d0
/dev/dsk/c2t2d0
/dev/data
/dev/dsk/c4t0d0
/dev/dsk/c6t0d1
/dev/dsk/c4t0d1
/dev/dsk/c6t0d0
/dev/dsk/c6t0d7
/dev/dsk/c4t0d7

I will open a call with HP. Sigh