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: Sun, 09 Mar 2008 20:50:34 +0100 [thread overview]
Message-ID: <47D43F8A.1050508@foo-lounge.de> (raw)
In-Reply-To: <CFB019DD-6BDA-4007-B4AA-3E06C58196FD@iki.fi>
Timo Sirainen wrote:
> On Mar 9, 2008, at 4:58 AM, Timo Reimann wrote:
>
>>>> However, there is no `ls' or similar call required to wake up my disk.
>>>> It just happens.
>>>
>>> Thanks, mountd is indeed the problem:
>>>
>>> I'll go figure out why it's doing this.
>>
>> If you find a solution prior to the other guys who offered their help to
>> me, please let us (especially me :) ) know.
>
> Well, after half an hour of looking at mountd and libblk code and trying
> to figure out why I can't seem to find the code for what I see in the
> strace, I finally found out the mountd sources were newer than what I
> was using and this issue was already fixed (Debian unstable):
>
> This appears to fix my problem, although it'll probably takes a few days
> until I'm sure. This is the second time already when I've wasted a lot
> of time trying to figure out a problem, only to find out that
> dist-upgrade would have solved it. Have to remember to do that the next
> time. :)
Thanks a lot for the hint, that seems to have fixed it for me as well. I
was previously looking over the changelog too but couldn't relate any of
the entries to my issue successfully. Double-checking whatever I was
doing might have helped my case as well. :)
Like you, I won't be absolutely sure before at least 24h of testing have
passed, but so far there hasn't been a single undesirable spinup of my
backup disk for the last couple of hours. As mentioned before, my disk
wouldn't stay quiet for more than 25 minutes.
For whom it may concern: I'm running Ubuntu Gutsy and did a backport of
nfs-utils 1.1.1-12ubuntu3, currently contained in Hardy.
Cheers,
--Timo
prev parent reply other threads:[~2008-03-09 19:50 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
[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 [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=47D43F8A.1050508@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