From: Sebastian Riemer <sebastian.riemer@profitbricks.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "Alexander Kühn" <alexander.kuehn@nagilum.de>,
linux-raid@vger.kernel.org
Subject: Re: sync action not working/ignored
Date: Mon, 24 Sep 2012 09:48:55 +0200 [thread overview]
Message-ID: <50601067.4020003@profitbricks.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1209230757420.13902@uplift.swm.pp.se>
On 23.09.2012 07:59, Mikael Abrahamsson wrote:
> On Sun, 23 Sep 2012, Alexander Kühn wrote:
>
>> root@nas:~# echo /sys/block/md*/md/sync_action
>> /sys/block/md1/md/sync_action
>> root@nas:~# cat /proc/mdstat
>> Personalities : [raid6] [raid5] [raid4]
>> md1 : active (auto-read-only) raid5 sdb[5] sdg[9] sdd[7] sdf[6]
>> sde[8] sdc[2] sda[1]
>> 11719408128 blocks super 1.2 level 5, 64k chunk, algorithm 2
>> [7/7] [UUUUUUU]
>> bitmap: 0/15 pages [0KB], 65536KB chunk
>
> I'd imagine that it's the "(auto-read-only)" that is the culprit here.
> If you can do something that writes to the array (mount of a
> filesystem for instance) and then reproduce the problem?
>
Indeed, use "mdadm -w /dev/md1" to set it writeable. This immediately
starts pending sync actions. In the kernel code in "drivers/md/md.c"
there is the function "action_store" which handles your "sync_action"
sysfs file writes. I just sets some bits in "mddev->recovery".
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-09-24 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 22:27 sync action not working/ignored Alexander Kühn
2012-09-23 5:59 ` Mikael Abrahamsson
2012-09-24 7:48 ` Sebastian Riemer [this message]
2012-09-26 1:47 ` NeilBrown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50601067.4020003@profitbricks.com \
--to=sebastian.riemer@profitbricks.com \
--cc=alexander.kuehn@nagilum.de \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).