This is an old revision of the document!
NB, part of the following instructions come from 1).
NB, this originates from 2).
First of all, which snapshots do we keep?
Then, how to access them?
File Explorer
: Properties → Previous Versions
.snapshot
hidden folderNB, this originates from 3).
For anti-ransomware reasons, we also have a backup on tape of each NAS share, thus completely independent from the NAS infrastructure.
Some notes:
Then, how to access them?
NB, the following instructions come from 4)
If you need to synchronize data to another folder, you can let `rsync` 3.1.0+ saves in the log file the MD5 checksum of any transferred file (cf. https://stackoverflow.com/questions/29624524/how-can-i-print-log-the-checksum-calculated-by-rsync#45053057):
$ rsync \ --log-file=/path/to/file.log \ --log-file-format="%C %f" \ [...] \ "${SOURCE_FOLDER}" \ "${TARGET_FOLDER}" $ grep -e "${SOURCE_FOLDER}" /path/to/file.log | \ cut -c 29- | \ awk '{if ($2 != "") {print $0}}' | \ sed -e "s, ${SOURCE_FOLDER}/, ,g" \ >"/path/to/${SOURCE_FOLDER}.md5" $ cd "${TARGET_FOLDER}" $ md5sum -c "/path/to/${SOURCE_FOLDER}.md5"
TreeSize est lancé sur certains share de manière périodique.
NB, this partly originate from 5).
Lorsqu'un partage a été crée et que votre CI vous a donné les droits d'accès, suivez la procédure ci-dessous pour vous connecter à votre partage. A noter que pour vous connecter à un partage depuis l'extérieur de l'université, vous devez configurer et lancer votre VPN. Veuillez vous référer à la documentation du VPN de l'unige pour ce faire.
ug-nas-test-smb-browsing.sh
script!
NB, this originates from 6) 7)
Les produits Adobe sont de plus en plus “strictes” par rapport aux disques réseaux :
First of all, you need to mount the share root (thus, not a super/sub-folder).
Then
File Explorer
: General → Capacity
df -h /path/to/the/mounted/share
NB, part of the following instructions come from 8).
Here the commands to get the list of all the shares you have access on a specific server:
PS C:\WINDOWS\system32> net view \\nasac-faculty.unige.ch /all | Select-String Disk [...] PS C:\WINDOWS\system32> (net view \\nasac-faculty.unige.ch /all | Select-String Disk).length 107 PS C:\WINDOWS\system32>
'smbclient -L
' does not allow “grep-piping” if interactive! capello@harlock:~$ smbclient -L nasac-faculty.unige.ch -W ISIS -U capello Enter ISIS\capello's password: Sharename Type Comment --------- ---- ------- [...] SMB1 disabled -- no workgroup available capello@harlock:~$ cat <<EOF >~/.smbclient username = capello password = ${ISIS} domain = ISIs EOF capello@harlock:~$ smbclient -L nasac-faculty.unige.ch -W ISIS -A ~/.smbclient | grep -c Disk 107 capello@harlock:~$
La procédure est sensiblement la même pour d'autres variantes de Linux.
mount
command, which however requires superuser privileges: root@harlock:~# findmnt /mnt root@harlock:~# mount \ -t cifs \ -o vers=3,sec=ntlmsspi,domainauto,username=capello \ //nasac-faculty.isis.unige.ch/ADM_HOME/DISTIC/capello \ /mnt/ Password for capello@//nasac-faculty.isis.unige.ch/ADM_HOME/DISTIC/capello: root@harlock:~# findmnt /mnt TARGET SOURCE FSTYPE OPTIONS /mnt //nasac-faculty.isis.unige.ch/ADM_HOME/DISTIC/capello cifs rw,relatime,vers=3,sec=ntlmsspi,cache=strict,username=capello,domain=ISIS,uid=0,noforceuid,gid=0,noforcegi root@harlock:~#
capello@harlock:~$ gio mount smb://nasac-faculty.isis.unige.ch/ADM_HOME/DISTIC/capello Password required for share adm_home on nasac-faculty.isis.unige.ch User [capello]: Domain [WORKGROUP]: ISIs Password: capello@harlock:~$ ls -l /run/user/$(id -u)/gvfs/ total 2 drwx------ 1 capello capello 2048 Nov 30 11:50 smb-share:server=nasac-faculty.isis.unige.ch,share=adm_home capello@harlock:~$
Se connecter à un serveur:
Choisir l'ip ou le nom de votre EVS (transmis par votre CI):
Entrer vos identifiants ISIS:
NB , the following instructions come from <https://gitlab.unige.ch/prods/ies/recherche/hpc/issues/925>
SMB3+ requires packet signing, thus if you encounter the following error…
CIFS VFS: validate protocol negotiate failed: -13 CIFS VFS: failed to connect to IPC (rc=-5) CIFS VFS: validate protocol negotiate failed: -13 CIFS VFS: session ffff962f7cd42400 has no tcon available for a dfs referral request CIFS VFS: cifs_mount failed w/return code = -5
…you have to specify that you want packet signing via a mount option, either sec=ntlmsspi (preferred) or sec=ntlmv2.
NB , the following instructions come from <https://gitlab.unige.ch/prods/ies/recherche/hpc/issues/873>
Starting from Windows 10, symlinks (AKA symbolic links) are fully supported (cf. https://blogs.windows.com/windowsdeveloper/2016/12/02/symlinks-windows-10/ ). However, while Linux can make use of symlinks on a SMB share created on Windows 10, there is no way to create them on Linux.
On the other hand, Linux-only symlinks on SMB shares are still possible, no more via the SMB1-only CIFS Unix Extensions (cf. https://www.samba.org/samba/CIFS_POSIX_extensions.html ), but via the new SMB3 POSIX Extensions (cf. https://wiki.samba.org/index.php/SMB3-Linux#Symbolic_links ).
Specyfing the mount option mfsymlinks will allow symlink creation on Linux using the Minshall+French file format, which means that they will be seen on Windows as a plain text file (cf. https://wiki.samba.org/index.php/UNIX_Extensions#Storing_symlinks_on_Windows_servers ).
ATTENTION , while the mount option mfsymlinks is available from SMB2+, it is preferable to use it together with SMB3+ (see Linux and SMB3+).
Connectez un lecteur réseau pour y accéder à partir de l’Explorateur de fichiers dans Windows sans avoir à le rechercher ou à saisir son adresse réseau à chaque fois.
Sélection du disque et du nom du partage:
Saisie de vos identifiants ISIS:
NB, this originates from 10) 11) 12)
If you still get connection refused messages and you are sure your ISIs credentials are right, the IP address your computer got could have been blacklisted in the last 15 minutes on the NAS side because of too many SMB NTLM authentication failures.
Here how to find out if you are impacted:
Start → PowerShell → ipconfig → IPv4 Address
Applications → Terminal → ifconfig | grep -e “inet ”
Applications → Terminal → ip addr show | grep -e “inet ”
NB, part of the following instructions come from 13).
You must set the access rights directly from Windows, please check the “Affectation des droits” paragraph in the “Gestion des postes de travail avec l'Active Directory (AD)” guide available on Plone.
smbcacls
(usually shipped by the smbclient
package)!
If you are encountering network errors when copying a gvfs mount, you should use a tool dedicated to network copy such as rsync, gio copy or scp.
When copying CIFS data from and to linux using Rsync, you can use this rsync example
rsync --partial --stats --progress –A –a –r –v --no-perms src dest
NB , the following instructions come from <https://gitlab.unige.ch/prods/ies/recherche/hpc/issues/716>
Nowadays most of the GNU/Linux distribution defaults to NFSv4, which is a big step forward and differs quite a lot from NFSv3 (cf. http://www.citi.umich.edu/projects/nfsv4/ ). One of the main advantages of NFSv4 is the ACLs support into the protocol itself (cf. http://wiki.linux-nfs.org/wiki/index.php/ACLs ), ACLs that resemble very much the Windows ones.
The NASAC, being based on a Unix system, natively supports NFSv4 ACLs. Actually, given that it is connected to the UniGE's Active Directory, the NFSv4 ACLs are the same as the Windows ones.
Here the instructions to manage the NFSv4 ACLs for a share: