Your message dated Wed, 20 Sep 2006 22:07:48 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line why is this bug still open?
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: cryptsetup
Version: 2:1.0.3-3
Severity: important
Please forgive me if this bug is not related to cryptsetup, I can
suspect LVM2 and mdadm as well.
Please reassign it if necessary.
I have a root, and several other filesystems lied upon LVM2 over
dm-crypt over software RAID-5. The root filesystem is being setup by
initrd created by yaird (0.0.12-15), other filesystems get up from
ordinary initscripts.
During init runlevel 6 sequence however, the root partition remains in
read-write mode and it gets corrupted every single reboot.
The lvm2 stop script refuses to bring PV, GV and LV's created on
cryptsetup mapping down, because the filesystem on root LV is still
mounted.
Because of active LVM, the cryptsetup refuses to stop a given mapping
and initscript says it is 'busy' (that's where I would suspect setting
it read-only).
After all, just before shutdown, kernel says about setting md devices
readonly. And of course my /dev/md1 with RAID5 is not lucky enough and
is reported 'busy' instead of setting read-only - here I suspect the
source of my data corruption.
The filesystem used by me is reiserfs 3.6. This problem is not related
to the filesystem however. First, the initscripts are remounting it
readonly succesfully. Second, I have three reiserfs filesystems on this
particular dm-crypt mapping and only the root filesystem gets corrupted.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages cryptsetup depends on:
pn dmsetup <none> (no description available)
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libdevmapper1.02 2:1.02.07-1 The Linux Kernel Device Mapper use
ii libgcrypt11 1.2.2-1 LGPL Crypto library - runtime libr
ii libgpg-error0 1.2-1 library for common error values an
ii libpopt0 1.10-2 lib for parsing cmdline parameters
ii libuuid1 1.39-1 universally unique id library
cryptsetup recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, September 20, 2006 17:05, Jonas Meurer said:
> do you still any objections against closing this bug?
Nope
> i think that it should be closed for exactly the reason you gave in your
> last posting.
I'm closing it now, I just wanted to keep it open for a while to see if
there were any objections...
--
David Härdeman
--- End Message ---
