On Wed, 2009-03-25 at 15:09 -0700, Richard A Nelson wrote:
> 1) 2.6.29 NFS clients can no longer lock files:
> #strace -f lockfile fubar
> ...
> uname({sys="Linux", node="gothic-ave", ...}) = 0
> lstat64("_V0H.jaqyJB.gothic-ave", 0xbfdac9ec) = -1 ENOENT (No such file or directory)
> open("_V0H.jaqyJB.gothic-ave", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0444) = -1 EINVAL (Invalid argument)
> write(2, "lockfile: ", 10lockfile: ) = 10
> write(2, "Try praying", 11Try praying) = 11
> write(2, ", giving up on \"", 16, giving up on ") = 16
> write(2, "fubar", 5fubar) = 5
> write(2, "\"\n", 2"
>
> clients still on 2.6.28 and lower work fine ... the server *is* 2.26.29
lockfile works fine for me, both on NFSv3 and NFSv4 against my NetApp
filers, and as far as I can remember, there have been no changes to the
exclusive create code in the 2.6.29 client.
Given that you are claiming to be seeing selinux problems on
2.6.29-based servers, could you therefore please check again after
downgrading the server kernel?
Trond
--
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
