Re: Reshape stuck immediately, backup file all nulls

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

 



On Sat, Jan 30, 2016 at 6:09 PM, Phil Turmel <philip@xxxxxxxxxx> wrote:
> Hi Björn,
>
> On 01/30/2016 07:21 AM, Björn Augustsson wrote:
>
>> The question is, what kind of state am in now?
>
> The kernel is waiting for mdmon (mdadm as a background task) to step
> through the stripes.  mdmon died and the kernel will wait forever.

OK. So I think the root cause here is that my invocation of mdadm was
unconfined,
because I was running it interactively. So it could create the backup file.
But the background version starts via systemd, and runs as mdadm_t, which
can't read that file (because it's in /boot). And poof.

I'll file a bug vs the fedora selinux policy for this, too.

>> And how should I recover?
>> Will just adding a policy to allow access to that file, and then
>> mdadm --grow --continue /dev/md127
>> fix it?
>
> Probably.  Others have fixed this by disabling selinux for the reshape.
>  Don't forget to specify --backup-file again on the command line.  (I
> don't use selinux myself, so I can't be more specific.)

Yeah, this seems to be working.
mdadm --grow --continue --backup-file=/boot/grow_md127.bak /dev/md127
is running, and the counters in /proc/mdstat started moving. It's going to be
a day or two for this to complete, but right now things are looking good.

Thanks for the help!

/August.

> In the future, consider not using a backup file at all -- mdadm
> generally leaves enough dead space on devices to avoid the need.
>
>> Is the broken backup file going to be a problem?
>
> Shouldn't be. Report back if it is.
>
> Phil



-- 
Wrong on most accounts.  const Foo *foo; and Foo const *foo; mean the same: foo
being a pointer to const Foo.  const Foo const *foo; would mean the same but is
illegal (double const).  You are confusing this with Foo * const foo; and const
Foo * const foo; respectively. -David Kastrup, comp.os.linux.development.system
--
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



[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux