@Frantaylor
If you're experiencing similar issue like some of us better don't use Linux it this case.
I'll recomend 2.6.27, because it's marked as long supported one. If you're going to copy large files XFS should be good (it's known to be good when comes to copying big files, but I never used it too much and I'm not sure if it's as good as some people claim). Maybe better use old Ext3, because it's quite mature, so your data should be safe. When comes to number of cores you should know better, it's your server
@Energyman
There was at least one report, but as far I remember nothing specific. I have no single idea what my report should look like in this case, becasue it's quite strange thing. There's always a chance they'll replace buggy kernel part.
However, 2.6.31 looks very promising when comes to this issue.
I don't even care what OS it runs, just that it has first-class NFS4 service. I would prefer Linux because I know it best. If there is something that works perfect out of the can, that would be best, but I am willing to fiddle around if I have to. I can see from the discussion here that Linux is not a slam-dunk.
Hey kraftman, is this something that you share an interest in? Surely you can tell me if 2 cores is sufficient or if I need 4? And do you know what would be the most stable kernel? I want speed, but data corruption is intolerable.
@Energyman
But since almost nobody with the problem ever complains on lkml it will probably never fixed. So if you see this io-hangs, go to lkml. Thank you.
However, 2.6.31 looks very promising when comes to this issue.
Comment