On Feb 2, 2009, at 12:39 AM, martin f krafft wrote:
also sprach Will Glynn <w...@lerfjhax.com> [2009.01.21.0406 +0100]:
Package: mdadm
Version: 2.6.7.1-1
[...]
I believe this is fixed by a particular upstream commit, already
included in 2.6.8: 6e9eac4f089a44e9091967a3e6198aeae7e845a3
This commit went into 2.6.4 already. Are you sure you were using
2.6.7.1 at the time?
Yeah, I was wrong; it's not that commit. However, the host system and
rescue shell in question are definitely 2.6.7.1-1, and reassembling
with mdadm 2.6.8 compiled from source fixed the issue.
System availability wasn't critical in this case, so I allowed the
array to finish reshaping in the rescue shell, started by the 2.6.8
binary. On reboot, 2.6.7.1-1 was able to reassemble the no-longer-
reshaping array, and everything came up correctly.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
