Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: John Adams <john.adams@avid.com>
To: "scameron@beardog.cce.hp.com" <scameron@beardog.cce.hp.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: "mike.miller@hp.com" <mike.miller@hp.com>
Subject: Re: Question about seemingly extraneous i/o's
Date: Thu, 10 May 2012 19:39:58 +0000	[thread overview]
Message-ID: <CBD190C1.114E%jadams@avid.com> (raw)
In-Reply-To: <20120510185614.GY11309@beardog.cce.hp.com>


On 5/10/12 2:56 PM, "scameron@beardog.cce.hp.com"
<scameron@beardog.cce.hp.com> wrote:

>
>I have this script, which just cranks up the scsi logging level
>a bit, then writes 1 block out to a disk, sleeps a bit, then
>cranks the logging back down.  There's no other i/o going
>to the disk (not mounted, no filesystem)
>
>-----8<---- -----8<---- -----8<---- -----8<---- -----8<----
>#!/bin/sh
>
>logger 
>vvvvvv==============================================================vvvvvv
>LOGGING_LEVEL=14683648
>
>sysctl -w dev.scsi.logging_level=$LOGGING_LEVEL
>dd if=/dev/zero of=/dev/sdb count=1 bs=512 seek=5000 oflag=direct
>sleep 1
>sysctl -w dev.scsi.logging_level=0
>logger 
>^^^^^^==============================================================^^^^^^
>-----8<---- -----8<---- -----8<---- -----8<---- -----8<----
>
>
>This script produces the log below.  It does the write, as
>expected, but then it also does a test unit ready, then inquiries and a
>bunch of reads.
>
>Where are these coming from?

I had a similar question once and found that when I closed the disk
handle, udev was invoking blkid and that was generating some read noise.
blktrace was helpful there.

>


      reply	other threads:[~2012-05-10 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 18:56 Question about seemingly extraneous i/o's scameron
2012-05-10 19:39 ` John Adams [this message]

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=CBD190C1.114E%jadams@avid.com \
    --to=john.adams@avid.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.miller@hp.com \
    --cc=scameron@beardog.cce.hp.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