On Tuesday November 15, [EMAIL PROTECTED] wrote:
> > mdadm --add /dev/md0 /dev/sda2..
> yes , i am using raidstart for this. it should be the same.
No, it shouldn't.
raidstart is broken by design and cannot work reliable. It is one of
the main reasons that I wrote mdadm.
raidstart trusts the de
> mdadm --add /dev/md0 /dev/sda2..
yes , i am using raidstart for this. it should be the same.
I am handling a big cluster with supermicro machines,each machine has its
own 4 sata disks.I am using 2.6.6 kernel.
Did you ever pulled out a disk from raid5 while the machine was running ?
Just want to
NeilBrown <[EMAIL PROTECTED]> wrote:
>
>
> Despite the fact that md threads don't need to be signalled, and won't
> respond to signals anyway, we need to have an 'interruptible' wait,
> else they stay in 'D' state and add to the load average.
>
> ...
> + if (signal_pending(current))
>
Following are two patches for md in 2.6.14-mm2 that are suitable to go
into the 2.6.15-rc series.
The first adds a date to the deprecation of START_ARRAY ioctl.
The second fixes a recently introduced problem that causes md threads
to permanently add to the load average (other than that, every wor
Despite the fact that md threads don't need to be signalled, and won't
respond to signals anyway, we need to have an 'interruptible' wait,
else they stay in 'D' state and add to the load average.
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./drivers/md/md.c | 17
This was marked deprecated "after 2.6" back in the 2.5 days.
But now it seems there isn't going to be any "after 2.6", and
we deprecate by date now. So set a date.
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./Documentation/feature-removal-schedule.txt |9 +
On Mon, Nov 14, 2005 at 09:27:25PM +0200, Raz Ben-Jehuda(caro) wrote:
> I have made the following test with my raid5:
> 1. created raid5 with 4 sata disks.
> 2. waited untill raid was fully initialized.
> 3. pulled a disk from the panel.
> 4. shut the system.
> 5. put back the disk.
> 6. turn on th
I have made the following test with my raid5:
1. created raid5 with 4 sata disks.
2. waited untill raid was fully initialized.
3. pulled a disk from the panel.
4. shut the system.
5. put back the disk.
6. turn on the system.
The raid failed failed to recver. i got message from the md layer
saying
Carlos Carvalho wrote:
Shane Bishop ([EMAIL PROTECTED]) wrote on 14 November 2005 11:20:
>I had an mdadm device running fine, and had created my own scripts for
>shutting it down and such. I upgraded my distro, and all of a sudden it
>decided to start initializing md devices on it's own, whic
Shane Bishop ([EMAIL PROTECTED]) wrote on 14 November 2005 11:20:
>I had an mdadm device running fine, and had created my own scripts for
>shutting it down and such. I upgraded my distro, and all of a sudden it
>decided to start initializing md devices on it's own, which include one
>that I
10 matches
Mail list logo
