Possible O_DIRECT problems ?
A message that is not in the archive (sent off-list or not yet received): [email protected]
fyi: the complete patch against 2.4.16 (should work with little or no modification against 2.4.17) is here:
http://www.citi.umich.edu/projects/nfs-perf/patches/
you'll need to apply inode2file.diff then nfs-odirect11.diff, and it requires Trond's pathconf patch in order to be completely useful.
because O_DIRECT cannot do small I/O (must be a multiple of a block size), does fsx work when using it? can someone describe the failures?
Quoted 17 lines · GOTO Masanori
At Fri, 21 Dec 2001 00:39:42 +0000,
Quoted 5 lines · Dave Jones
Quoted 2 lines · Trond Myklebust
O_DIRECTfor NFS isn't yet merged into the kernel. Are these Chuck
Lever's NFS patches you've been testing?Where is Chuck's patch ? I searched but didn't find.
Quoted 3 lines
Nope, stock 2.4.17rc2 & 2.5.1.
I thought NFS might just ignore theO_DIRECTflag if it didn't understand it yet, I wasn't expecting such a dramatic failure.Supporting
direct_IOwith NFS is some meaningful for users who have fast NAS server environment, IMHO.
Quoted 8 lines
Quoted 3 lines
I just got reminded of the bugs Andrew Morton & some others found in
O_DIRECT, so this may be hitting the same problems already found.No, I think it's another issue, but it may be another bugs...
-- gotom
- Chuck Lever
--
corporate: <[email protected]>
personal: <[email protected]>