Ubuntu
lvm2 package

Parse error when running "...display"-Tools

Bug #604572 reported by Johannes
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
lvm2 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: lvm2

Hey nerd-friends,

when I use the "...display"-Tools, for example lvdisplay or pvdisplay, I get this error:
> Parse error at byte 7 (line 1): expect a value

Thanks for helping

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: lvm2 2.02.54-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Mon Jul 12 14:08:37 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.utf8
SourcePackage: lvm2

Revision history for this message
Johannes (magicjojo) wrote :
Revision history for this message
Steve Beattie (sbeattie) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
Revision history for this message
Piotr Auksztulewicz (p-launchpad-net-hasiok-net) wrote :

I had a similar problem today when running *any* LVM tool, including vgbackup/restore, so I was basically unable to do anything with the LVM subsystem. The error message was:

  Parse error at byte 5 (line 1): unexpected token

I managed to figure (by strace'ing the vgdisplay process) that it is caused by corrupted /etc/lvm/cache/.cache file (most likely fscked up after a crash I had). Solution: delete the .cache file and run vgdisplay or whatever and it is recreated. I have verified that the recreated file is identical to the one I had on backup media.

So it is not much of a bug, but just a cryptic error message. It'll be prudent to change it to something meaningful - or just plainly recreate the cache file in such case and stop whining.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lvm2 (Ubuntu):
status: New → Confirmed
Revision history for this message
KARARI (martinkarari) wrote :

Thanks for above. I had the same issue while creating physical volume as below.

pvcreate /dev/sda4

deleting /etc/lvm/cache/.cache solved issue!

Revision history for this message
KARARI (martinkarari) wrote :

Has this been solved in newer versions of ubuntu?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.