On Mon, 14 Aug 2000, Jens Axboe wrote:
>> I found that increasing the read_latency to match write_latency fixes the
>> problems perfectly - thanks for the pointer!
>
>Ok good. Andrea, could we bump read latency in 2.2.17-pre?
Yes.
>> Increasing the read_latency and write_latency to 10,000,000 r
Check out the section on that in the Software-RAID HOWTO. You can get it
from http://www.LinuxDoc.org/HOWTO/Software-RAID-HOWTO-6.html#ss6.1 but a
mirror closer to you might be better.
Greg
> -Original Message-
> From: Martin Brown [mailto:[EMAIL PROTECTED]]
> Sent: Monday, Augu
Corin Hartland-Swann wrote:
>
> Hi Andre,
>
> The revised comparison between 2.2.15 and 2.4.0-test5 are as follows:
>
> ==> 2.2.15 <==
>
> Dir Size BlkSz Thr# Read (CPU%) Write (CPU%) Seeks (CPU%)
> - -- --- - -- --
> /mnt/ 256
judging by the traffic on this list, patched 2.2.14 is your best
bet. I have 2.2.12 which came with RH 6.1, and it works fine.
--
ai
http://sefiroth.org
On Mon, 14 Aug 2000, Ryan Daly wrote:
> Guys,
>
> I'm using 2.4.0-test5 right now 'cause I don't have the time to figure out how
> the n
> file. Should the /dev/mdx's which are equivalent to the / and /boot
> filesystems, respectively, be the first ones to be mounted?
Doesn't matter. The kernel mounts the root and the others are mounted
when fstab is read (root is already mounted at this point).
[EMAIL PROTECTED]
I lost 2 drives out of a 2 drive RAID5. How can I rebuild the super blocks
of the 2 dead drives to see if I can restore tire some data?
And.. if am able to mount the array and it shows up with the correct drive
space used, but some of the files are an incorrect file type.. what would
cause this
On Monday August 14, [EMAIL PROTECTED] wrote:
> Guys,
>
> I'm using 2.4.0-test5 right now 'cause I don't have the time to figure out how
> the new module directory structure works... (If anyone knows what to do, can
> you let me know?)
"make modules_install" should install the RAID modules into
hi ya ryan
usually i get the opposite problem
how to stop the system from autodetecting the
raid array sot hat it doesnt stop the booting...
so to turn it ondo the oopposite of what i do
to fix my "faulty raid" when it dies
- make sure you have /etc/raidtab
- make sure your kernel
Greetings,
I'm (somewhere) in the middle of upgrading from non-raid to RAID1.
I'm using RH6.2 on a dual PIII-450s w/ 2 Barracuda 20GB Seagates
(with minutely different geometries).
Looking at Section 4 of "the Boot + Root + Raid + Lilo : Software Raid HOWTO"
I've gotten up to 4.5 - "Test your n
Again may be missing something here...
How do you turn on autodetection in the kernel?
-rd
2 of my 4 raid drives failed.. what's the best way to repair the super block
to see if I can get one of them to work?
___
Martin Brown
Unix Systems and Network Administrator
Tantalus Communications Inc.
Suite 500 - 1122 Mainland Street
Vancouver, BC V6B 5L1
[EM
Guys,
I'm using 2.4.0-test5 right now 'cause I don't have the time to figure out how
the new module directory structure works... (If anyone knows what to do, can
you let me know?)
The 2.4 series has the new RAID code built in already, correct?
I'm using raidtools-19990824-0.90. Will I be OK w
On Mon, Aug 14 2000, Corin Hartland-Swann wrote:
> I have tried this out, and found that the default settings were:
> elevator ID=232 read_latency=128 write_latency=8192 max_bomb_segments=4
>
> Can anyone point me to any documentation on this elevator code? I was
> wondering what exactly the diff
Hi,
We had a strange thing running on 2.2.16 raid-1 soft
on ide.
8 days ago we saw the timeout on hdc. We could not raidhotadd /dev/hdc
and nothing worked on hdc. So we decided to change the hdc
(hd broken) We did it last friday and the reconstruction was easy.
Today we realized this:
the data on
Hi there,
I am CC:ing this to Andrea Arcangeli because he is credited at the top of
drivers/block/ll_rw_blk.c as writing the elevator code.
On Sun, 13 Aug 2000, Jens Axboe wrote:
> On Sun, Aug 13 2000, Corin Hartland-Swann wrote:
> > The fact remains that disk performance is much worse under 2
I took a stock 2.2.14 kernel, applied that raid patch (this time
successfully), built and booted the kernel. Since I had a /etc/raidtab.foo
i thought that raid wouldn't get autoconfigured but still I'm
seeing these messages in dmesg output for which you may have an
explanation:
md driver 0
On Sun, 13 Aug 2000, Edward Schernau wrote:
> Anyone used the DC690 under Linux? Its a PCI card, 2 IDE busses,
> no CDROM support, with 4 30pin SIMM slots. Supposedly does mirroring,
> all of which is transparent to the OS. It doesn't require any DOS
> drivers. Any pointers would be apprectiat
17 matches
Mail list logo
