From: Dave Jones <davej@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: loody <miloody@gmail.com>, Linux-FSDevel <linux-fsdevel@vger.kernel.org>
Subject: Re: dummy file read periodically for external USB Hard Disk
Date: Mon, 7 Jul 2014 23:17:04 -0400 [thread overview]
Message-ID: <20140708031704.GA15698@redhat.com> (raw)
In-Reply-To: <20140708130127.0f29a46f@notabene.brown>
On Tue, Jul 08, 2014 at 01:01:27PM +1000, NeilBrown wrote:
> On Mon, 7 Jul 2014 22:42:29 +0800 loody <miloody@gmail.com> wrote:
>
> > hi all:
> > we met a USB Hard Disk that will go to suspend if host stop
> > sending scsi read command over 5mins.
> > To save the IO, kernel will keep the file in page cache as much as
> > he can and under this circumstances, the read command may disappear
> > for a while longer enough to cause the device suspend.
> >
> > is there any kernel config or module parameter can do the dummy
> > read periodically, even the sector 0 (MBR) is fine.
> > or is there any kernel api I can use to read sector 0(MBR) maybe
> > every 4mins?
>
> Open the device with O_DIRECT and read a block every 4 minutes.
> That should keep it awake.
modifying /sys/module/usbcore/parameters/autosuspend might also have the
desired effect without the need for periodic reads.
Dave
next prev parent reply other threads:[~2014-07-08 3:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 14:42 dummy file read periodically for external USB Hard Disk loody
2014-07-08 3:01 ` NeilBrown
2014-07-08 3:17 ` Dave Jones [this message]
2014-07-08 15:00 ` loody
2014-07-09 14:13 ` loody
2014-07-10 0:47 ` NeilBrown
2014-07-11 9:04 ` loody
2014-07-12 3:01 ` Randy Dunlap
2014-07-18 17:31 ` loody
2014-07-18 18:13 ` Randy Dunlap
2014-07-19 10:59 ` loody
2014-07-19 11:02 ` loody
2014-07-19 21:19 ` Randy Dunlap
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=20140708031704.GA15698@redhat.com \
--to=davej@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miloody@gmail.com \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.