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

Bug#714974: nfs-kernel-server: Duplicate cookies reported - jfs partition, with samba



On 07/04/2013 11:03 PM, Ben Hutchings wrote:
Control: reassign -1 src:linux 3.2.46-1 Control: severity -1 important Control: tag -1 moreinfo

On Thu, 2013-07-04 at 19:23 -0500, Karl Schmidt wrote:
Package: nfs-kernel-server Version: 1:1.2.6-4 Severity: serious Justification: Effects
usability of package

nfs-kernel-server contains the scripts to set up the NFS kernel server; the server itself is part
of the 'linux' package.

This error is from the client machne - but I believe the error is caused by the server issuing
duplicate cookies. Repeated multiple times  - From syslog: Jul  4 18:45:17 singapore kernel:
[280774.570555] NFS: directory //accounting contains a readdir loop.Please contact your server
vendor.  The file: .~lock.credit.rtf1.rtf# has duplicate cookie 199

The directory list shows files multiple times
[...]

You said here that this bug was fixed: <http://bugs.debian.org/685407#152>.  Though I was
sceptical, as we didn't change anything in jfs.  So what has changed between then and now?

Worked fine for a while after I upgraded changed the kernel. (fooled myself good )
Now, I've realized problem only occurs in the directory that has a samba share - I had 2 strange settings trying to please a windoze side program:

oplocks = No
level2 oplocks = No

I tried removing these settings. - no joy - I was still able to get this error:


Jul 5 11:24:21 singapore kernel: [340720.514830] NFS: directory accounting/US-bank_viaklix contains a readdir loop.Please contact your server vendor. The file: Services_enabled has duplicate cookie 8

Just before that was this indication of a imap exchange:
Jul 5 11:24:17 singapore rpc.idmapd[2403]: nss_getpwnam: name 'XXXX' not found in domain 'xtronics.network'


Do I need to do something to update the cookies?

Any clues if this is samba related or jfs related?

Related to length of time from last reboot?


The problem seems to be limited to when both windoze and linux file browsers look at the same directory after a new file was created on the windoze side.

The other detail is that this setup had worked for years with the 2.6 kernel so likely some change in moving from squeeze to wheezy triggered the errors.


--------------------------------------------------------------------------------
Karl Schmidt                                  EMail Karl@xtronics.com
Transtronics, Inc.                              WEB http://secure.transtronics.com
3209 West 9th Street                             Ph (785) 841-3089
Lawrence, KS 66049                              FAX (785) 841-0434

We can't tax and sue each other into prosperity. -kps
--------------------------------------------------------------------------------


Reply to: