Hi,
I would like to know if there are any known conflicts between current
RAID and NFS patches for Linux-2.2.17. I am using raid-2.2.17-A0,
linux-2.2.17-nfsv3-0.23.1 and dhiggen-over-0.23.1 patches.
The system usually works fine, but every 1-2 weeks the kernel seems to run
into problems. There
On Mon, 6 Nov 2000, Erik Heinz wrote:
Hi,
I would like to know if there are any known conflicts between current
RAID and NFS patches for Linux-2.2.17. I am using raid-2.2.17-A0,
linux-2.2.17-nfsv3-0.23.1 and dhiggen-over-0.23.1 patches.
The system usually works fine, but every 1-2
Dan,
On Sat, 4 Nov 2000, Dan Browning wrote:
'/' mounted on RAID-5
IIRC, lilo cannot deal with RAID-5 partitions at boot time - only RAID-1
(and maybe RAID-0?)
* When booting with newly created '/dev/md0' as '/', it is reported
corrupt and needs a manual fsck
* The manual fsck
On Tue, 7 Nov 2000, Shaggy Im-erbtham wrote:
My box is Slackware 7.0 (kernel 2.2.13) which had raidtools-0.41 installed.
My immediate problem is that the tutorials I read (as well as the one
included with the package) uses "mdrun" as part of the installation
process of raid. Well, I don't
Thank you for your reply, Corin Hartland-Swann. I've gotten my / up
and running on RAID-5. Now I have another problem. It is described
in the following bugreport that I posted to linux-kernel. The system
is running RAID, but I don't think the problem is RAID related (more
of IDE related).
As
Linus,
The following patch addresses a small number of bugs in raid1.c in
2.4.0-test10.
1/ A number of routines that are called from interrupt context used
spin_lock_irq / spin_unlock_irq
instead of the more appropriate
spin_lock_irqsave( ,flags) / spin_unlock_irqrestore(
On Mon, 6 Nov 2000, Jeff Garzik wrote:
Neil Brown wrote:
It looks like an interupt is happening while another interrupt is
happening, which should be impossible... but it isn't.
If multiple interrupts are hitting a single code path (like IDE irqs 14
-and- 15), you definitely have to
Neil Brown wrote:
It looks like an interupt is happening while another interrupt is
happening, which should be impossible... but it isn't.
If multiple interrupts are hitting a single code path (like IDE irqs 14
-and- 15), you definitely have to think about that. The reentrancy
guarantee only
My box is Slackware 7.0 (kernel 2.2.13) which had raidtools-0.41 installed.
My immediate problem is that the tutorials I read (as well as the one
included with the package) uses "mdrun" as part of the installation
process of raid. Well, I don't have it.
The installation left me with
