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: Fri, 22 Feb 2008 21:03:22 +0100 [thread overview]
Message-ID: <47BF2A8A.9030002@foo-lounge.de> (raw)
In-Reply-To: <18366.5777.25957.73691-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
Neil Brown wrote:
> On Thursday February 21, mailinglist-d4LLFNs4DFRA7UZ8SB9NFg@public.gmane.org wrote:
>>> 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.
>>
>
> The fact that you have to compile your own tools rather than just use
> what the distro provides is always a bit of a bore.
>
> Also, if you change the server to stop using UUIDs, then any clients
> which have the filesystem mounted will need to remount as the old
> mount will become stale.
>
> So it isn't a major problem, but nor is it an ideal solution.
Is there a proper place to file a bug report for this issue? I'm lacking
the expertise to know whose responsibility it is, but I remember you
mentioned libblkid before.
--Timo
next prev parent reply other threads:[~2008-02-22 20:03 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
2008-02-22 0:25 ` Neil Brown
[not found] ` <18366.5777.25957.73691-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-02-22 20:03 ` Timo Reimann [this message]
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=47BF2A8A.9030002@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.