lvsplit: Couldn't reallocate the logical volume: No such file or directory

[Anne Makino]

Hi All,
I am getting the following message when execute the lvsplit command:
# lvsplit /dev/vg01/lvol3
lvsplit: Couldn't reallocate the logical volume: No such file or directory

# lvdisplay /dev/vg01/lvol3
LV Name /dev/vg01/lvol3
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 1
LV Size (Mbytes) 280400
Current LE 35050
Allocated PE 70100
....

# lvdisplay /dev/vg01/lvol3b
--- Logical volumes ---
LV Name /dev/vg01/lvol3b
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 0 ==ZERO!
Current LE 0
Allocated PE 0
....

# ll /dev/vg01/*
crw-r----- 1 root sys 64 0x010000 Oct 5 2005 /dev/vg01/group
...
brw-r----- 1 root sys 64 0x010003 Oct 5 2005 /dev/vg01/lvol3
brw-r----- 1 root sys 64 0x010009 Apr 10 08:48 /dev/vg01/lvol3b
..
crw-r----- 1 root sys 64 0x010003 Oct 5 2005 /dev/vg01/rlvol3
crw-r----- 1 root sys 64 0x010009 Apr 10 08:48 /dev/vg01/rlvol3b

Any idea?

[Steven E. Protter]

Shalom,

Try the command differently:
lvsplit /dev/vg01/rlvol3

But I actually suspect there is something wrong with the logical volume.

# lvdisplay /dev/vg01/lvol3b
--- Logical volumes ---
LV Name /dev/vg01/lvol3b
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 0 ==ZERO!

That tells me the thing has already been split or broken in some other way.

SEP

[Anne Makino]

Hi Steave,
The others lvols in vg01 was split successful.

AM

[Anne Makino]

Hi Steven,
The others lvols in vg01 was split successful.

AM

[Anne Makino]

Hi All! Good News!
After applied the patch PHKL_35970 - s700_800 11.11 LVM Cumulative Patch and dependencies, the lvol was splited and merged successful!!

SR:8606365604 CR:JAGaf26236:

"Logical volumes with greater than or equal to 65536 physical extents can cause LVM commands to fail or return incorrect
results. Logical volumes with less than 65536 physical extents are not affected by this defect. This defect was introduced with PHKL_30622.
Since the maximum number of logical extents in a logical volume is 65535, this problem can only occur in mirrored
logical volumes where the number of physical extents can exceed this number. For example, a logical volume with no
mirrors contains 40000 logical extents and 40000 physical extents. Once this logical volume is mirrored, it will
contain 40000 logical extents and 80000 physical extents.
The commands affected include lvdisplay(1M), lvextend(1M), lvreduce(1M), lvsplit(1M), lvmerge(1M), pvmove(1M), and
others. Data corruption can also occur, as mirrors may not be fully resynchronized after a system panic. Below
are examples of how the problem manifests itself in the output and execution of some of the LVM commands."

www.itrc.hp.com -> patch database -> PHKL_35970 -> patch details: PHKL_35970 -> JAGaf26236

[Anne Makino]

Applied the patch PHKL_35970 - s700_800 11.11 LVM Cumulative Patch and dependencies. It was solved the issue.