Hi,
Just before the Thanksgiving break, we enabled quotas on the /home areas on the mseas-data server (running CentOS 5.8), using the following line in the updated /etc/fstab
/dev/mapper/the_raid-lv_home /home ext3 defaults,usrquota,grpquota 1 0
Following the Thanksgiving reboot of mseas-data we have been experiencing problems with svn on mseas (our front-end machine, running CentOS 6.2). After consulting with the svn mailing list, it appeared to be a communication issue between mseas and mseas-data. We therefore rebooted mseas. Now mseas is not mounting /home. We get the following error
[root@mseas etc]# mount mseas-data:/home mount.nfs: Unknown error 521
We have tried this mounting with both of the following lines in fstab and got the same error
mseas-data:/home /home nfs defaults 0 0
mseas-data:/home /home nfs defaults,usrquota,grpquota 0 0
(the latter was to mimic the mounting of /home on mseas-data)
The only thing we've found out on the web so far was advice on editting /etc/exports to have an "insecure" option for the export of /home, which we already had.
Any thoughts on how to resolve or debug this issue would be greatly appreciated.
Thank you.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley@mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301
Hi,
A quick follow-up. I tried reverting back to the set ups on both machines before we enabled quotas. Rebooted both machines. Still cannot mount /home from the client (mseas).
Thanks.
Hi,
Just before the Thanksgiving break, we enabled quotas on the /home areas on the mseas-data server (running CentOS 5.8), using the following line in the updated /etc/fstab
/dev/mapper/the_raid-lv_home /home ext3 defaults,usrquota,grpquota 1 0
Following the Thanksgiving reboot of mseas-data we have been experiencing problems with svn on mseas (our front-end machine, running CentOS 6.2). After consulting with the svn mailing list, it appeared to be a communication issue between mseas and mseas-data. We therefore rebooted mseas. Now mseas is not mounting /home. We get the following error
[root@mseas etc]# mount mseas-data:/home mount.nfs: Unknown error 521
We have tried this mounting with both of the following lines in fstab and got the same error
mseas-data:/home /home nfs defaults 0 0
mseas-data:/home /home nfs defaults,usrquota,grpquota 0 0
(the latter was to mimic the mounting of /home on mseas-data)
The only thing we've found out on the web so far was advice on editting /etc/exports to have an "insecure" option for the export of /home, which we already had.
Any thoughts on how to resolve or debug this issue would be greatly appreciated.
Thank you.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley@mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301 _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi,
A quick follow-up. I tried reverting back to the set ups on both machines before we enabled quotas. Rebooted both machines. Still cannot mount /home from the client (mseas).
Thanks.
Hi,
Just before the Thanksgiving break, we enabled quotas on the /home areas on the mseas-data server (running CentOS 5.8), using the following line in the updated /etc/fstab
/dev/mapper/the_raid-lv_home /home ext3 defaults,usrquota,grpquota 1 0
Following the Thanksgiving reboot of mseas-data we have been experiencing problems with svn on mseas (our front-end machine, running CentOS 6.2). After consulting with the svn mailing list, it appeared to be a communication issue between mseas and mseas-data. We therefore rebooted mseas. Now mseas is not mounting /home. We get the following error
[root@mseas etc]# mount mseas-data:/home mount.nfs: Unknown error 521
We have tried this mounting with both of the following lines in fstab and got the same error
mseas-data:/home /home nfs defaults 0 0
mseas-data:/home /home nfs defaults,usrquota,grpquota 0 0
(the latter was to mimic the mounting of /home on mseas-data)
The only thing we've found out on the web so far was advice on editting /etc/exports to have an "insecure" option for the export of /home, which we already had.
Any thoughts on how to resolve or debug this issue would be greatly appreciated.
By which NFS version are you exporting from the mseas-data server...v3 or v4?
If v3, you may have to add "vers=3" to the options section of your fstab. Try manually mounting with -o vers=3 in the command line to see if this fixes things.
Hi Mike,
I think v3 but I'm not sure (how do I check this?). At any rate, I tried your suggestion both ways
[root@mseas etc]# mount -o vers=3 mseas-data:/home mount.nfs: Unknown error 521
[root@mseas etc]# mount -o vers=4 mseas-data:/home mount.nfs: mounting mseas-data:/home failed, reason given by server: No such file or directory
What should I look at next?
Thanks.
Pat
Hi,
A quick follow-up. I tried reverting back to the set ups on both machines before we enabled quotas. Rebooted both machines. Still cannot mount /home from the client (mseas).
Thanks.
Hi,
Just before the Thanksgiving break, we enabled quotas on the /home areas on the mseas-data server (running CentOS 5.8), using the following line in the updated /etc/fstab
/dev/mapper/the_raid-lv_home /home ext3 defaults,usrquota,grpquota 1 0
Following the Thanksgiving reboot of mseas-data we have been experiencing problems with svn on mseas (our front-end machine, running CentOS 6.2). After consulting with the svn mailing list, it appeared to be a communication issue between mseas and mseas-data. We therefore rebooted mseas. Now mseas is not mounting /home. We get the following error
[root@mseas etc]# mount mseas-data:/home mount.nfs: Unknown error 521
We have tried this mounting with both of the following lines in fstab and got the same error
mseas-data:/home /home nfs defaults 0 0
mseas-data:/home /home nfs defaults,usrquota,grpquota 0 0
(the latter was to mimic the mounting of /home on mseas-data)
The only thing we've found out on the web so far was advice on editting /etc/exports to have an "insecure" option for the export of /home, which we already had.
Any thoughts on how to resolve or debug this issue would be greatly appreciated.
By which NFS version are you exporting from the mseas-data server...v3 or v4?
If v3, you may have to add "vers=3" to the options section of your fstab. Try manually mounting with -o vers=3 in the command line to see if this fixes things.
Hi Mike,
I think v3 but I'm not sure (how do I check this?). At any rate, I tried your suggestion both ways
[root@mseas etc]# mount -o vers=3 mseas-data:/home mount.nfs: Unknown error 521
[root@mseas etc]# mount -o vers=4 mseas-data:/home mount.nfs: mounting mseas-data:/home failed, reason given by server: No such file or directory
What should I look at next?
You appear to be missing the target mountpoint in your manual commands. It should probably look more like:
mount -o vers=3 mseas-data:/home /home
On the other hand, a Google search for "mount.nfs: Unknown error 521" turns up some interesting information:
https://www.google.com/search?q=mount.nfs+unknown+error+521&ie=utf-8&...
One of the items is a bug report from Fedora in which it turns out that the /etc/exports file has some sort of corruption (probably invalid characters) in it that was causing the NFS server system to not properly export the filesystem.
You may try, on the mseas-data system, to run "exportfs" to see what the system thinks it's exporting.
Hi Mike,
A colleague of mine did some hunting of his own and found that if he restarted nfs on the server (mseas-data) then the client was able to mount the disk.
Thank you very much for all of your time and help.
Pat
Hi Mike,
I think v3 but I'm not sure (how do I check this?). At any rate, I tried your suggestion both ways
[root@mseas etc]# mount -o vers=3 mseas-data:/home mount.nfs: Unknown error 521
[root@mseas etc]# mount -o vers=4 mseas-data:/home mount.nfs: mounting mseas-data:/home failed, reason given by server: No such file or directory
What should I look at next?
You appear to be missing the target mountpoint in your manual commands. It should probably look more like:
mount -o vers=3 mseas-data:/home /home
On the other hand, a Google search for "mount.nfs: Unknown error 521" turns up some interesting information:
https://www.google.com/search?q=mount.nfs+unknown+error+521&ie=utf-8&...
One of the items is a bug report from Fedora in which it turns out that the /etc/exports file has some sort of corruption (probably invalid characters) in it that was causing the NFS server system to not properly export the filesystem.
You may try, on the mseas-data system, to run "exportfs" to see what the system thinks it's exporting.
Mike Burger wrote: <snip>
Just before the Thanksgiving break, we enabled quotas on the /home areas on the mseas-data server (running CentOS 5.8), using the following line in the updated /etc/fstab
/dev/mapper/the_raid-lv_home /home ext3 defaults,usrquota,grpquota 1 0
Following the Thanksgiving reboot of mseas-data we have been experiencing problems with svn on mseas (our front-end machine, running CentOS 6.2). After consulting with the svn mailing list, it appeared to be a communication issue between mseas and mseas-data. We therefore rebooted mseas. Now mseas is not mounting /home. We get the following error
[root@mseas etc]# mount mseas-data:/home mount.nfs: Unknown error 521
We have tried this mounting with both of the following lines in fstab and got the same error
mseas-data:/home /home nfs defaults 0 0
mseas-data:/home /home nfs defaults,usrquota,grpquota 0 0
<snip>
By which NFS version are you exporting from the mseas-data server...v3 or v4?
If v3, you may have to add "vers=3" to the options section of your fstab. Try manually mounting with -o vers=3 in the command line to see if this fixes things.
Also, are any of the directories you want to mount ext4? I just had a problem the other week, where I had copied a line in /etc/fstab, and hadn't changed it to ext4 (it was a 3TB drive I'd added), and it wouldn't mount till I changed that.
mark
mark
-
Frank Cox -
m.roth＠5-cent.us -
Mike Burger -
Pat Haley