- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Corruption in /etc/lvmtab file
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2009 07:25 AM
тАО08-11-2009 07:25 AM
the system is 11.23 4640, connected to SAN.
I see the /etc/lvmtab file has these strange chars in it, possible to delete it and run vgscan -a?
where did the garbage chars come from?
#strings /etc/lvmtab
/dev/dsk/c15t0d6
/dev/dsk/c14t1d0
/dev/dsk/c14t1d6
/dev/vgP60Oracle
/dev/dsk/c14t1d1
/dev/vgJPPData
/dev/dsk/c14t1d3
/dev/vgJPPLogs
/dev/dsk/c14t1d4
/dev/vgJPPArch
/dev/dsk/c14t1d5
/dev/BCVvgp60logs
J~K{
/dev/dsk/c16t0d6
/dev/BCVvgp60arch
J~K}
/dev/dsk/c16t0d7
/dev/dsk/c16t2d0
/dev/dsk/c16t2d6
/dev/BCVvgp60data
J~K~
/dev/dsk/c16t0d1
/dev/dsk/c16t0d2
/dev/dsk/c16t0d3
/dev/dsk/c16t0d4
/dev/dsk/c16t0d5
/dev/dsk/c16t1d7
/dev/dsk/c16t2d7
/dev/dsk/c16t3d0
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2009 07:37 AM
тАО08-11-2009 07:37 AM
Solutionstrings just looks for a sequence of 4 or more printable characters followed by a newline or null character - it's possible for that sort of sequence to pop up in the binary parts of the file as well - which is what you are seeing here. It does not mean you have a corrupt file - this is perfectly normal.
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2009 07:39 AM
тАО08-11-2009 07:39 AM
Re: Corruption in /etc/lvmtab file
As Duncan pointed out those odd characters are perfectly normal. They are certainly apart of the lvm header but I've forgotten their exact purpose.
J~K{ for example, is normal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2009 07:42 AM
тАО08-11-2009 07:42 AM
Re: Corruption in /etc/lvmtab file
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2009 07:45 AM
тАО08-11-2009 07:45 AM
Re: Corruption in /etc/lvmtab file
It is normal, I think you no need to recreate it.
Regards,
LIJEESH N G
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2009 07:54 AM
тАО08-11-2009 07:54 AM
Re: Corruption in /etc/lvmtab file
To add to the understanding you now already have, the '/etc/lvmtab' also contains the VGIDs for the various volume groups. This information is "packed" into a binary format and hence isn't readable by filters that assume ASCII encoding.
The file is intended to be maintained and manipulated only the standard LVM tools --- and that's one reason it is kept in a binary format.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2009 01:21 AM
тАО08-13-2009 01:21 AM
Re: Corruption in /etc/lvmtab file
As a learning exercise, it is worth saying
that strings(1M) command is obsolete in
HP-UX 11i v3 as far as LVM is concerned.
a) There are actually two LVM files:
/etc/lvmtab (for LVM L1)
/etc/lvmtab_p (for LVM L2)
b) New command to check them in much nicer
way is:
# lvmadm -l
And yes, those extra characters in
/etc/lvmtab are normal (the others already
confired it for you).
Cheers,
VK2COT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2009 01:57 AM
тАО08-13-2009 01:57 AM
Re: Corruption in /etc/lvmtab file
My B.11.31.0803_LR lvmadm(1m) doesn't have that -l option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2009 02:03 AM
тАО08-13-2009 02:03 AM
Re: Corruption in /etc/lvmtab file
>Dennis: My B.11.31.0803_LR lvmadm(1m) doesn't have that -l option.
I think VK2COT meant 'lvmadm -t' :
http://www.docs.hp.com/en/lvm-v2/L2_whitepaper_8.pdf
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2009 02:12 AM
тАО08-13-2009 02:12 AM
Re: Corruption in /etc/lvmtab file
Of course I tried that too. Except -t just gives max numbers and no names.
(They've given you a number and taken away your name ... ;-)