On Tue, Dec 04, 2001 at 08:20:44AM +0100, Florian Schaefer wrote:
> On Mon, 3 Dec 2001 16:16:12 -0500, Jan Harkes said:
> > I guess once in a blue moon, the O_DIRECT bit will be set and the
> > readdir will fail in the DirectIO path, while otherwise it will run
> > fine. Could you try the followin
On Mon, 3 Dec 2001 16:16:12 -0500, Jan Harkes said:
> I guess once in a blue moon, the O_DIRECT bit will be set and the
> readdir will fail in the DirectIO path, while otherwise it will run
> fine. Could you try the following patch to linux/fs/coda/dir.c
I just applied it and recompiled the modu
3:03 dexter kernel: coda_pioctl: Venus returns: -13 for (0x7f01,0x1,0x1)
Dec 3 19:53:08 dexter kernel: coda_pioctl: Venus returns: -107 for
(0x7f00,0x1,0x1)
Dec 3 19:53:17 dexter kernel: coda_venus_readdir: cannot read directory -22.
Coda ioctls with -13 (EACCES), and -107 (ENOTCONN) return codes
Hi again,
OK, the problem can be reproduced.
I just restarted my computer and encountered the same problem. And it
could be resolved in the same way: I had to start X, then it goes away
without anything else done. I can even close X again and still have
access to my coda volume.
I know that ev
that dir and just got "cannot read directory -22".
>From /var/log/messages:
Dec 3 19:53:03 dexter kernel: coda_pioctl: Venus returns: -13 for
(0x7f01,0x1,0x1)
Dec 3 19:53:08 dexter kernel: coda_pioctl: Venus returns: -107 for
(0x7f00,0x1,0x1)
Dec 3 19:53:17 dexter kernel: coda_ven
