The "open failed, retrying R/O" messages aren't serious; they just
indicate the file was locked or otherwise in use -- in this case
presumably because it's on a read-only medium. Probably should add a
test for RO filesystems and not try to open r/w (And I should probably
change these to DEBUG_VERBOSE class messages.)
Do you happen to know if I could rely on the read-only attribute being
set for an exported CD?
> No6:24:17 zeego kernel: eth1: Interrupted while interrupts are masked! isr=0x0 imr=0x0.
Don't know what this is, but I hope smbfs didn't cause it!
> Later, I got some other problems when trying to list any directories from
> the mounted filesystems:
> No7:23:35 zeego kernel: smb_trans2_request: result=-32, setting invalid
> Nov 16 17:23:46 zeego kernel: smb_retry: timed out, try again later
> No7:23:46 zeego kernel: smb_lookup: find //usr failed, error=-32
> Nov 16 17:23:57 zeego kernel: smb_retry: timed out, try again later
> No7:23:57 zeego kernel: smb_lookup: find //usr failed, error=-5
> Nov 16 17:23:57 zeego kernel: smb_retry: caught signal
> No7:23:57 zeego kernel: smb_proc_readdir_long: error=-5, breaking
> Nov 16 17:23:57 zeego kernel: smb_refill_dircache: readdir failed, result=-5
> No7:24:04 zeego kernel: smb_retry: caught signal
Something is very wrong here -- the samba server isn't giving smbfs a
new connection. Dropping a connection is very common, but it's supposed
to recover right away. Possible network problems?