Bug 11813

Summary: xfs filesystem exported via nfs don't work in 2.6.27.3
Product: File System Reporter: François Valenduc (francoisvalenduc)
Component: XFSAssignee: XFS Guru (xfs-masters)
Status: REJECTED INVALID    
Severity: normal    
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2.6.27.3 Subsystem:
Regression: --- Bisected commit-id:

Description François Valenduc 2008-10-23 12:32:51 UTC 
Latest working kernel version: 2.6.27.2
Earliest failing kernel version: 2.6.27.3
Distribution: Gentoo
Hardware Environment:
Software Environment:
Problem Description:

With kernel 2.6.27.3, it's impossible to use a xfs filesystem  exported via NFS. I am using gentoo and I share a portage tree mounted on an xfs filesystem via NFS. Each time packages are fetched, the emerge process is blocked. It seems the problematic commit is the following:

commit c068663ae65e507814545b59a8e2090f48a85613
Author: Christoph Hellwig <hch@lst.de>
Date:   Sun Oct 12 14:30:44 2008 +0200

    xfs: fix remount rw with unrecognized options

    commit 6c5e51dae2c37127e00be392f40842e08077e96a upstream

    When we skip unrecognized options in xfs_fs_remount we should just break
    out of the switch and not return because otherwise we may skip clearing
    the xfs-internal read-only flag.  This will only show up on some
    operations like touch because most read-only checks are done by the VFS
    which thinks this filesystem is r/w.  Eventually we should replace the
    XFS read-only flag with a helper that always checks the VFS flag to make
    sure they can never get out of sync.

    Bug reported and fix verified by Marcel Beister on #xfs.
    Bug fix verified by updated xfstests/189.

If I revert it, the problem doesn't occur.

Steps to reproduce:
Comment 1 Eric Sandeen 2008-10-23 14:53:19 UTC 
Is the exported path part of your root fs?
What options is the xfs filesystem mounted with (cmdline and/or fstab, as well as what /proc/filesystems shows...)
The emerge process is on the client, right ... what does sysrq-w show for that process?
Comment 2 François Valenduc 2008-10-24 11:30:01 UTC 
It appears it works correctly now. I think I didn't remounted the exported filesystem on the client. That's probably the reason of the failure.