linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: "Jure Erznožnik" <jure.erznoznik@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Fwd: (user) Help needed: mdadm seems to constantly touch my disks
Date: Tue, 20 Dec 2016 10:39:26 +1100	[thread overview]
Message-ID: <87inqftro1.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAJ=9zidt_25tCF8QBy0To9oY+QNVD1ufF+CQ-pSjD97zVaLoGg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

On Mon, Dec 19 2016, Jure Erznožnik wrote:

> I have made two blktraces at the same time: one for md0 and one for a
> member of the array. I hope they will show something sensible.
>
> I dropped them here:
> http://expirebox.com/download/ee081fa4f85ffbd0bfad68e4ee257e11.html
>
> The file will be available for 48 hours or so they say.

Thanks.
The blktrace_md0.txt file shows several writes that originate from
   iscsi_trx

so it looks like 'md0' (or some other device that is built on it) is
being exported as an iscsi target.  Is that correct?

There are also some large (1024 sector) writes being generated about
once per second.  That is very clearly something being written to md0,
not something that md0 is doing itself.
They are generated by a kworker.  It might be iscsi related, but it
might be something else.

Try disabling the iscsi export and if the strange traffic still appears,
collect another blktrace (maybe for a bit longer - 30 seconds?).
Also please report output of
  ls -l /sys/block/md0/holders/
  fuser /dev/md0

when the problem is occurring.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2016-12-19 23:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13  8:13 (user) Help needed: mdadm seems to constantly touch my disks Jure Erznožnik
2016-12-14  1:15 ` NeilBrown
     [not found]   ` <CAJ=9zieRuTNiEGuB_RouqbdLGoxNkn09yiogR6rND84LtMdbxA@mail.gmail.com>
2016-12-15  7:01     ` Fwd: " Jure Erznožnik
2016-12-18 19:40       ` Jure Erznožnik
2016-12-18 21:30         ` Theophanis Kontogiannis
2016-12-18 22:21       ` Fwd: " NeilBrown
     [not found]         ` <CAJ=9zidNV4sPj7KC7_mJEo8+=-YTKyWD5RiLsGG9p33CV12Qdg@mail.gmail.com>
2016-12-19  4:01           ` NeilBrown
2016-12-19  7:12             ` Jure Erznožnik
2016-12-19 23:39               ` NeilBrown [this message]
2016-12-21 11:33                 ` Jure Erznožnik
2016-12-21 22:52                   ` 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=87inqftro1.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=jure.erznoznik@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    /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).