Your message dated Wed, 13 Feb 2008 15:07:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Device nodes are not removed when devices are brought down
has caused the Debian Bug report #402511,
regarding Device nodes are not removed when devices are brought down
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 [EMAIL PROTECTED]
immediately.)
--
402511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402511
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: lvm-common
Version: 1.5.20
Severity: important
(Note that I personally think that this should be fixed before Etch as it
is a recent regression and likely to cause unneeded BRs during Etch, but
the errors are probably too harmless to warrant RC severity.)
Since very recently I'm seeing the following messages (transcribed,
possibly not completely literal) during the last stage of shutdown:
<snip>
Stopping remaining crypto disks
Shutting down LVM Volume Groups
/dev/dm-6: open failed, no such device or address
/dev/dm-7: open failed, no such device or address
Can't deactivate volume group "strider" with open LVs
Stopping early crypto disks
</snip>
I have one VG ("strider") with 6 LVs. Of those 6 LVs, two hold an
encrypted filesystem: home and swap.
The errors for /dev/dm-[67] appeared only recently and seem bogus to me.
The "Can't deactivate volume group" message has always been there and is
expected as I have root on an LV in VG "strider".
My dm devices are as follows:
/dev/dm-0: swap
/dev/dm-1: root
/dev/dm-2: usr
/dev/dm-3: var
/dev/dm-4: home
/dev/dm-5: srv
/dev/dm-6: home-crypt
/dev/dm-7: swap-crypt
So, it looks like the lvm init script is trying to access crypto dm
devices that I would guess have already been disabled/removed during
the "Stopping remaining crypto disks" phase.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages lvm-common depends on:
ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries
ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo
ii modutils 2.4.27.0-6 Linux module utilities
pgpDa1Y6ei9lJ.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Monday 11 February 2008, Jonas Meurer wrote:
> Could you try to reproduce the issue described in bug #406697 with
> latest debian/unstable? You said on irc, that you're not sure whether
> the described issue happens anymore.
Thanks for the reminder. I'd forgotten about that.
The following messages no longer appear when I shut down my laptop with
current testing:
/dev/dm-6: open failed, no such device or address
/dev/dm-7: open failed, no such device or address
Therefore closing both this report and the one it was cloned from.
As I don't know exactly _what_ fixed this, I'm not using versioned closures.
Cheers,
FJP
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
