Your message dated Mon, 14 Apr 2008 23:10:16 -0400
with message-id <[EMAIL PROTECTED]>
and subject line raidtools2 has been removed from Debian, closing #181514
has caused the Debian Bug report #181514,
regarding raidtools2: omiting "nr-spare-disks 0" in a raid1 config results in
non redundand raid1
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.)
--
181514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=181514
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: raidtools2
Version: 1.00.3-1
Severity: normal
Using the following in /etc/raidtab one can create a raid with mkraid,
format and use it:
raiddev /dev/md/0
raid-level 1
nr-raid-disks 2
chunk-size 4
persistent-superblock 1
device /dev/rd/0
raid-disk 0
device /dev/rd/1
raid-disk 1
After a "raidstop /dev/md/0; dd if=/dev/zero of=/dev/rd/1;",
i.e. simulated disk failure, the raid fails to start.
Adding "nr-spare-disks 0" and one can creat a raid1 that actually
recovers (into degraded mode) from such a disk failure.
MfG
Goswin
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux dual 2.4.19 #11 SMP Thu Jan 9 00:18:31 CET 2003 i686
Locale: LANG=C, LC_CTYPE=de_DE
Versions of packages raidtools2 depends on:
ii debconf 1.2.23 Debian configuration management sy
ii libc6 2.3.1-11 GNU C Library: Shared libraries an
ii makedev 2.3.1-62 Creates device files in /dev.
-- debconf information:
* raidtools2/init:
raidtools2/oldraid:
raidtools2/nosupport:
--- End Message ---
--- Begin Message ---
Version: 1.00.3-17+rm
The raidtools2 package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/298968 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
Barry deFreese
--- End Message ---
