All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Rees <rees@umich.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: xfstests fails on nfs4 file system
Date: Sat, 30 Jul 2011 13:08:22 -0400	[thread overview]
Message-ID: <20110730170822.GA27493@merit.edu> (raw)
In-Reply-To: <20110730163326.GA19290@infradead.org>

Christoph Hellwig wrote:

  On Sat, Jul 30, 2011 at 11:16:04AM -0400, Jim Rees wrote:
  > xfstests fails on nfs4 file system:
  > 
  > rhcl1# mount -t nfs -o nfsvers=4,minorversion=1 emc-1:/pnfs2 /mnt/emc-1
  > rhcl1# cd /home/rees/xfstests
  > rhcl1# setenv TEST_DEV emc-1:/pnfs2
  > rhcl1# setenv TEST_DIR /mnt/emc-1/rees/xfstests
  > rhcl1# ./check -nfs
  > common.rc: Error: $TEST_DEV (emc-1:/pnfs2) is not a MOUNTED nfs filesystem
  > /bin/df: `emc-1:/pnfs2': No such file or directory
  > /bin/df: no file systems processed
  > 
  > Originally nfs4 was a separate file system type, and it still shows up that
  > way in mtab:
  > emc-1:/pnfs2/ on /mnt/emc-1 type nfs4 (rw,relatime,vers=4,...
  > 
  > I fixed this by commenting out the type check at the end of common.rc.  I
  > don't know enough about the innards of xfstests to know what the proper fix
  > is.  Maybe a substring match, or explicit check for nfs4?
  
  What about the following patch?  I makes sure the nfs4 output gets
  normalized to nfs as early as possible.

Makes sense, and it works.

Tested-by: Jim Rees <rees@umich.edu>

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2011-07-30 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30 15:16 xfstests fails on nfs4 file system Jim Rees
2011-07-30 16:33 ` Christoph Hellwig
2011-07-30 17:08   ` Jim Rees [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=20110730170822.GA27493@merit.edu \
    --to=rees@umich.edu \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.com \
    /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.