06-27-2002 02:34 AM
Solved! Go to Solution.
06-27-2002 02:39 AM
I havee seen this on a couple of our boxes. Not sure why it happens though
You can recreate lvmtab by moving it to lvmtab.bak and performing a
This will recreate lvmtab. The only problem being that it won't be in descending order by volume group
for more options
Hope this helps
06-27-2002 02:47 AM
you have the volume group with the physical disk information in it.It has the table where the volume groups and the associated physical volumes in each group.
If sometime your lvmtab file is corrupt then
you should do a vgscan -a
to rebuild the lvmtab file.
06-27-2002 03:04 AM
Your lvmtab is not corrupt.
files /etc/lvmtab reports the file is data.
strings /etc/lvmtab extracts the printable characters.. which do not always report just device files.
A vgscan recreation can mess up your pvlinks configuration(alternate paths) very easily causing serious perf degradation.. make sure you know what you're doing.
06-27-2002 03:07 AM
the other vgs will also be swapped. vgscan recreates in numberical order of device file...
06-27-2002 03:21 AM
/etc/lvmtab is NOT a textfile, and should be edited manually.
"strings /etc/lvmtab" will also show some rubbisch in many cases. "strings" only tries to filter out non-text data, but can never really know what is what.
06-27-2002 04:00 AM
lvmtab is not a text file. It normally contains some unreadable charecters. It is not because of somebody is doing vi. If U doubt like this it is always better to keep a copy of lvmtab. For seeing the contents of lvmtab
Best of luck
06-27-2002 04:28 AM
The /etc/lvmtab is a binary data file. As noted, 'strings /etc/lvmtab' will expose the printable characters. The file is not and should not be editted manually in any fashion.
The file actually contains the physical device paths for each volume group defined to the system. In addition, the VGID (Volume Group Identification) and some other state information about each volume group is recorded.
As Bill has aptly noted, do *not* capraciously run 'vgscan'. This may reorder the primary and alternate paths to a volume group leading to non-optimal performance. It is the order of the paths in /etc/lvmtab that determines which is a primary and which as an alternate (secondary) pvlink. For vg00, boot information may become incorrect due to reordering of devices following a 'vgscan'. See the 'vgscan' man pages for more information.