|
There is nothing in the LVM commands except lvscan that gives location info.
LVSCAN list th lv in the other I created them.
However, the graphical tool lists the names on the gui cyinder displays backwards.
So for installer and the gui, it would be / could be programmer's choice of what gets created fisrt, second, last as all the LVM commands are in memory before it is created.
Without having the specs of LVM it is not possible to determine the location of an LV inside a VG.
I think the LV go on front to back and some more attention to detaill needs to be in the Linux installers and gui tools.
I don't think it is as much as a performace hit as you indicate but it sure is a foo paw of an industrry's lack of what is important.
The file system's, the installer, the (gu)i tools, The file system's, the installer, the (gu)i tools, The file system's, the installer, the (gu)i tools, The file system's, the installer, the (gu)i tools, The file system's, the installer, the (gu)i tools, he file system's, the installer, the (gu)i tools, and finally the file system's, the installer, the (gu)i tools.
Ubuntu's programmer for LVM is even more out to lunch on this matter. To the point that Ubuntu LVM is only available via voodoo magic.
SJ
__________________
Do the Math
|