Dear All
I've just had a disk (sdc) fail in my raid5 array (sdb sdc sdd),
and I noticed that it triggered a bug (?) in raid5.c, line 523:
kernel: md: bug in file raid5.c, line 523
Is it OK to ignore this ?
I'm running 2.4.5ac13.
Thanks!
Ian
--- excerpt from messages ---
Jun 14 07:10:42
OK...when I do mdTAB I currently get:
md5sum mdatopbm
Not too bad. Should work for most people.
As for migrating this...all old utils should have a wrapper for a while
(maybe quite a while - a year or so?) that points the users to the new
command.
e.g.
mkraid /dev/md0
Error: mkraid has been
raidctl is already used in the BSD camp.
RAIDCTL(8) NetBSD System Manager's Manual RAIDCTL(8)
NAME
raidctl - configuration utility for the RAIDframe disk driver
Neil Brown wrote:
Thankyou for all the suggestions for names for mdctl.
We have
raidctl
There appears to be a discrepancy between the true state of affairs on my
RAID partitions and what df reports;
[root /]# sfdisk -l /dev/hda
Disk /dev/hda: 38792 cylinders, 16 heads, 63 sectors/track
Units = cylinders of 516096 bytes, blocks of 1024 bytes, counting from 0
Device Boot
On Friday June 15, [EMAIL PROTECTED] wrote:
There appears to be a discrepancy between the true state of affairs on my
RAID partitions and what df reports;
[root /]# sfdisk -l /dev/hda
Disk /dev/hda: 38792 cylinders, 16 heads, 63 sectors/track
Units = cylinders of 516096 bytes, blocks
On Fri, 15 Jun 2001 13:25, Neil Brown wrote:
hda1 has 768095 1K blocks.
md/raid rounds down to a multiple of 64K, and then removes the last
64k for the raid super block, leaving
768000 1K blocks.
ext2fs uses some of this for metad, and reports the rest as the
available space.
The
