All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre FAUQUEMBERGUE <pierref@buf.com>
To: Harald Dunkel <harald.dunkel@aixigo.de>, linux-nfs@vger.kernel.org
Subject: Re: Debian kernel:
Date: Mon, 18 Jan 2016 16:36:23 +0100	[thread overview]
Message-ID: <569D0677.8070908@buf.com> (raw)
In-Reply-To: <5694F0E8.1060400@aixigo.de>

Hi Harri,

thank you for your time and the tips.

so, I will do that :

1. modify /etc/default/grub with :

GRUB_CMDLINE_LINUX="nfs.nfs4_unique_id=${GRUB_DEVICE_UUID}"

2. See the result :

grub-mkconfig | less -Sr

3. rebuild grub.cfg :

sudo update-grub

4. Reboot

I will let you know, if the error keep going to appear.

thanks.


Pierre



On 01/12/2016 01:26 PM, Harald Dunkel wrote:
> Hi Pierre,
>
> On 01/07/2016 07:34 PM, PIERRRE wrote:
>> Hi,
>>
>> I have the same issue with several NFS servers. Cannot find any help.
>>
>> How did you fixed it with grub ?
> I set
> 	GRUB_CMDLINE_LINUX="nfs.nfs4_unique_id=e2177c92-1fe6-48db-918b-ddefba900379"
>
> in /etc/default/grub and rebuild the grub.cfg file.
>
> The important point is that every NFS client and every root
> partition get its own unique id. Be careful, especially if
> you clone your hosts.
>
> You can generate a new ID using uuidgen on the command line.
>
>
> Hope this helps
> Harri


      reply	other threads:[~2016-01-18 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06  6:40 Debian kernel: "Server nfs-home reports our clientid is in use" Harald Dunkel
2015-08-11  7:09 ` Harald Dunkel
2016-01-07 18:34   ` Debian kernel: PIERRRE
2016-01-12 12:26     ` Harald Dunkel
2016-01-18 15:36       ` Pierre FAUQUEMBERGUE [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=569D0677.8070908@buf.com \
    --to=pierref@buf.com \
    --cc=harald.dunkel@aixigo.de \
    --cc=linux-nfs@vger.kernel.org \
    /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.