[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#816613: marked as done (linux-image-amd64: nfs4_unique_id conflict on 3.16.7-ckt20-1+deb8u3)

Your message dated Thu, 06 May 2021 20:12:18 +0200
with message-id <E1leiTk-001On3-5A@hullmann.westfalen.local>
and subject line Closing this bug
has caused the Debian Bug report #816613,
regarding linux-image-amd64: nfs4_unique_id conflict on  3.16.7-ckt20-1+deb8u3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
816613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816613
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-amd64
Version: 3.16+63
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
     Update linux-image-amd64 to version 3.16.7-ckt20-1+deb8u3.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     I did not pass the parameter nfs.nfs4_unique_id=blablabla to the kernel. I think it would solve the problem, but the point here is the default behavior from nfs client ID: it uses the hostname to generate the default client ID as stated in nfs.txt. I assured that there are not two clients with the same hostname. 
   
   * What was the outcome of this action?
     The NFS mount was remounted read-only and the message:
        kernel: [341091.216825] NFS: Server nfs reports our clientid is in use
     appeared in syslog.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-3.16.0-4-amd64  3.16.7-ckt20-1+deb8u3

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
This bug was filed for a very old kernel. If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from buster.backports
please reopen the bug, see https://www.debian.org/Bugs/server-control

--- End Message ---
Reply to: