My current patch set for smbfs tests for the read-only attribute and
disables write permission for the inode, and then won't try to open a
file r/w. So it should suppress the open failed messages.
> No, no network problems. I've got two machines together on the 10Base2
> ethernet, and I can ftp and scp between the two. Now, I also cannot
> unmount the filesystem because it tells me it is busy.
I posted a patch for a bug in fs/namei.c that was leaking a dentry if a
lookup failed, as it will on smbfs if a file is busy (e.g. pagefile.sys
on NT). This was keeping smbfs from unmounting in some cases.
It's also possible that the connection failure is causing the unmount
problems.
Regards,
Bill