This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
en:navody:faq:start [20.06.2018 15:07] danecek@cesnet.cz [NFS] |
en:navody:faq:start [16.07.2019 13:19] danecek@cesnet.cz |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ~~TOC 2-4~~ | ||
====== FAQ - Frequently Asked Questions ====== | ====== FAQ - Frequently Asked Questions ====== | ||
Line 181: | Line 182: | ||
# mount -o sec=krb5i,proto=tcp,port=2049,intr storage-jihlava1-cerit.metacentrum.cz:/ /mnt/storage-cerit | # mount -o sec=krb5i,proto=tcp,port=2049,intr storage-jihlava1-cerit.metacentrum.cz:/ /mnt/storage-cerit | ||
# kswitch -p user@EINFRA | # kswitch -p user@EINFRA | ||
- | # mount -o rw,nfsvers=4,hard,intr,sec=krb5i nfs.du1.cesnet.cz:~/ /mnt/storage-du1 | + | # mount -o rw,nfsvers=4,hard,intr,sec=krb5i nfs.du4.cesnet.cz:~/ /mnt/storage-du4 |
</code> | </code> | ||
Line 196: | Line 197: | ||
<code>.du4.cesnet.cz = EINFRA-SERVICES</code> | <code>.du4.cesnet.cz = EINFRA-SERVICES</code> | ||
+ | === Issue with connecting NFS via Kerberos ticket === | ||
+ | __Problem description:__ | ||
+ | I tried to connect via NFS protocol, but I've got following error report. | ||
+ | <code>mount.nfs: Network is unreachable</code> | ||
+ | |||
+ | __Solution:__ | ||
+ | The issue is caused by failed startup **rpc-gssd** service, see the service status: | ||
+ | <code>systemctl status rpc-gssd</code> | ||
+ | <code>Condition: start condition failed at Thu 2018-05-06 06:12:22 CET; 20s ago | ||
+ | └─ ConditionPathExists=/etc/krb5.keytab was not met</code> | ||
+ | |||
+ | To resolve this issue, you can create empty file in the /etc folder via following command: | ||
+ | <code>touch /etc/krb5.keytab</code> | ||
+ | |||
+ | Now you can restart **rpc-gssd** service and remount your storage. | ||
==== FileSender ==== | ==== FileSender ==== | ||
Line 276: | Line 292: | ||
Based on new Terms of Service that are in effect from January 2018, the system of handling data on storage facilities has been changed in order to prevent the facilities to get full. The data has been classified into two categories, permanent archives and backups. | Based on new Terms of Service that are in effect from January 2018, the system of handling data on storage facilities has been changed in order to prevent the facilities to get full. The data has been classified into two categories, permanent archives and backups. | ||
- | **The system is applied to storage facilities put into operation since 2018. It doesn't affect storage facilities du1, du2, and du3 where all data is considered to be a permanent archive.** | + | **The system is applied to storage facilities put into operation since 2018. It doesn't affect storage facilities du2, and du3 where all data is considered to be a permanent archive.** |
Line 325: | Line 341: | ||
<code>Error (transfer) | <code>Error (transfer) | ||
Endpoint: ducesnet#globusonline (d8eb370a-6d04-11e5-ba46-22000b92c6ec) | Endpoint: ducesnet#globusonline (d8eb370a-6d04-11e5-ba46-22000b92c6ec) | ||
- | Server: globus.du1.cesnet.cz:2811 | + | Server: globus.du4.cesnet.cz:2811 |
File: /~/VO_storage-cache_tape/backups/tests/fLLgaxLv2R1/4Hcy5vd98A0 | File: /~/VO_storage-cache_tape/backups/tests/fLLgaxLv2R1/4Hcy5vd98A0 | ||
Command: RETR ~/VO_storage-cache_tape/backups/tests/fLLgaxLv2R1/4Hcy5vd98A0 | Command: RETR ~/VO_storage-cache_tape/backups/tests/fLLgaxLv2R1/4Hcy5vd98A0 | ||
Line 342: | Line 358: | ||
Please connect to the data storage using ssh protocol. | Please connect to the data storage using ssh protocol. | ||
- | <code>ssh username@ssh.du1.cesnet.cz</code> | + | <code>ssh username@ssh.du4.cesnet.cz</code> |
Now go to the directory, which you wish to check. Here is obvious which files are causing the issue. It is **test1 a testfile1**. | Now go to the directory, which you wish to check. Here is obvious which files are causing the issue. It is **test1 a testfile1**. |