Messages in this thread | | | Date | Sat, 27 Mar 1999 03:58:45 -0600 (CST) | From | mev0003@unt ... | Subject | Re: smbfs still timing out |
| |
On 26 Mar, Eloy A. Paris spewed forth: :: I have seen this here too, and also when doing an ls on the root :: directory of my NT box. The page file is locked or something so :: whatever smbfs is trying to do with the file at the moment of a ls, it :: gets an error from NT. :: :: peloy.- :: :: Michael H. Warfield <mhw@wittsend.com> wrote: :: > mev0003@unt.edu enscribed thusly: :: > :: > [...] :: > [snip]
Fsck, Fsck, Fsck, Fsck, It happened again. Mar 27 02:47:05 reliant kernel: smb_retry: signal failed, error=-3 Mar 27 02:47:05 reliant kernel: smb_retry: signal failed, error=-3 Mar 27 02:48:45 reliant last message repeated 2 times Mar 27 03:53:40 reliant kernel: smb_retry: signal failed, error=-3
That's with the password included in the command line.
Here's what's currently mounted: root:reliant lib$ mount /dev/sda1 on / type ext2 (rw) none on /proc type proc (rw) /dev/sda3 on /home type ext2 (rw) /dev/sda2 on /usr/local type ext2 (rw) //WINNT/C$ on /home/me2v/mounts type smbfs (0) //WINNT/ME2V on /home/me2v/winnt type smbfs (0) /dev/scd0 on /mnt/cdrom type iso9660 (ro)
and you have to be root to umount the shares when this happens too: me2v:reliant me2v$ smbumount mounts Could not open mounts: Input/output error
root:reliant lib$ umount /home/me2v/mounts root:reliant lib$
gAR!!
-- 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...
- 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/
| |