>>>>> "Clay" == Clay McClure <clay@xxxxxxxxxxx> writes:
Clay> Hello, When multiple 2.6.18 NFSv3 clients write to the same
Clay> file, after one of the clients has recently read from the
Clay> file, we see data corruption in the form of null bytes
Clay> inserted into the file.
If its the same bug we've seen it appeared in 2.6.17 and we "fixed" by
downgrading the involved hosts to 2.6.16. It was related to this post
by Trond Myklebust (in Jan/Feb) :-
That is very likely to be the same problem as fixed in
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=5d47a35600270e7115061cb1320ee60ae9bcb6b8
AFAICR, all kernels after 2.6.17 were affected. Can you therefore see if
the same patch applies to 2.6.19, and if it fixes your problem?
Cheers
Trond
Sincerely,
Adrian Phillips
--
Who really wrote the works of William Shakespeare ?
http://www.pbs.org/wgbh/pages/frontline/shakespeare/
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
NFS maillist - NFS@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@xxxxxxxxxxxxxxxxxxxxx is being discontinued.
Please subscribe to linux-nfs@xxxxxxxxxxxxxxx instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
