Hello to all in the list,
sorry for misconfiguration of my autoresponder to send out fo office mails
to mailinglists.
will not happen again.
-Ursprüngliche Nachricht-
Von: Aaron Hatfield [mailto:[EMAIL PROTECTED]]
Gesendet am: Mittwoch, 8. September 1999 20:17
An: Schackel, Fa.
Hello,
I have just joined this list, but have read through as many of the archives
as I could about booting from a raid1 /boot partition. From what I have read
someone has done it using "grub" (I dont know it), but not via lilo. If what
I discuss below has already been done/discussed or is just
Hello folks,
Due to too much coffee while diagnosing another problem... I found myself
unable to sleep. So I did some ide raid0 benchmarks for everyone to mull
over.
[Note that I did these benchmarks with hdparm and not bonnie, as I actually
had a readable raid5 filesystem on this disk set.
Date: Wed, 8 Sep 1999 18:11:46 +0900
From: Sang-yong Suh [EMAIL PROTECTED]
By the way, I need one more help. The /dev/md0 partition has a lot
of entries in its lost+found directory even after "rm -f". It has
9484 entries now. When I tried rm, it says "Operation not permited".
Yea, im always keen to see results, ive been trying to understand
performance
issues with ide raid0 for a while.
In the HOWTO i remember that says raid0 can give "near linear" performance
increases, a few weeks ago i played with a 4 way ide raid0, and i max'ed out
at
about the same figures you
Ingo Molnar wrote:
just a suggestion - if it's a faulty cable or a single faulty disk, then
you can find the problematic disk (or group of disks) by using less than 9
disks in the RAID0 array. I'd first split it into a 4 and 5-disk group.
This presumes the test doesnt take too long.
Thank
I wrote:
Ingo Molnar wrote:
just a suggestion - if it's a faulty cable or a single faulty disk, then
you can find the problematic disk (or group of disks) by using
less than 9
disks in the RAID0 array. I'd first split it into a 4 and 5-disk group.
This presumes the test doesn't take too
Hello all,
I am encountering reproducible read time errors while reading from my
existing RAID array with at least one disk running on a HPT-366 driven
channel. This manifests itself as random errors... e.g. if you read the
same thing five times, you will get five different answers. I first
Post your /etc/raidtab
You may have a spelling oops hidden in there, according to the error message :)
"Stoica, Dragos" wrote:
Hi!
I'm trying to create a RAID volume in linear mode from two 18Gb partitions
on different HDD's. I followed the instructions in Software RAID HOWTO and I
All,
Here's a reprise of this ancient message. But there's method
in my madness. We need to do just this and are hitting a wall.
We have stock RedHat 6.0 with the 18 disk patch by Lance
Robinson, and no other kernel, module or raidtools changes. We
tried removing disk fifteen (sdo, scsi 2 0
Over the weekend, I got RAID1 running on my RedHat 2.2.11 box. Following the
advice on this list, I fetched raidtools-19990824-0.90.tar, and the
raid0145-19990824-2.2.11 kernel patch. I applied the patch to a pristine
kernel tree, compiled, rebooted, and it started working.
I followed the
On Mon, 13 Sep 1999, Lawrence Dickson wrote:
1. unmount everything that's directly on the disk that isn't raid.
2. swapoff if you have swap on that disk
Didn't understand this. Our system is on hda and we can't
unmount it.
indeed. you can't do it on the disk with the root-device on
12 matches
Mail list logo
