Messages in this thread | | | Date | Mon, 9 Feb 2004 20:39:26 -0800 | From | Mike Fedyk <> | Subject | 4.1GB limit with nfs3, 2.6 & knfsd? |
| |
Hi,
I was trying to tar and bzip2 some directories over the weekend and I think I may have found a bug.
The operation would consistantly fail when the bzip2ed tar file hit 4.1GB when directed at a 2.6.1-bk2-nfs-stale-file-handles knfsd server from another computer running the same kernel.
If I try the operation against a local filesystem, or a 2.4.24 knfsd server on the network there are no failures and the file is at 18GB and growing on the local filesystem (not enough space on the 2.4 server...).
This is all from the same nfs client computer.
I plan on doing some more tests with dd and cat against the server after the files have finished compressing.
Anyone have any ideas? I know this could be userspace, but why does it work against a 2.4 knfsd and on the local filesystem? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |