Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
May 31 20:36:38 main kernel: [12596.700620] CIFS VFS: No response to cmd 4 mid 8270
May 31 20:36:38 main kernel: [12596.700806] CIFS VFS: Send error in Close = -11
May 31 20:36:55 main kernel: [12613.623723] CIFS VFS: No response for cmd 6 mid 8274
May 31 20:36:55 main kernel: [12613.623842] CIFS VFS: No response for cmd 50 mid 8275
May 31 20:37:16 main kernel: [12634.680159] CIFS VFS: No response for cmd 6 mid 8279
May 31 20:37:16 main kernel: [12634.680279] CIFS VFS: No response for cmd 50 mid 8280
May 31 20:37:38 main kernel: [12655.706690] CIFS VFS: No response for cmd 6 mid 8285
May 31 20:37:38 main kernel: [12655.706812] CIFS VFS: No response for cmd 50 mid 8286
May 31 20:37:38 main kernel: [12655.946296] CIFS VFS: No response for cmd 50 mid 8287
May 31 20:37:38 main kernel: [12655.946413] CIFS VFS: No response for cmd 50 mid 8288
May 31 20:37:43 main kernel: [12661.334499] CIFS VFS: No response for cmd 50 mid 8289
I'm 99% sure they're generated by Courier-imap trying to access emails stored in my QNAP NAS.
The shared folder of my NAS is mounted in fstab with:
//192.168.168.10/mail /mnt/mail cifs username=virtual,password=miapw,iocharset=utf8,nos erverino,uid=5000,gid=5000,_netdev,mapchars 0 0
Ubuntu 10.10 running on VMWare with Postfix + Courier-IMAP + MySQL.
I've read about similar problems on the Net solved disabling the optimistic locking of cifs. This trick didn't solve my problem.
I used to see these and switched to using autofs. With autofs
a new connection is sought if the existing connection breaks.
It's likely that a temporary glitch is breaking the connection
and the traditional mount doesn't know how to reestablish it.
I tried but I received an error of mounting not allowed because wrong type of fs, "superblock" not valid (I'm translating so the messages could be sligthly different). dmesg says "autofs: called called with bogus options".
I'm trying to follow your logic. First you said you're getting "No response"
errors when you use mount. I mentioned autofs, and you said when you ran it
you received an error about "bogus options." I asked you to post the autofs
files, and you show an entry for /etc/fstab, which is used for mount and not
Hmmm. Are we talking about the same thing? Autofs is a daemon with its own
Hi, you are right, I didn't know autofs, I wrongly supposed it was a parameter like cifs ("type" of mount).
I've read something now about it, I followed some "How To" but...I failed!
If you can please guide me step by step considering that I already installed autofs, smbclient and smbfs.
I wanna reach my nas' mail share through /mnt/mail exactly like I already do with the usual mount described above.
I guess you should tell me exactly what to write inside auto.master and the other auto.xxx files.