Skip to end of metadata
Go to start of metadata

Research Data Facility User's Guide

The Research Data Facility (RDF) is a network storage appliance which can be accessed as a network share from Windows, MacOS, or Linux systems using the SMB file sharing protocol.   The RDF also supports NFSv3, for Unix/Linux clients which have been granted access to specially configured NFS shares.  The RDF does not support both SMB and NFS for the same data shares.

For instructions on how to map your SMB share, see the section for your operating system below.





1) Launch Windows Explorer (File Explorer in Windows 10)

2) Select Network->Map Network Drive

Right-click on the Network icon and select "Map Network Drive":

3) Select mapping options

Select the desired local drive mapping (i.e., Z:). 

In the Folder dialog box, enter \\\research

If you are working on a Windows system which is bound to Rice Active Directory (ADRICE), you provided your credentials at login.  Click “Finish” and you will see the RDF drive available in the Windows File Explorer.

If your Windows system is *not* bound to Active Directory, you will be prompted for Active Directory, you must select “Connect using different credentials”, then click “Finish”.

You will be prompted for a username and password.  Enter ADRICE\<yournetid> and provide your password when prompted. 

You should now see the RDF research share available in the Windows File Explorer.

4) To disconnect, right-click the drive in the Windows File Explorer and select the “Disconnect” option.



1) From the Finder, select Go->Connect to Server

2) In the Server Address field in the Connect to Server dialog box, enter


Then click the Connect button.

3) You will be asked to provide your NetID and NetID password in the Name and Password fields.  Be sure that Registered User is selected, then click Connect.

You will now see the RDF drive available to use in the Finder window.

4) To disconnect, click the eject button to the right of the drive share icon in Finder.

Linux (Ubuntu/CENTOS/Redhat)

Most Linux distributions do not allow non-privileged users to execute mount commands.  A user with sudo privileges can use the following procedure to mount their RDF SMB share from a Linux client.  For non-privileged users without sudo access, please see the procedure following step 3 below.

Please make note of the following mount options used in the examples below:

        username: should be the NetID of the mounting user

        domain: should be ADRICE

        mfsymlinks: this option allows symlinks to work consistent with POSIX filesystem behavior on a CIFS based filesystem

        rw: grant read/write access to the user mounting the share

        vers=3.0:  The RDF does not support lower CIFS/SMB version standards.  Linux mount.cifs will default to the lowest version so this parameter is required

        sign: Request packet signing from the server.  The RDF requires this parameter for a secure connection.

        uid: should match the local POSIX userid number of the mounting user

        gid: should match the local POSIX groupid number of the mounting user


1) Make sure cifs-utils is installed


sudo yum install cifs-utils


sudo apt-get install cifs-utils


2) Create the mount point

[heider@ancalagon ~]$ mkdir $HOME/mymount

Issue the mount command and passwords (including sudo password if required)

[heider@ancalagon ~]$ sudo mount.cifs -o username=heider,domain=ADRICE,mfsymlinks,rw,vers=3.0,sign,uid=1000,gid=1000 // $HOME/mymount

[sudo] password for heider:
Password for heider@//  ********

You can use the df command to check to make sure the mount is active:

[heider@ancalagon ~]$ df -h $HOME/mymount
Filesystem                   Size  Used Avail Use% Mounted on
//  600T  341T  260T  57% /home/heider/mymount

Now you can use the filesystem

[heider@ancalagon ~]$ ls -l $HOME/mymount/heider
total 0
drwxr-xr-x. 2 heider heider 0 Nov  1 12:29 data
[heider@ancalagon ~]$ cd $HOME/mymount/heider
[heider@ancalagon heider]$ mkdir data2
[heider@ancalagon heider]$ ls -l
total 0
drwxr-xr-x. 2 heider heider 0 Nov  1 12:29 data
drwxr-xr-x. 2 heider heider 0 Nov  1 12:31 data2

3)  To unmount the filesystem, be sure you do not have any active processes using the share, then type:

[heider@ancalagon ~]$ sudo umount $HOME/mymount

You can use df again to verify the share is unmounted (note that the mount directory now just appears as a local filesystem)

[heider@ancalagon ~]$ df -h $HOME/mymount
Filesystem                       Size  Used Avail Use% Mounted on
/dev/mapper/rhel_ancalagon-home  178G  3.7G  165G   3% /home


Preconfigured Mount Point

The following procedure will configure a Linux client to allow a non-root user to access their RDF share from user space with a more convenient mount command, assuming that the user's local POSIX username matches their NetID.  Administrative access to the client system is required to complete steps 1-4, at which time /rdf will be mountable by a non-root user.

1) Make sure cifs-utils is installed


sudo yum install cifs-utils


sudo apt-get install cifs-utils

2) Change permissions to allow non-root users to execute mount commands

sudo chmod u+s /bin/mount /usr/sbin/mount.cifs

3) Create mount point

sudo mkdir /rdf

4) As a privileged user, edit the file /etc/fstab using your editor of choice, adding the following line:

// /rdf cifs nounix,mfsymlinks,rw,vers=3.0,sign,noperm,domain=ADRICE,user,noauto 0 0

5) At this point, a user of the system without root privilege should be able to execute a mount command, provide their NetID password, and be able to access the share locally at /rdf:

[heider@ancalagon /]$ mount /rdf
Password for heider@//  ********
[heider@ancalagon /]$ df -k /rdf
Filesystem                     1K-blocks         Used    Available Use% Mounted on
// 644245094400 333210730200 311034364200  52% /rdf

scp smb RDF issue 2019-01-09

At this time we are investigating an issue where a workstation mouting RDF via SMB and a server with remote data copied via scp will receive an "Input/Output" error with files larger than 9.9GB.

Workaround: Use rsync via ssh instead.

We have contacted our vendor and are investigating.