From: Jeff Blaine <jblaine@mitre.org>
To: nfs@lists.sourceforge.net
Subject: General NFSv3 + Linux kernel timeline?
Date: Tue, 11 Jan 2005 11:32:33 -0500 [thread overview]
Message-ID: <41E3FFA1.8020609@mitre.org> (raw)
I've read the FAQ. A lot of the information is not very
specific as to affected versions:
Is there any (or can anyone take 5 minutes to write up)
timeline that lists the major obvious problems throughout
2.4.21 to 2.6.9 and where they were fixed and enabled
(NOT experimental) in the kernel?
Things like the "file corruption when very rapid writes
from different clients leave the file size unchanged"
bug, rsize/wsize problems, etc.
Thanks for any info.
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-01-11 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 16:32 Jeff Blaine [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-12 14:44 General NFSv3 + Linux kernel timeline? Lever, Charles
2005-01-12 17:46 ` Trond Myklebust
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=41E3FFA1.8020609@mitre.org \
--to=jblaine@mitre.org \
--cc=nfs@lists.sourceforge.net \
/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.