Hello,
On Tue, 2005-08-09 at 20:44 +0100, Martin Michlmayr wrote:
> Hi Adam (et al.),
>
> Sorry for not responding earlier but I've been travelling and quite
> busy and completely forgot about this issue. As I said, I don't know
> what the ideal situation is. The nice thing about the transition
Hi Adam (et al.),
Sorry for not responding earlier but I've been travelling and quite
busy and completely forgot about this issue. As I said, I don't know
what the ideal situation is. The nice thing about the transition
package is that it provides some kind of upgrade path: it depends on
the pac
Greetings,
First, sorry about the very negative tone of my message. I had meant to
start it with "First the good news: thanks for the transitional
raidtools2 package!" But with emotions running high and a rush to get
this out at the end of the day, I neglected this important part of the
report.
* Adam C Powell IV <[EMAIL PROTECTED]> [2005-06-19 20:02]:
> The transition from raidtools2 to mdadm breaks all installations with
> more than one RAID array
> That the transitional raidtools2 package entered sarge just days before
> the release (and that sarge had zero testing cycles, unlike pota
Hi,
We know that there was no testing cycle for Sarge (badly enough) but we
made a release note for this and you can find it here:
http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#s-mdadm
If we make a patch that does the transition from /etc/raidtab to
mdadm.conf, i'm
Package: raidtools2
Version: 1.00.4
Severity: grave
Justification: breaks reboot for sites with multiple RAID arrays
Tags: sarge
Greetings,
The transition from raidtools2 to mdadm breaks all installations with
more than one RAID array because /etc/raidtab is ignored during
autodetection. I disco
6 matches
Mail list logo
