|
|
|
Re: RAID1 over aoe devices freezes cp-procs on failure of one aoe device | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
Hallo Gabor,
Gabor Gombas <gombasg@xxxxxxxxx> schrieb:
> On Thu, Jun 05, 2008 at 04:25:02PM +0200, Lars Täuber wrote:
>
> > The lost aoe-device is correctly marked as faulty but the the raid is
> > not usable for a copying processes any more although the remaining
> > device should be enough for a RAID1. There was no change after
> > removing the faulty device from md9.
> >
> > Is it possible that one faulty aoe-device blocks the aoe-module anyhow
> > so that all other aoe devices aren't accessible anymore? Or is the
> > RAID subsystem responsible for this?
>
> It should be easy to test: when the RAID hangs, try to read directly
> from the remaining device ("dd if=/dev/etherd/e11.1 ..."). If that also
> hangs, then it is an AoE issue.
the easiest tests are the last that come to mind. :o)
There is another problem here:
The described problem is not reproducable. I'm not sure wether I made something wrong or the situation is not the same after the shutdown.
I'm checking this right now.
Thanks
Lars
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Home] [ATA RAID] [Linux SCSI Target Infrastructure] [Linux] [Managing RAID on Linux] [Linux IDE] [Linux SCSI] [Linux Hams] [Device-Mapper] [Kernel] [Linux Books] [Linux Admin] [Linux Net] [GFS] [RPM] [Photos] [Yosemite Photos] [Yosemite News] [AMD 64] [Linux Nework]
![]() |
![]() |