UBFS: Difference between revisions

From CCN Wiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
The good people at UBIT have provided us with a 1TB network folder and allow specified UB users to be able to access this network folder. In The Before Times, there used to be a ubfs folder in your home directory that you needed to manually mount. This is no longer the case, so if you're just returning to the lab after an extended vacation, you will find our shared drive in the /ubfs/ folder:


== '''UBFS''' ==
cd /ubfs/caset/cpmcnorg/


The UBFS folder in your home directory contains data and lots of other goodies you may need to access at some point. The good people at UBIT grant permissions to specified UB users to be able to access this network folder.
Also, your own network folder can be found in:
cd /ubfs/myfiles/


If you do not have a UBFS folder in your home directory, one will be created for you automatically by running the <code>ubmount.sh</code> script. This script sends the UBIT fileserver all the information it needs in order to grant you access to the drive. However, this script also requires you to provide it with a few parameters, which we store in a file called <code>ubfs.keys</code> that sits in your home directory in a place that only you can see it.
=Possible Problems=
 
==I Can't Access the Shared Folder!==
=== Creating a ubfs.keys configuration file ===
Access to /ubfs/caset/ uses Kerberos authentication of your UBIT credentials. When you log in to the workstation, you get a temporary authentication token that's good for a short period of time -- 24 hours or so, I think. If you log in to the workstation and leave the session open for an extended period to run a process (e.g., running data preprocessing over the weekend), then your access token will have expired by the time you log back in (your session will have been idle, but not terminated). If that's the case, you won't be able to access the ubfs folder.
Open a terminal (ctrl-alt-T).
Fortunately, the fix for this problem is easy: log out and log back in. This generates a new authentication token.
Move to the .config directory
cd ~/.config 
Check that the ubfs.keys file exists
touch ubfs.keys
Open the file to edit
nano ubfs.keys
 
In the ubfs.keys file add the following:
username=''YourUBname''
password=''YourUBpassword''
domain=AD
 
Push ctrl-o to save, enter, and ctrl-x to exit. Your ubfs.keys file is now correctly configured for this computer (you will have to do this on each computer you work on).
 
===Using ubmount.sh to mount the ubfs directory===
Is your ~/ubfs folder empty (or nonexistent)? Well guess what, you need to mount (or remount) it!
 
Just open up your Terminal (ctrl-alt-T) and run the command:
ubmount.sh
 
Your UBFS folder should be good as new!
 
If not, we've got a bit more to add to this wikipage.
==What am I looking for?==
After it has been mounted, your ~/ubfs folder will contain several dozen directories, only one of which contains our files. You will be looking for the following subdirectory:
~/ubfs/cpmcnorg/
This folder contains many subdirectories of useful resources and is where we plan to store all of our raw fMRI data (for the time being, at least)

Latest revision as of 13:53, 25 May 2021

The good people at UBIT have provided us with a 1TB network folder and allow specified UB users to be able to access this network folder. In The Before Times, there used to be a ubfs folder in your home directory that you needed to manually mount. This is no longer the case, so if you're just returning to the lab after an extended vacation, you will find our shared drive in the /ubfs/ folder: 

cd /ubfs/caset/cpmcnorg/

Also, your own network folder can be found in: 

cd /ubfs/myfiles/

Possible Problems

I Can't Access the Shared Folder!

Access to /ubfs/caset/ uses Kerberos authentication of your UBIT credentials. When you log in to the workstation, you get a temporary authentication token that's good for a short period of time -- 24 hours or so, I think. If you log in to the workstation and leave the session open for an extended period to run a process (e.g., running data preprocessing over the weekend), then your access token will have expired by the time you log back in (your session will have been idle, but not terminated). If that's the case, you won't be able to access the ubfs folder. Fortunately, the fix for this problem is easy: log out and log back in. This generates a new authentication token.

Retrieved from "https://ccn-wiki.caset.buffalo.edu/index.php?title=UBFS&oldid=2171"