Your message dated Sun, 9 Jun 2013 14:11:27 +0300
with message-id <20130609111127.GA3775@sid.nuvreauspam>
and subject line Re: Bug#711740: device-mapper: Udev interaction fails: Missing
symlinks
has caused the Debian Bug report #711740,
regarding device-mapper: Udev interaction fails: Missing symlinks
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
711740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: device-mapper
Version: 1.02.77-2
Severity: serious
Justification: Policy 10.5
After upgrade, some events making udev create symlinks are not generated. This
leads into missing symlink files beneath:
/dev/disk/by-uuid
/dev/disk/by-id
Missing Symlinks include:
- LVM FIles: /dev/disk/by-id/dm-uuid-LVM-
GYN4GdZKa5TvWdCOOkuthLtWvSvmcrqUb0rzgJDDCTAHvMrYZw4yARd0ktzO8iyq (for example)
- Device Symlinks: /dev/disk/by-uuid/e43025c6-432d-4e42-9a89-8d07c2777b4f
Making the system unbootable in the worst-case scenario.
On my system, relevant mounts were only accessed via cryptsetup and autofs,
thus causing some filesystems become inaccessible.
The problem seems to relate to device mapper update from 1.02.77-1 to
1.02.77-2.
However, in the same run, also lvm is replaced from 2.02.98-1 to 2.02.98-2.
Regards,
Yusuf
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'testing'), (730, 'experimental'), (700,
'stable'), (500, 'testing-proposed-updates'), (500, 'proposed-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 3.9-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Du, 09 iun 13, 10:02:04, Yusuf Iskenderoglu wrote:
> Package: device-mapper
> Version: 1.02.77-2
> Severity: serious
> Justification: Policy 10.5
...
> The problem seems to relate to device mapper update from 1.02.77-1 to
> 1.02.77-2.
> However, in the same run, also lvm is replaced from 2.02.98-1 to 2.02.98-2.
Dear Yusuf,
There is no device-mapper package in Debian, only dmraid, which has
other versions than what you seem to be using:
$ rmadison dmraid
dmraid | 1.0.0.rc16-4.1 | squeeze | source, amd64, armel, i386, ia64, mips,
mipsel, powerpc, s390, sparc
dmraid | 1.0.0.rc16-4.2 | wheezy | source, amd64, armel, armhf, i386, ia64,
mips, mipsel, powerpc, s390, s390x, sparc
dmraid | 1.0.0.rc16-4.2 | jessie | source, amd64, armel, armhf, i386, ia64,
mips, mipsel, powerpc, s390, s390x, sparc
dmraid | 1.0.0.rc16-4.2 | sid | source, amd64, armel, armhf, i386, ia64,
mips, mipsel, powerpc, s390, s390x, sparc
Also Debian only has lvm2 (note the 2 in the package name) version
2.02.98-1
$ rmadison lvm2
lvm2 | 2.02.66-5 | squeeze | source, amd64, armel, i386, ia64, mips, mipsel,
powerpc, s390, sparc
lvm2 | 2.02.95-7 | wheezy | source, amd64, armel, armhf, i386, ia64, mips,
mipsel, powerpc, s390, s390x, sparc
lvm2 | 2.02.95-7 | jessie | source, amd64, armel, armhf, i386, ia64, mips,
mipsel, powerpc, s390, s390x, sparc
lvm2 | 2.02.98-1 | sid | source, amd64, armel, armhf, i386, ia64, mips,
mipsel, powerpc, s390, s390x, sparc
My guess is you have some non-Debian repositories in your sources.list.
Please try to reproduce this bug with Debian packages and reopen this
bug and assign to the correct package.
Kind regards,
Andrei
--
Looking after bugs filled against unknown packages
signature.asc
Description: Digital signature
--- End Message ---
