Your message dated Mon, 20 Jul 2009 15:22:45 +0000
with message-id <[email protected]>
and subject line Bug#537460: fixed in mdadm 3.0-1
has caused the Debian Bug report #537460,
regarding mdadm: Adjusting logcheck rules for CONFIG_PRINTK_TIME
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.)
--
537460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537460
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mdadm
Version: 2.6.9-3
Severity: normal
Tags: patch
The logcheck rules will not match for a kernel with CONFIG_PRINTK_TIME.
Here's a patch to fix that.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26.8 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mdadm depends on:
ii debconf 1.5.27 Debian configuration management sy
ii libc6 2.9-20 GNU C Library: Shared libraries
ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip
ii makedev 2.3.1-88 creates device files in /dev
ii udev 0.141-1 /dev/ and hotplug management daemo
Versions of packages mdadm recommends:
ii module-init-tools 3.9-2 tools for managing Linux kernel mo
ii postfix [mail-transport-agen 2.6.2~rc1-1 High-performance mail transport ag
mdadm suggests no packages.
-- debconf information excluded
>From ca058245a08a5828d3be5e44a55828bccbdd7ddd Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Fr=C3=A9d=C3=A9ric=20Bri=C3=A8re?= <[email protected]>
Date: Thu, 16 Jul 2009 22:56:25 -0400
Subject: [PATCH] Adjusting logcheck rules for CONFIG_PRINTK_TIME
---
debian/mdadm.logcheck.ignore.server | 38 +++++++++++++++++-----------------
debian/mdadm.logcheck.violations | 6 ++--
2 files changed, 22 insertions(+), 22 deletions(-)
diff --git a/debian/mdadm.logcheck.ignore.server
b/debian/mdadm.logcheck.ignore.server
index 84a1f9b..cebc025 100644
--- a/debian/mdadm.logcheck.ignore.server
+++ b/debian/mdadm.logcheck.ignore.server
@@ -1,22 +1,22 @@
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: md driver [.[:digit:]]+
MAX_MD_DEVS=[[:digit:]]+, MD_SB_DISKS=[[:digit:]]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: bitmap version [.[:digit:]]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: md[[:digit:]]+ stopped\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: md[[:digit:]]+ still in use\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: cannot remove active disk
[[:alnum:]]+ from md[[:digit:]]+ \.\.\. ?$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: raid([01456]|456|10)
personality registered for level ([01456]|10)$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md:
(data-check|requested-resync|resync|reshape|recovery) of RAID array
md[[:digit:]]+$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: resuming
(data-check|requested-resync|resync|reshape|recovery) of md[[:digit:]]+ from
checkpoint\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: md[[:digit:]]+:
(data-check|requested-resync|resync|reshape|recovery) done\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: minimum _guaranteed_ ?speed:
[[:digit:]]+ KB/sec/disk\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: using maximum available idle IO
bandwidth \(but not more than [[:digit:]]+ KB/sec\) for
(data-check|requested-resync|resync|reshape|recovery)\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: delaying
(data-check|requested-resync|resync|reshape|recovery) of md[[:digit:]]+ until
md[[:digit:]]+ has finished \(they share one or more physical units\)$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: using [[:digit:]]+k window,
over a total of [[:digit:]]+ blocks\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: (un)?bind<[^>]+>$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: export_rdev\([^)]+\)$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: raid[[:digit:]]+: raid set
[[:alnum:]]+ active with [[:digit:]]+ out of [[:digit:]]+ mirrors$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: RAID([01456]|10) conf printout:$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:[[:space:]]+---(
[wrf]d:[[:digit:]]+){2,3}$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:[[:space:]]+disk [[:digit:]]+,(
wo:[[:digit:]]+,)? o:[[:digit:]]+, dev:[[:alnum:]]+$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: md driver [.[:digit:]]+ MAX_MD_DEVS=[[:digit:]]+, MD_SB_DISKS=[[:digit:]]+$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: bitmap version [.[:digit:]]+$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: md[[:digit:]]+ stopped\.$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: md[[:digit:]]+ still in use\.$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: cannot remove active disk [[:alnum:]]+ from md[[:digit:]]+ \.\.\. ?$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: raid([01456]|456|10) personality registered for level ([01456]|10)$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: (data-check|requested-resync|resync|reshape|recovery) of RAID array
md[[:digit:]]+$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: resuming (data-check|requested-resync|resync|reshape|recovery) of
md[[:digit:]]+ from checkpoint\.$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: md[[:digit:]]+: (data-check|requested-resync|resync|reshape|recovery)
done\.$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: minimum _guaranteed_ ?speed: [[:digit:]]+ KB/sec/disk\.$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: using maximum available idle IO bandwidth \(but not more than [[:digit:]]+
KB/sec\) for (data-check|requested-resync|resync|reshape|recovery)\.$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: delaying (data-check|requested-resync|resync|reshape|recovery) of
md[[:digit:]]+ until md[[:digit:]]+ has finished \(they share one or more
physical units\)$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: using [[:digit:]]+k window, over a total of [[:digit:]]+ blocks\.$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: (un)?bind<[^>]+>$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: export_rdev\([^)]+\)$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
raid[[:digit:]]+: raid set [[:alnum:]]+ active with [[:digit:]]+ out of
[[:digit:]]+ mirrors$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
RAID([01456]|10) conf printout:$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[
*[[:digit:]]+\.[[:digit:]]+\])?[[:space:]]+---( [wrf]d:[[:digit:]]+){2,3}$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[
*[[:digit:]]+\.[[:digit:]]+\])?[[:space:]]+disk [[:digit:]]+,(
wo:[[:digit:]]+,)? o:[[:digit:]]+, dev:[[:alnum:]]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mdadm(\[[[:digit:]]+\])?:
Rebuild((Start|Finish)ed|[2468]0) event detected on md device
/dev/[-_./[:alnum:]]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mdadm(\[[[:digit:]]+\])?: SpareActive event
detected on md device /dev/[-_./[:alnum:]]+, component device
/dev/[-_./[:alnum:]]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mdadm(\[[[:digit:]]+\])?:
(New|Degraded)Array event detected on md device /dev/[-_./[:alnum:]]+$
diff --git a/debian/mdadm.logcheck.violations b/debian/mdadm.logcheck.violations
index 294c384..ea8cce7 100644
--- a/debian/mdadm.logcheck.violations
+++ b/debian/mdadm.logcheck.violations
@@ -1,3 +1,3 @@
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: kicking non-fresh [[:alnum:]]+
from array!$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: raid[[:digit:]]+: Disk failure on
[[:alnum:]]+, disabling device\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:[[:space:]]+Operation continuing on
[[:digit:]]+ devices?$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
md: kicking non-fresh [[:alnum:]]+ from array!$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?
raid[[:digit:]]+: Disk failure on [[:alnum:]]+, disabling device\.$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[
*[[:digit:]]+\.[[:digit:]]+\])?[[:space:]]+Operation continuing on [[:digit:]]+
devices?$
--
1.6.3.3
--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 3.0-1
We believe that the bug you reported is fixed in the latest version of
mdadm, which is due to be installed in the Debian FTP archive:
mdadm-udeb_3.0-1_amd64.udeb
to pool/main/m/mdadm/mdadm-udeb_3.0-1_amd64.udeb
mdadm_3.0-1.diff.gz
to pool/main/m/mdadm/mdadm_3.0-1.diff.gz
mdadm_3.0-1.dsc
to pool/main/m/mdadm/mdadm_3.0-1.dsc
mdadm_3.0-1_amd64.deb
to pool/main/m/mdadm/mdadm_3.0-1_amd64.deb
mdadm_3.0.orig.tar.gz
to pool/main/m/mdadm/mdadm_3.0.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
martin f. krafft <[email protected]> (supplier of updated mdadm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Format: 1.8
Date: Mon, 20 Jul 2009 16:22:54 CEST
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: amd64 source
Version: 3.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers <[email protected]>
Changed-By: martin f. krafft <[email protected]>
Description:
mdadm - tool to administer Linux MD arrays (software RAID)
mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 534663 537460
Changes:
mdadm (3.0-1) unstable; urgency=low
.
* New stable upstream release.
* Add information about udev and device links in /dev to bugscript output.
* Add pointer to FAQ and in particular rootdelay to the bug script
pre-subject file, which is displayed by tools like reportbug and thus
hopefully reduces the numbers of duplicated bugs.
* Patch from Frédéric Brière to make logcheck rules printk_time aware
(closes: #537460).
* Updated German translation due to typos and old spelling rules; thanks to
Helge Kreutzmann for the patch (closes: #534663).
* Bumped Standard-Version to 3.8.2; no changes necessary.
Checksums-Sha256:
aabf6bd4c5302fa651178d2a186777a31d49f27be94039bc1b58a017f5ae4d67 128258
mdadm-udeb_3.0-1_amd64.udeb
f7cc242fd9a1075538db35925e41a944724e3326e6a52ead497821298271c73a 328449
mdadm_3.0.orig.tar.gz
286ac0244f5c9f81f7c503a60ce0927873149429ce4774daf37cab9b98186ba3 1220
mdadm_3.0-1.dsc
4b882d5a5fe9785de391e2bf766c828678572ecdd8ccd4f8cdb06241f79f9ef0 139584
mdadm_3.0-1.diff.gz
4856e5ab36bda2f40d2e28405cff6f2575465900d94b8db9886a5638b47650eb 430896
mdadm_3.0-1_amd64.deb
Checksums-Sha1:
c628efe6c80cd78fc6d4a8f7649cb2bf157e01cf 128258 mdadm-udeb_3.0-1_amd64.udeb
79cd0c2f5cab99c4382f38e1c825690a01897db7 328449 mdadm_3.0.orig.tar.gz
5f51c3f71980529297c1b5bcc82878eb50ce980f 1220 mdadm_3.0-1.dsc
db92850cc16c5d6c7f12b8a4d0b70a5e5355f9ce 139584 mdadm_3.0-1.diff.gz
80d06659871b193fa86ce923a178aa43d4945551 430896 mdadm_3.0-1_amd64.deb
Files:
09a375a2e9d1ab7a75f9ef77171be644 128258 debian-installer optional
mdadm-udeb_3.0-1_amd64.udeb
1eb89885b2b881562fc79ed2f5e1a056 328449 admin optional mdadm_3.0.orig.tar.gz
f663b0f9400739d755eee16fa3a907b6 1220 admin optional mdadm_3.0-1.dsc
7e4ec228363bd99c0d7036dd0327deff 139584 admin optional mdadm_3.0-1.diff.gz
f84a91b3611d2da87a7824e1ce6680b2 430896 admin optional mdadm_3.0-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEAREDAAYFAkpkfeEACgkQIgvIgzMMSnXSRwCg6MdUYydZ+3dNH6NnU2TXLQzW
1ZAAmwS4FGzbKNpN9aknrDha2rjc4a3h
=9HgR
-----END PGP SIGNATURE-----
--- End Message ---
