"Schackel, Fa. Integrata, ZRZ DA" wrote:
>
> Hi,
>
> after I applied the raid0145-19990421-2.2.6 patch to my
> new downloaded kernel(2.2.10 from kernel.org) I wanted
> to raise the max devices of a md in md.h.
> But md.h was 0 bytes.
> I don't think it's ok ?!?
>
include/linux/md.h has moved to
Hi, you applied the wrong patch
raid0145-19990421-2.2.6 means the following
raid-date of release - kernel version where it can applied
to patch 2.2.10 you need the patch raid0145-19990724-2.2.10
When your kernel-mirror doesn't have it in his
(ftp://ftp.de.kernel.org/pub/linux/daemons/raid/alp
Hi,
after I applied the raid0145-19990421-2.2.6 patch to my
new downloaded kernel(2.2.10 from kernel.org) I wanted
to raise the max devices of a md in md.h.
But md.h was 0 bytes.
I don't think it's ok ?!?
I also don't want to touch my existing Kernel 2.2.5 cause
it's running. ;-) You know...
> I think _both_ lines are necessary to release the inode.
> ...
> + clear_inode(rdev->inode);
It works for me! However, I think there's another bug hiding. When I erase
the contents of one partition (to learn at last how to recover from a RAID1
failure :) ), 'active inodes' show up again
Rich Bollinger
- Original Message -
From: Egon Eckert <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 22, 1999 4:04 PM
Subject: raidstop; raidstart fails
> On 2.0.37+raid990713 (recent), when I stop my raid1 device (using
raidstop),
> it refuses to &#
On 2.0.37+raid990713 (recent), when I stop my raid1 device (using raidstop),
it refuses to 'raidstart' (I have to reboot to get /dev/md0 active again).
Is it a bug or a feature? :)
Here it is:
--
ego2:~# cat /proc/mdstat
Personalities : [raid1] [raid5]
read_ahead 1024 sectors
md0 : activ
