From: NeilBrown <neilb@suse.com>
To: Wols Lists <antlists@youngman.org.uk>,
Theophanis Kontogiannis <tkonto@gmail.com>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Question on blocks periodic writes
Date: Fri, 11 Nov 2016 12:52:34 +1100 [thread overview]
Message-ID: <87a8d6lr4t.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <58249BD9.8000303@youngman.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
On Fri, Nov 11 2016, Wols Lists wrote:
> On 10/11/16 02:00, NeilBrown wrote:
>>> [ 8664.858104] xfsaild/md1(658): WRITE block 0 on md1 (8 sectors)
>> This is XFS doing something. md cannot possibly stop all IO while the
>> filesystem performs occasional IO. If these continue, you need to
>> discuss with xfs developers how to stop it. If the writes to individual
>> drives continue after there are no writes to 'md1', then it is worth
>> coming back here to ask.
>>
>>
> Would the new journal feature be any help?
Probably not, though until we know what is causing the writes, it is
hard to say.
>
> I haven't dug in enough to understand it properly, and it would increase
> the vulnerability of the system to a journal failure, but the feature
> itself seems almost perfect for batching writes and enabling the disks
> to spin down for extended periods.
You might be able to build functionality onto the journal which allows
the drives in the main array to stay idle for longer, but it doesn't try
to do that at present.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2016-11-11 1:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 17:20 Question on blocks periodic writes Theophanis Kontogiannis
2016-11-10 2:00 ` NeilBrown
2016-11-10 16:10 ` Wols Lists
2016-11-11 1:52 ` NeilBrown [this message]
2016-11-11 12:11 ` Theophanis Kontogiannis
2016-11-11 12:13 ` Theophanis Kontogiannis
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=87a8d6lr4t.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=tkonto@gmail.com \
/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).