All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timo Reimann <mailinglist-d4LLFNs4DFRA7UZ8SB9NFg@public.gmane.org>
To: Neil Brown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: mountd prevents spindown of non-exported disk
Date: Thu, 21 Feb 2008 12:18:18 +0100	[thread overview]
Message-ID: <47BD5DFA.8080200@foo-lounge.de> (raw)
In-Reply-To: <18364.64328.189954.417159-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>

Hi Neil,

first of all, thanks for replying.


Neil Brown wrote:
> On Wednesday February 20, mailinglist-d4LLFNs4DFRA7UZ8SB9NFg@public.gmane.org wrote:
>> Although there should be nothing accessing the disk except my custom
>> backup cron job initiating at 5am daily, something was constantly
>> bringing it back into active state after a rough 20-25 minutes. With the
>> help of blktrace, I monitored every single I/O access to the disk and
>> found a single process only that would cause the wake-up:
>>
>>
>> So for some reason, rpc.mountd issues this disk request in regular
>> intervals although nothing on the disk is being NFS-exported according
>> to /etc/exports.
> 
> This is doubtlessly something related to libblkid.
> 
> We use libblkid to get a unique UID for each filesystem and use that
> as an identified in the filehandle.
> 
> We only ever ask it for the UID of specific devices that have been
> exported.  However it is quite possible that it touches other devices
> as well...
> 
> I'm using libblkid in a way that it wasn't originally designed to be
> used.  It was (as far as I can tell) designed to find a device given a
> UUID or similar.  In that case you would expect it to touch every
> device.
> 
> You could always build your own nfs-utils and configure with
> --without-uuid.
> 
> Not an ideal solution...

What would be the downside of that solution? I suppose NFS would keep on
working even if I disabled that switch, but you gave the impression
there was some (major) drawback.


Cheers,

--Timo

  parent reply	other threads:[~2008-02-21 11:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 21:52 mountd prevents spindown of non-exported disk Timo Reimann
2008-02-21  4:17 ` Neil Brown
     [not found]   ` <18364.64328.189954.417159-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-02-21 11:18     ` Timo Reimann [this message]
2008-02-22  0:25       ` Neil Brown
     [not found]         ` <18366.5777.25957.73691-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-02-22 20:03           ` Timo Reimann
2008-02-25 14:24     ` Timo Reimann
     [not found]       ` <47C2CFB1.4000004-d4LLFNs4DFRA7UZ8SB9NFg@public.gmane.org>
2008-02-25 15:51         ` Benjamin Coddington
2008-02-26 14:04           ` Timo Reimann
2008-02-25 16:32         ` J. Bruce Fields

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=47BD5DFA.8080200@foo-lounge.de \
    --to=mailinglist-d4llfns4dfra7uz8sb9nfg@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --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.