Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
At boot-time there are some errors listed for these mounts (even though the IPs are available), but both end up mounted by the time I get to the login shell.
Code:
fsck from util-linux-ng 2.17.2
fsck from util-linux-ng 2.17.2
/dev/sda6: clean, 70446/1463504 files, 5556011/5848320 blocks
/dev/sda1: clean, 212/62248 files, 45287/248832 blocks
init: statd-mounting main process (585) killed by TERM signal^M
mount.nfs: DNS resolution failed for 10.xxx.xxx.xxx: Name or service not known
mount.nfs: DNS resolution failed for 10.xxx.xxx.xxx: Name or service not known
mountall: mount /mnt/mynfs [597] terminated with status 32
mount.nfs: DNS resolution failed for 10.xxx.xxx.xxx: Name or service not known
mountall: mount /mnt/mynfs [620] terminated with status 32
bad user name "myuser"
mountall: mount /mnt/mycifs [598] terminated with status 1
bad user name "myuser"
init: ureadahead-other main process (709) terminated with status 4^M
init: ureadahead-other main process (711) terminated with status 4^M
init: ureadahead-other main process (712) terminated with status 4^M
init: ureadahead-other main process (720) terminated with status 4^M
init: ureadahead-other main process (721) terminated with status 4^M
init: ureadahead-other main process (722) terminated with status 4^M
init: ureadahead-other main process (723) terminated with status 4^M
init: ureadahead-other main process (724) terminated with status 4^M
init: ureadahead-other main process (725) terminated with status 4^M
init: ureadahead-other main process (726) terminated with status 4^M
init: ureadahead-other main process (727) terminated with status 4^M
init: ureadahead-other main process (728) terminated with status 4^M
init: ureadahead-other main process (730) terminated with status 4^M
* Starting AppArmor profiles ^[[80G ^M^[[74G[ OK ]
* Starting web server apache2 ^[[80G ^M^[[74G[ OK ]
.....
After logging in, if I try to "ls /mnt/mycifs" it blocks for around 30 seconds before returning the directory listing. Subsequent reads to the mount are fast and normal. An strace of the "ls /mnt/mycifs" command is as follows (the line in bold is where it gets stuck):
After trying this ls command on the CIFS mount the following error is posted to dmesg:
Code:
CIFS VFS: No response for cmd 50 mid 13
Similarly, if I try to "ls /mnt/mynfs" it blocks forever, never returning the directory listing. Again, here is the strace output (line where it gets stuck in bold):
After booting, if I simply "umount /mnt/mycifs && mount /mnt/mycifs" or "umount /mnt/mynfs && ount /mnt/mynfs" then both mounts are completely fine and list directories quickly and normally. It appears that something funny is happening to the mountpoints at boot-time, though the network is accessible and these shares end up getting mounted.
I could resolve this issue by adding some umount/mount commands to /etc/rc.local, but I would like to resolve the source of the problem rather than add that hack if possible. I have also tried adding the _netdev boot option to /etc/fstab with no improved behavior. Any ideas on why this is occuring and what else I can try to debug it?
You might try changing the mount options and adding _netdev to the options. That tells the system that network connectivity has to be there to mount the device.
Thanks for the suggestion. I tried changing the mount options to "defaults" and "defaults,_netdev" with no improvements. I also tried adding "ASYNCMOUNTNFS=no" to /etc/default/rcS with no improvement. Any other ideas I can try?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.