[Bugme-new] [Bug 9212] New: 9p: Frequent bad file descriptors from
u9fs
bugme-daemon at bugzilla.kernel.org
bugme-daemon at bugzilla.kernel.org
Mon Oct 22 11:03:48 PDT 2007
http://bugzilla.kernel.org/show_bug.cgi?id=9212
Summary: 9p: Frequent bad file descriptors from u9fs
Product: File System
Version: 2.5
KernelVersion: 2.6.22
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: v9fs
AssignedTo: ericvh at gmail.com
ReportedBy: ericvh at gmail.com
CC: sqweek at gmail.com
From: sqweek at gmail.com
So ever since I actually converted to u9fs on my server, I keep getting:
ls: cannot access /home/sqweek/mail//new: Bad file descriptor
I have a precmd that checks my maildir every time a prompt is
displayed, and every time it hits problems it seems to be just as I
open a new terminal (and therefore shell, of course) - often enough
because I just got a mail notification so I open a new terminal to
check it.
Here's what the serverside u9fs log has to say:
<- Twalk tag 0 fid 10 newfid 11 nwname 0
-> Rwalk tag 0 nwqid 0
<- Topen tag 0 fid 11 mode 0
-> Ropen tag 0 qid (0000000000058211 1193059597 d) iounit 0
<- Twalk tag 0 fid 10 newfid 12 nwname 0
-> Rwalk tag 0 nwqid 0
<- Tstat tag 0 fid 12
-> Rstat tag 0 stat 'new' 'sqweek' 'wheel' '' q (0000000000058211
1193059597 d) m 020000000755 at 1193066604 mt 1193059597 l 0 t 0 d 0
<- Tclunk tag 0 fid 12
-> Rclunk tag 0
<- Tread tag 0 fid 11 offset 0 count 8192
-> Rread tag 0 count 0 ''
<- Tclunk tag 0 fid 11
-> Rclunk tag 0
<- Twalk tag 0 fid 9 newfid 11 nwname 0
-> Rwalk tag 0 nwqid 0
<- Tflush tag 1 oldtag 0
-> Rflush tag 1
<- Twalk tag 0 fid 9 newfid 11 nwname 0
-> Rerror tag 0 ename fid already in use
<- Twalk tag 0 fid 10 newfid 11 nwname 0
-> Rerror tag 0 ename fid already in use
It does appear that fid 11 is attempting to be reused without being
clunked, but I'm *far* from fluent with 9p, so I post it to an
audience that is.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the Bugme-new
mailing list