From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] NFSD: Add v4.2 SEEK support
Date: Tue, 28 Oct 2014 17:09:00 -0400 [thread overview]
Message-ID: <545005EC.9030505@Netapp.com> (raw)
In-Reply-To: <20141028210700.GI32743@fieldses.org>
On 10/28/2014 05:07 PM, J. Bruce Fields wrote:
> On Tue, Sep 30, 2014 at 01:00:24PM -0400, Anna Schumaker wrote:
>> I'm testing with xfstests #285. It's an lseek specific test, and helped
>> find a few edge cases during development.
>
> Any hints? I did basically:
>
> yum install xfsprogs-devel libattr-devel libacl-devel
> git clone git://oss.sgi.com/xfs/cmds/xfstests.git
> cd xfstests
> make
> make install
> cat >local.config <<EOF
> FSTYP=nfs
> TEST_DEV=f20-1:/exports/xfs/xfstests
> TEST_DIR=/mnt
> NFS_MOUNT_OPTIONS='-overs=4.2,sec=sys'
Try setting TEST_FS_MOUNT_OPTIONS instead of NFS_MOUNT_OPTIONS.
> EOF
> ./check -nfs generic/285
>
> Passes just fine, but insists on using 4.0 and sec=krb5p, so apparently
> NFS_MOUNT_OPTIONS is ignored.
>
> I'm probably missing something basic, I haven't used xfstests before
> (shame on me).
>
> --b.
>
next prev parent reply other threads:[~2014-10-28 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 17:58 [PATCH v3 0/2] NFSD: Add v4.2 SEEK support Anna.Schumaker
2014-09-26 17:58 ` [PATCH v3 1/2] NFSD: Add generic v4.2 infrastructure Anna.Schumaker
2014-09-26 17:58 ` [PATCH v3 2/2] NFSD: Implement SEEK Anna.Schumaker
2014-09-26 21:54 ` [PATCH v3 0/2] NFSD: Add v4.2 SEEK support J. Bruce Fields
[not found] ` <CAFX2Jfm2pDmz7vKPVNe8yZScVT-MvVD=+AsfOgdrPfKwgaLTXw@mail.gmail.com>
2014-10-01 18:21 ` J. Bruce Fields
2014-10-28 21:07 ` J. Bruce Fields
2014-10-28 21:09 ` Anna Schumaker [this message]
2014-10-28 21:17 ` J. Bruce Fields
2014-10-28 21:24 ` J. Bruce Fields
2014-10-28 21:29 ` Anna Schumaker
2014-10-28 21:30 ` J. Bruce Fields
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=545005EC.9030505@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox