> >From the mount/unmount end, I get the following:
> root:reliant me2v$ mount | grep WINNT
> //WINNT/C$ on /home/me2v/mounts type smbfs (0)
> root:reliant me2v$ ls mounts
> ls: mounts: Input/output error
> root:reliant me2v$ smbumount mounts
> Could not open mounts: Input/output error
> root:reliant me2v$ umount mounts
> root:reliant me2v$
> As you see, umount works, but smbumount, I had thought was what normal
> users (as opposed to root) were supposed to use. I did all the above
> (except the umount) as a normal user, also, with the same results.
> >From /var/log/messages:
> Mar 25 10:12:18 reliant kernel: smb_retry: signal failed, error=-3
> Mar 25 10:12:45 reliant last message repeated 3 times
Uh oh... I know this is going to sound condensending but please
bear with me and understand that this has happened before (hell, its
happened to me before). The "Signal failed, error=-3" is indicative of
an earlier version of smbmount that would give all of the symptoms exactly
as you have described. That makes me suspicious that you may not have
successfully updated the smbmount binary.
1) Double check that you ran configure with the "-with-smbmount"
option before building and installing samba. You can check the Makefile
in the source directory for a define for "MPROGS". If that define is
empty, you didn't build smbmount.
2) Make sure that you don't have more than one smbmount in your path.
If you don't specify the -prefix=/usr option when configuring the Samba
build, smbmount is going to get installed in /usr/local/bin instead of
/usr/bin. If there is already an smbmount in /usr/bin, you will execute
that one instead of the new one.
"whereis smbmount" will tell you were all the versions are.
"which smbmount" will tell you which one got executed.
Do an "ls -l" on the smbmount indicated by which and verify that
it was updated by your build.
3) If you are running RedHat, make sure that you applied the
RedHat package patches out of "packaging/RedHat/*.patch" before doing
the configure and build (Actually, I think the patch to Makefile.in
is the only important one. The other one is for smbsh and doesn't
affect smbmount).
> I'm not quite sure how to diagnose this problem and fix it. Any
> suggestions would be welcome.
>
>
> --
> Matthew Vanecek
> Studies in Business Computers at the University of North Texas
> http://www.unt.edu/bcis
> *****************************************************************
> Visit my Website at http://people.unt.edu/~mev0003
> *****************************************************************
> For 93 million miles, there is nothing between the sun and my shadow
> except me. I'm always getting in the way of something...
Mike
-- Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com (The Mad Wizard) | (770) 925-8248 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/