From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Wuqixuan <wuqixuan@huawei.com>
Cc: "trond.myklebust@primarydata.com"
<trond.myklebust@primarydata.com>,
Linyongting <linyongting@huawei.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"wuqixuan@gmail.com" <wuqixuan@gmail.com>
Subject: Re: Help to know the stable ver of nfsv4 for commercial app
Date: Fri, 14 Feb 2014 10:53:58 -0500 [thread overview]
Message-ID: <20140214155358.GG21982@fieldses.org> (raw)
In-Reply-To: <BB7C62C2B0732E4DA93834A501E846456C8E98D7@szxema505-mbx.china.huawei.com>
On Fri, Feb 14, 2014 at 08:55:11AM +0000, Wuqixuan wrote:
> Hi Trond, Bfields, All,
>
> We are useing nfsv3 in 2.6.34.13 kernel for commucial use. For some reasons(such as security), has requirement to upgrade to nfsv4(still on 2.6.34.x kernel). We did two things:
>
> 1. I passed through the git log of kernel.org of nfs, found after 2010(2.6.34 is released on May 2010, and no update on 2.6.34.x for nfs/nfsd), just for sampling, nfsd/nfs4proc.c has 460 commits while nfs/nfs3proc.c has only 38 commits.
> 2. Just enable nfsv4 on 2.6.34.13, got problem(EIO) on just a simple open. Found it's because of one commit(https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a2c0b9e291208f65221a0ad8a0c80a377707d480), simply remove this commit, now can simply use nfsv4 on 2.6.34.13.
>
> So we are worried about the stability of nfsv4 on 2.6.34.x.
> If any one has some idea or information about:
>
> 1. Whether nfsv4 (including nfs/nfs4/sunrpc) of 2.6.34.x is stable enough for commercial use or not.
> 2. If nfsv4 is not stable enough on 2.6.34.x, which version can we use , 3.10 ? or 3.12 ?
> 3. Is there any mature commercial application on nfsv4 on 2.6.34.x or before? Can tell some famous company or app name ?
I don't know anything about the specific bug that you found.
Based on https://lwn.net/Articles/585416/ 2.6.34 appears to be EOL'd as
of 2.6.34.15, so it would be up to you to support it past that.
http://www.kernel.org/ lists which stable kernel branches are still
being updated. I'm not sure where you find out how long those branches
are expected to be maintained.
Someone who needs guaranteed support periods for "commercial use"
usually gets a contract with someone like my employer. (And indeed the
enterprise distros do support NFSv4 on kernels that branched off before
2.6.34).
--b.
next prev parent reply other threads:[~2014-02-14 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 8:55 Help to know the stable ver of nfsv4 for commercial app Wuqixuan
2014-02-14 15:53 ` bfields [this message]
2014-02-14 17:12 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2014-02-15 1:45 Wuqixuan
2014-02-17 15:13 ` Dr Fields James Bruce
2014-02-14 8:47 Wuqixuan
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=20140214155358.GG21982@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linyongting@huawei.com \
--cc=trond.myklebust@primarydata.com \
--cc=wuqixuan@gmail.com \
--cc=wuqixuan@huawei.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.