Linux NFS development
 help / color / mirror / Atom feed
From: Timo Reimann <mailinglist-d4LLFNs4DFRA7UZ8SB9NFg@public.gmane.org>
To: Timo Sirainen <tss@iki.fi>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS server waking up sleeping disks
Date: Sat, 08 Mar 2008 14:59:30 +0100	[thread overview]
Message-ID: <47D29BC2.9000806@foo-lounge.de> (raw)
In-Reply-To: <1204969522.11220.680.camel@hurina>

Timo Sirainen wrote:
> My Linux 2.6.24.1 NFS server has two disks. One of them is rarely used,
> so it's normally sleeping and is not even mounted anywhere. But after
> the NFS mount hasn't been used for a while (some hours?) doing just a
> "ls" on NFS client causes the sleeping disk to wake up and the "ls"
> reply is delayed a few seconds until the wakeup is finished.
> 
> Any ideas why it's waking up the disk that has nothing to do with NFS,
> and how to prevent it from doing this?

Your issue might be related to the same that I have (which is still
unresolved). Basically, my non-mounted backup disk keeps spinning up
after a rough 20-25 minutes of sleeping. Check out my archived thread
for details and hints how to determine disk-accessing processes:

http://marc.info/?l=linux-nfs&m=120354580303104&w=2

However, there is no `ls' or similar call required to wake up my disk.
It just happens.


Regards,

--Timo (too)

  reply	other threads:[~2008-03-08 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-08  9:45 NFS server waking up sleeping disks Timo Sirainen
2008-03-08 13:59 ` Timo Reimann [this message]
     [not found]   ` <47D29BC2.9000806-d4LLFNs4DFRA7UZ8SB9NFg@public.gmane.org>
2008-03-08 23:27     ` Timo Sirainen
2008-03-09  2:58       ` Timo Reimann
     [not found]         ` <47D35249.7020000-d4LLFNs4DFRA7UZ8SB9NFg@public.gmane.org>
2008-03-09  3:11           ` Timo Sirainen
2008-03-09 19:50             ` Timo Reimann

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=47D29BC2.9000806@foo-lounge.de \
    --to=mailinglist-d4llfns4dfra7uz8sb9nfg@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tss@iki.fi \
    /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