Re: kern/46377 (Use of Coda file system triggers an immediate kernel panic)

[christos%zoulas.com@localhost (Christos Zoulas)]

The following reply was made to PR kern/46377; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: u-bsdmwle%aetey.se@localhost, gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
        netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/46377 (Use of Coda file system triggers an immediate kernel 
panic)
Date: Fri, 4 May 2012 13:57:10 -0400

 On May 4,  5:28pm, u-bsdmwle%aetey.se@localhost (u-bsdmwle%aetey.se@localhost) 
wrote:
 -- Subject: Re: kern/46377 (Use of Coda file system triggers an immediate ker
 
 | Yes this works now! Thanks a lot.
 
 Wonderful.
 
 | I can now directly run most of my software environment (including
 | among others openoffice and mplayer), without installing anything
 | locally - besides the Coda client itself.
 
 Great.
 
 | Starting/running different programs for about an hour did not crash
 | the system. The only occasional console messages were like
 | 
 | -----
 | coda_getpages: cannot open vnode 0xc538600c => 13
 | -----
 | 
 | which may have been triggered by interrupting a process before
 | its open() fetch operations completed, or alike (?). Hopefully
 | not a kernel issue at all.
 
 13 == EACCES, means that you cannot do the operation on this file;
 perfectly normal. I have commented out all the vnops debugging printfs
 now.
 
 thanks for testing!
 
 christos