Bug 530625 - getcwd failure on NFS4 mounted file systems
Summary: getcwd failure on NFS4 mounted file systems
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 11
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-23 20:31 UTC by Wolfgang Denk
Modified: 2010-06-28 15:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 15:07:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Logfile of "strace -f make -s" (762.10 KB, application/octet-stream)
2009-10-23 20:31 UTC, Wolfgang Denk
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Gentoo 289022 0 None None None Never

Description Wolfgang Denk 2009-10-23 20:31:55 UTC
Created attachment 365889 [details]
Logfile of "strace -f make -s"

Description of problem:

When running "make" in directories on NFS4 mounted file systems,
getcwd() fails occasionally:


Version-Release number of selected component (if applicable):
kernel-2.6.30.8-64.fc11.x86_64

How reproducible:

The problem is stable, it happened reliably with every test I ran so far.

Steps to Reproduce:
1. Download and unpack ftp://ftp.denx.de/pub/u-boot/u-boot-2009.08.tar.bz2
2. Install some cross tool chain, say ELDK.1s
   Then "export CROSS_COMPILE=ppc_6xx-"
3. "make mrproper; make A3000_config; make -s"
  
Actual results:

-> make -s
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory


Expected results:

No such error messages

Additional info:

/etc/exports on NFS4 server:
============================

/srv/nfs4       10.0.0.0/255.0.0.0(rw,insecure,no_subtree_check,nohide,sync,fsid=0)     192.168.0.0/255.255.0.0(rw,insecure,no_subtree_check,nohide,sync,fsid=0)
/srv/nfs4/home  10.0.0.0/255.0.0.0(rw,insecure,no_subtree_check,nohide,sync)            192.168.0.0/255.255.0.0(rw,insecure,no_subtree_check,nohide,sync)

/etc/fstab on client:
=====================

castor:/                /mnt/castor             nfs4    rw,rsize=8192,wsize=8192,intr 00
/mnt/castor/home        /home                   none    rw,bind         0 0

-> mount
...
castor:/ on /mnt/castor type nfs4 (rw,rsize=8192,wsize=8192,intr,clientaddr=192.168.1.4,addr=192.168.1.2)
/mnt/castor/home on /home type none (rw,bind)


I'm running the tests in a subdirectory of "/home"

Part of the Makefile which contains the failing shell commands:

...
$(obj).depend:  $(src)Makefile $(TOPDIR)/config.mk $(SRCS)
                @rm -f $@
                @for f in $(SRCS); do \
                        g=`basename $$f | sed -e 's/\(.*\)\.\w/\1.o/'`; \
                        $(CC) -M $(HOSTCFLAGS) $(CPPFLAGS) -MQ $(obj)$$g $$f >> $@ ; \ 
                done
...

The shell running the "for" loop is failing because of the getcwd()
issue - see attached strace log. Look for pid 14647.



Notes:

1) Originally I had cachefilesd running and the "fsc" mount option
   on; disabling both (and rebooting) did not change the behaviour.

2) This seems to be a more generic problem; this gentoo bug report
   looks suspiciously similar:
   http://bugs.gentoo.org/show_bug.cgi?id=289022

3) Mounting the same file system with NFS3 makes the problem go aways.

Comment 1 Bug Zapper 2010-04-28 10:56:43 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2010-06-28 15:07:19 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.