Dear Alvin,
OnSun, 16 Jul 2000 22:44:54 -0700 (PDT)
[EMAIL PROTECTED](Alvin Oga) said:
hi "raiders"...
i recently changed my raid5 box that was running on debian-2.2
into a new atx case new linux-2.2.16...etc.e.tc...
-
- its in a 1U raid5 box... worlds
On Mon, 17 Jul 2000, Marc Haber wrote:
|mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
|haber@gwen[9/60]:~$ cat /proc/mdstat
|Personalities :
|read_ahead not set
|unused devices: none
|haber@gwen[10/61]:~$
You have not compiled in any raid personnalities into
On Mon, 17 Jul 2000 15:07:57 +0200 (MEST), Holger Kiehl
[EMAIL PROTECTED] wrote:
On Mon, 17 Jul 2000, Marc Haber wrote:
|mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
|haber@gwen[9/60]:~$ cat /proc/mdstat
|Personalities :
|read_ahead not set
|unused devices: none
When you fdisk'd hda, did it successfully re-read the partition table, or
did it fail with a device/resource busy message?
The last time I saw a device too small was because the kernel hadn't noticed
that the partition had been created.
reboot is the simplest cure, or call a sysctl to re-read
On Mon, 17 Jul 2000 16:44:45 +0100, "Jim Bowen" [EMAIL PROTECTED]
wrote:
When you fdisk'd hda, did it successfully re-read the partition table, or
did it fail with a device/resource busy message?
I don't remember any unusual error messages.
The last time I saw a device too small was because the
Hi all
I've just compiled my 2.2.16 kernel to support raid1 and raid5.
I'm trying to set up both type of raid on my system, one raid1 and one
raid5, but I get an strange error .. :?
I'm using the raidtools package supplied with redhat 6.2 (I've compiled it
myself)
Here's a scerpt of what
Hello,
I created a raid linear this weekend merging two IDE disks (45g , 10g) on
a 2.2.16 kernel with the corresponding patches from
http://people.redhat.com/mingo/raid-patches/.
Today I moved the raid to another computer (home to work). I compiled a
similar kernel and applied the same
Hi
By aplying the patch I got on mingo's site, I can now mkraid and format and
so ... but now when mounting the raid5 drive, I get lot of messages like:
Jul 17 19:22:38 linux3 kernel: set_blocksize: b_count 1, dev md(9,0), block 134138,
from c013d6c2
Jul 17 19:22:38 linux3 kernel:
According to the RAID HOWTO
(www.linuxdoc.org/HOWTO/Root-RAID-HOWTO-2.html) you are supposed to
have the following packages:
This document is obsolete. See the Sequel at:
ftp://ftp.bizsystems.net/pub/raid/Boot+Root+Raid+LILO.html
On Saturday July 15, [EMAIL PROTECTED] wrote:
Folks,
kernel 2.2.13ac1, patched with ide.2.2.13.1999.patch and
raid0145-19990824-2.2.11. I know this is no longer "state of the art", but it
was pretty solid in its day. Recently, we've had 2 events which took our the
entire raid5
Linus et-al,
Russell Coker reported to linux-kernel that raid1 would lock up for
him when running bonnie++ - thanks Russell.
I managed to reproduce this and, at least for me, it is caused by a
deadlock when kflushd tries to write out data via raid1, raid1 tries
to allocate memory, which
[Marc Haber]
I am trying to build a RAID 1 with two disks on a new system. Linux is
Debian potato, kernel 2.2.16 patched with raid-2.2.16-A0, raidtools
built from raidtools-dangerous-0.90.2116.tar.gz.
So far so good.
| Device BootStart EndBlocks Id System
|/dev/hda7
On Mon, 17 Jul 2000 08:53:07 -0400, James Manning [EMAIL PROTECTED]
wrote:
So far so good.
Looks fine
Also good.
Being a non-primary partition shouldn't be a problem
No, that isn't a problem. I have two RAID5 arrays running with
non-primary partitions included (since I never use primary
13 matches
Mail list logo
