Package: lvm2 Version: 2.02.39-7 Followup-For: Bug #466138 I think this is the same kind of issue as in the previous report, though I'm not sure.
>From Jan 5th on a nightly cron job that creates snapshots produces messages like this for every lvcreate: <quote> + lvcreate -L10G -s -n _home /dev/daisy/home File descriptor 3 left open File descriptor 41 left open File descriptor 42 left open File descriptor 43 left open Logical volume "_home" created </quote> The same file descriptors are listed for each group. I do not see such messages when I do other commands such as lvs. The only installs in the previous day were of a locally built, backported (from sid--I'm on lenny) samba. These did require upgrading libpam0g, libpamruntime, libpam-modules to sid, and installing libdb4.7 from sid. I also upgraded man-db and doc-base within lenny. I think the previous discussion implies a) my lvcreate's are still working OK and b) I may have a security problem with some other program. The new installs would be the obvious suspects, particularly pam. I'm looking for confirmation of a) and advice on how to handle b). Thanks. P.S. It might also be relevant that I get a parse error from lvm every time the system starts, at something like byte 3200. I seem to have all my volumes, and I don't know where the data is that is being read. -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (990, 'stable'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-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-18 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.1 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 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
