From: Trond Myklebust on
On Wed, 2010-03-24 at 14:02 -0400, Trond Myklebust wrote:
> I'd say you have a corruption issue either on the server side or on your
> client.

By the way. Does this issue happen with NFSv4 too, or is it only
NFSv4.1?

Trond

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Doug Nazar on
On 2010-03-24 2:06 PM, Al Viro wrote:
>
> How consistent are the effects you are seeing from test to test on the same
> kernel? This one was very interesting, since it seemed to fail with
> -EISDIR while opening .git/objects/pack. Which is a directory and which
> should fail with -EISDIR if and only if we pass O_CREAT to open(). And
> passing O_CREAT on that one is probably not an intended behaviour of git...
>
> Does anybody else see NFS breakage starting at that commit, BTW? Other
> testcases would be useful...
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo(a)vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>

I also see it....didn't bisect it yet since I was in a rush and had a
simple work around. I was doing a git pull between two repositories on a
NFS 4 w/krb5 security. Got the error about .git/objects/pack (error:
unable to open object pack directory: .git/objects/pack: Is a
directory). If I then run 'ls .git/objects/pack', and then the 'git
pull' again it works.

Doug

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Boaz Harrosh on
On 03/24/2010 08:10 PM, Trond Myklebust wrote:
> On Wed, 2010-03-24 at 14:02 -0400, Trond Myklebust wrote:
>> I'd say you have a corruption issue either on the server side or on your
>> client.
>

It is surely a corruption on the client. I've tested with an old server
and it fails just the same.

> By the way. Does this issue happen with NFSv4 too, or is it only
> NFSv4.1?
>
> Trond
>

-o minorversion=0 or =1 does not matter.
nfsv3 does not have that problem. (Same client different server though)

Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Al Viro on
On Thu, Mar 25, 2010 at 11:39:38AM +0200, Boaz Harrosh wrote:

> It makes no difference, fails just the same. Would an "strace" help?

It might, especially if you ran it for identical repositories on local
fs and on NFS; at least that way it would be possible to see where do
they diverge...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Benny Halevy on
On Mar. 24, 2010, 20:10 +0200, Trond Myklebust <trond.myklebust(a)fys.uio.no> wrote:
> On Wed, 2010-03-24 at 14:02 -0400, Trond Myklebust wrote:
>> I'd say you have a corruption issue either on the server side or on your
>> client.
>
> By the way. Does this issue happen with NFSv4 too, or is it only
> NFSv4.1?

I reproduced this both over v4 and v4.1 with ext3 exported on the server.

Benny

>
> Trond
>
> _______________________________________________
> pNFS mailing list
> pNFS(a)linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/