lvmtab file

[Asad Malik]

Hi
output of /etc/lvmtab looks like this
root@prodora3#strings /etc/lvmtab
/dev/vg00
/dev/dsk/c1t6d0
/dev/dsk/c2t6d0
/dev/vg04
/dev/dsk/c3t1d0
/dev/dsk/c4t0d0
/dev/vg05
/dev/dsk/c3t1d1
/dev/dsk/c4t0d1
/dev/vg06
/dev/dsk/c3t1d2
/dev/dsk/c4t0d2
/dev/vg07
/dev/dsk/c3t1d3
/dev/dsk/c4t0d3
/dev/vg67
;b9o
/dev/dsk/c8t0d0

vg67 is currently not activated. what is ;b9o coming from?

Thanks

[James R. Ferguson]

Hi:

This is simply a result of the binary data mapping to some visible ascii characters.

Regards!

...JRF...

[hpuxrox]

Dont worry its fine. Nothing is corrupt. Scared me the first time I seen it too.

[Helen French]

Hi Asad:

/etc/lvmtab is a binary file. Because the strings (1) command is looking for ASCII strings in a binary file, it is normal for some strange characters to appear.

If you have some problem with that VG, then:

# mv /etc/lvmtab /etc/lvmtab.org
# vgscan -v

This will recreate the lvmtab

HTH,
Shiju

[S.K. Chan]

You can safely ignore that. The reason for the "strings" command kindda explain why, since lvmtab file is not an ascii file.

[Jeff Schussele · Accepted solution]

Hi Asad,

The lvmtab file doesn't necessarily contain only activated VGs. It can contain all VGs that are or WERE on the system & were not removed properly such as using vgexport.

Not sure what the "junk" is that's in there, but you could safely rename the lvmtab file & use vgscan to recreate it. You could even use the -pv parameter on vgscan command to preview the actions.

HTH,
Jeff

[A. Clay Stephenson]

Not a problem at all. Strings simply determines that if 3 or more bytes in a row fall into the printable ASCII range, it must be a string. By chance, some of your binary data passed that test and was sent to stdout. This is perfectly normal.

[MANOJ SRIVASTAVA]

Hi Asad

The lvmtab file is not an ascii file , strings just display the printable strings in any file so that must be a printable string , in any case if you are having problems with vg67 dot he following

1. Rename lvmtab to lvmtab.old
2. rm -r /dev/vg67
3. then run vgscan

and recreate vg67 if you need to create it.


Manoj Srivastava