Chris Mauritz wrote:
> > the DPT card is passed over because it has been assigned the same
> > resources. Linux is recognizing the DPT card but skipping for the above
> > reason. Can I do an append in the lilo.conf file to force it?
> > Thanks,
>
> You should be able to disable the integrate
I am just interested in how I can force an irq and i/o in the lilo.conf
file. I did it for a network card.
Lorenz Glaza
Transamerica Life Companies
Special Studies/ALM
213-742-5049
[EMAIL PROTECTED]
http://lo-lands.ml.org
> -Original Message-
> From: (Chris Mauritz) [SMTP:[EMAIL PROTE
On Thu, 17 Dec 1998, Thilo Herrmann wrote:
> So this is the only significant issue in the 98-12-14/15 alpha release I
> encountered so far: hotadding a drive that previously failed without
> rebooting the machine.
It's an even less likely case: adding a drive that has a completely
invalid _bu
Ingo:
I did reboot the raid5 machine and tried raidhotadd again. Worked
without problem.
hde1 was rebuilt in the background and marked online in mdstat after
that.
So this is the only significant issue in the 98-12-14/15 alpha release I
encountered so far:
hotadding a drive that previously faile
> From [EMAIL PROTECTED] Thu Dec 17 15:15:04 1998
>
> > You should be able to disable the integrated SCSI controller from the
> > motherboard BIOS configuration utility (usually by hitting DEL at boot
> > time).
>
> I think that misses the point, I think the goal was to get both going
> in order
> You should be able to disable the integrated SCSI controller from the
> motherboard BIOS configuration utility (usually by hitting DEL at boot
> time).
I think that misses the point, I think the goal was to get both going
in order to spread an md-device across them for performance...
At least,
> From [EMAIL PROTECTED] Thu Dec 17 13:37:24 1998
>
> I know this may be more of a hardware question than a specific RAID
> question, but here goes. I just got a DPT RAID controller, but my
> motherboard has a built-in scsi controller. So I have two scsi
> controllers. My problem is that I hav
On Thu, 17 Dec 1998, Carlos Carvalho wrote:
> running! NICE! This is much better than the previous version. The only
> glitch is that the 4 raid5syncd threads didn't disappear after
> finishing reconstruction. Shouldn't they?
they should. I'll look into this.
-- mingo
Sending to the list as well to dispell rumors...
Laszlo Vecsey ([EMAIL PROTECTED]) wrote on 17 December 1998 11:52:
>On Thu, 17 Dec 1998, Carlos Carvalho wrote:
>
>> Now the bad news... The raid5 machine locked early this morning, after
>> about 24 hours running. I had to use sys-req b to reb
On Thu, 17 Dec 1998, Bart Schuller wrote:
> Just a very small nit: I decided to use my 2.1.131-ac11-raid kernel tree
> to make a kernel for a machine that doesn't need raid, but failed to
> link:
>
> fs/fs.o: In function `__bforget':
> /opt/src/linux.ojo/fs/buffer.c:1123: undefined reference to
On Thu, 17 Dec 1998, David Harris wrote:
> It seems that you are saying that there are two states of the resync speed:
> (1) full resync speed which only happens after a full second of IO silence,
> and (2) the guaranteed minimum bandwidth resync speed. Are there any shades
> of gray in between?
Hi,
MOLNAR Ingo wrote:
> the background resync writes to the disk continuously if you dont use the
> array. If you have finished using the array, it will not immediately start
> resyncing, but will delay for 1 second. (a reasonable timeout) The point
> is that 'small idle periods' are pretty comm
I know this may be more of a hardware question than a specific RAID
question, but here goes. I just got a DPT RAID controller, but my
motherboard has a built-in scsi controller. So I have two scsi
controllers. My problem is that I have a resource conflict between the
RAID card and the on-board
I've installed the latest raid versions with 2.1.131-ac11 in two
machines, one a raid5 with root-raid, another with raid1. The raid5
machine was upgraded from version 98-09-13, the raid1 one from the
pre-historic 0.36 (with 2.0.33).
Everything worked fine from the beginning. As expected, I had to
Thilo's fix for mkpv.c appears in a different form in
raid_io.c. I think the code would be more consistient
and portable if the following lines were removed from raid_io.c.
raid_io.c:21:#ifndef BLKGETSIZE
raid_io.c:22:#define BLKGETSIZE _IO(0x12, 96) /* Return device size. */
raid_io.c:23:#endif
Hello,
Just a very small nit: I decided to use my 2.1.131-ac11-raid kernel tree
to make a kernel for a machine that doesn't need raid, but failed to
link:
fs/fs.o: In function `__bforget':
/opt/src/linux.ojo/fs/buffer.c:1123: undefined reference to
`partition_name'
make[1]: *** [vmlinux] Error 1
> From: Tom Brown <[EMAIL PROTECTED]>
> Date: Wednesday, December 16, 1998 4:44 PM
>
>
> While I'm here... can anyone point me to a resource that describes what's
> happening when the BEGIN and START cylinders are not equal?
>
The Start cylinder is the actual cylinder number from the cylinder
hi,
i got the raidtab from the sample file (only change the
chunk size to 16)
the mdstat didn't change a bit since the box runned
(i compiled in the auto RAID detection)
On Wed, 16 Dec 1998, MOLNAR Ingo wrote:
>
> hi. Could you send me your:
>
>
On Wed, 16 Dec 1998 [EMAIL PROTECTED] wrote:
> > The resync uses all available unused I/O bandwidth. You cannot speed that
> > up, besides adding faster hardware :)
>
> It doesn't seem to... when the mke2fs is going and pounding the drives
> all 9 access lights are pegged, but the backgroun
On Thu, 17 Dec 1998, Louis Mandelstam wrote:
> On Wed, 16 Dec 1998, MOLNAR Ingo wrote:
>
> > (ok, i'll fix this. I dont use raidstop anymore because the kernel always
> > stops all RAID arrays before rebooting.)
>
> Jsut want to make sure I understand you:
>
> We should remove the raidstop co
On Wed, 16 Dec 1998, MOLNAR Ingo wrote:
> (ok, i'll fix this. I dont use raidstop anymore because the kernel always
> stops all RAID arrays before rebooting.)
Jsut want to make sure I understand you:
We should remove the raidstop commands from our reboot/halt scripts - it's
no longer needed? W
21 matches
Mail list logo
