Bug#508656: lvm2: parse error and file descriptior left open

Ross Boylan RossBoylan at stanfordalumni.org
Sat Dec 13 18:12:17 UTC 2008


Package: lvm2
Version: 2.02.39-6
Severity: normal

On the latest upgrade the terminal shows

<QUOTE>
Setting up lvm2 (2.02.39-6) ...
Installing new version of config file /etc/init.d/lvm2 ...
Setting up LVM Volume GroupsFile descriptor 47 left open
File descriptor 48 left open
File descriptor 49 left open
  Reading all physical volumes.  This may take a while...
  Found volume group "LITTLEBOY" using metadata type lvm1
  Found volume group "FATMAN" using metadata type lvm1
  Found volume group "daisy" using metadata type lvm2
File descriptor 47 left open
File descriptor 48 left open
File descriptor 49 left open
  Parse error at byte 3306 (line 253): unexpected token
  Parse error at byte 3306 (line 253): unexpected token
  Parse error at byte 3306 (line 253): unexpected token
  Parse error at byte 3306 (line 253): unexpected token
  Parse error at byte 3306 (line 253): unexpected token
  Parse error at byte 3306 (line 253): unexpected token
  Parse error at byte 3306 (line 253): unexpected token
  Parse error at byte 3306 (line 253): unexpected token
  Parse error at byte 3306 (line 253): unexpected token
  9 logical volume(s) in volume group "LITTLEBOY" now active
  5 logical volume(s) in volume group "FATMAN" now active
  10 logical volume(s) in volume group "daisy" now active
.
</QUOTE>

The parse errors are longstanding; I see them whenever the system
starts.  I don't recall seeing the file descriptor warnings before.

I have been assuming the parse errors are some garbage after the end
of the relevant file; everything seems to be working OK.  I've been
unable to identify what file has the problems.

I would like to identify and fix the problem.  Ideally we could
identify what caused the corruption in the first place, but it may be
that the current version of the software does not have the problem.

Some of my disks were initially created under earlier versions of lvm
on a different system.  I think I have also had the snapshot freeze
problem on this system.


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lvm2 depends on:
ii  libc6                        2.7-16      GNU C Library: Shared libraries
ii  libdevmapper1.02.1           2:1.02.27-4 The Linux Kernel Device Mapper use
ii  libreadline5                 5.2-3       GNU readline and history libraries
ii  lsb-base                     3.2-20      Linux Standard Base 3.2 init scrip

Versions of packages lvm2 recommends:
ii  dmsetup                      2:1.02.27-4 The Linux Kernel Device Mapper use

lvm2 suggests no packages.

-- no debconf information





More information about the pkg-lvm-maintainers mailing list