Re: Failed, but "md: cannot remove active disk..."

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Mon, 14 May 2012 13:44:25 +0200 Michał Sawicz <michal@xxxxxxxxxx> wrote:

> Dnia 2012-05-14, pon o godzinie 21:36 +1000, NeilBrown pisze:
> > Is the array still functioning?
> > Are there any interesting messages appearing in the kernel logs?
> 
> Yes and no, the array is fine, working, nothing interesting in any logs
> I can see.
> 
> > What does
> >   grep . /sys/block/md126/md/dev*/*
> > show?
>
//snip//


Thanks. No hints there - all normal.

If you can write to the array, then md_check_recovery must be getting run,
and the array is not read-only. So...

Is there a 'sync' thread still running?  It would be called
    md126_resync

That would stop things from progressing.
If there is, what does
    cat /proc/$PID/stack
show for the relevant PID ??

What about
    cat /sys/block/md126/md/sync_action
??
If that were 'frozen', that might explain it.

    cat /sys/block/md126/md/reshape_position

shows "none" I suspect?

I cannot think of anything else that could be getting in the way.

NeilBrown

Attachment: signature.asc
Description: PGP signature


[ATA RAID]     [Linux SCSI Target Infrastructure]     [Managing RAID on Linux]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device-Mapper]     [Kernel]     [Linux Books]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Photos]     [Yosemite Photos]     [Yosemite News]     [AMD 64]     [Linux Networking]

Add to Google Powered by Linux