Bug#522820: marked as done (linux-2.6: device mismatches found: 5632 for swap.)
Your message dated Mon, 3 Jun 2013 19:03:10 +0200
with message-id <20130603170310.GC5319@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #522820,
regarding linux-2.6: device mismatches found: 5632 for swap.
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 owner@bugs.debian.org
immediately.)
--
522820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522820
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: linux-2.6: device mismatches found: 5632 for swap.
- From: Kurt Roeckx <kurt@roeckx.be>
- Date: Mon, 6 Apr 2009 20:40:54 +0200
- Message-id: <20090406184054.GA16750@roeckx.be>
Source: linux-2.6
Version: 2.6.26-13
Hi,
I have seen this error on multiple systems, and always for the
device with swap on it:
mdadm[2860]: RebuildFinished event detected on md device /dev/md2, component device mismatches found: 5632
This error is logged after the monthly "check" that is being run for all
the md devices.
Running the check manually also seems to have the same effect.
And the mismatch_cnt does contain that value:
# cat /sys/block/md2/md/mismatch_cnt
5632
Kurt
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.
We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:
reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks
Cheers,
Moritz
--- End Message ---
Reply to: