UBFS - Revision history

Chris at 18:53, 25 May 2021

2021-05-25T18:53:23Z

← Older revision		Revision as of 14:53, 25 May 2021
Line 5:		Line 5:
	Also, your own network folder can be found in:		Also, your own network folder can be found in:
	cd /ubfs/myfiles/		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.

Chris at 18:10, 25 May 2021

2021-05-25T18:10:53Z

@@ Line 1: / Line 1: @@
-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.
+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:
-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.
+ cd /ubfs/caset/cpmcnorg/
-== Creating a ubfs.keys configuration file ==
+Also, your own network folder can be found in:
-Open a terminal (ctrl-alt-T).
+  cd /ubfs/myfiles/

Chris: /* What am I looking for? */

2018-12-06T20:15:27Z

What am I looking for?

← Older revision		Revision as of 16:15, 6 December 2018
Line 38:		Line 38:
	~/ubfs/		~/ubfs/
	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)		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)
	Note that prior to December 2018, the ~/ubfs/ folder would contain a pile of other irrelevant folders, and we were navigating to ~/ubfs/cpmcnorg/. Changes to the remote fileserver now have us directly mounting the cpmcnorg subdirectory, so we no longer have to navigate to our subdirectory. This might affect some scripts (like <code>update_scripts.sh</code> that were written prior to this change.		Note that prior to December 2018, the ~/ubfs/ folder would contain a pile of other irrelevant folders, and we were navigating to ~/ubfs/cpmcnorg/. Changes to the remote fileserver now have us directly mounting the cpmcnorg subdirectory, so we no longer have to navigate to our subdirectory. This might affect some scripts (like <code>update_scripts.sh</code>) that were written prior to this change.

	== Mounting Errors ==		== Mounting Errors ==

Chris: /* What am I looking for? */

2018-12-06T20:15:12Z

What am I looking for?

← Older revision		Revision as of 16:15, 6 December 2018
Line 36:		Line 36:
	==What am I looking for?==		==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:		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~~/		~/ubfs/
	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)		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)
			Note that prior to December 2018, the ~/ubfs/ folder would contain a pile of other irrelevant folders, and we were navigating to ~/ubfs/cpmcnorg/. Changes to the remote fileserver now have us directly mounting the cpmcnorg subdirectory, so we no longer have to navigate to our subdirectory. This might affect some scripts (like <code>update_scripts.sh</code> that were written prior to this change.

	== Mounting Errors ==		== Mounting Errors ==

Chris: /* Creating a ubfs.keys configuration file */

2018-06-05T16:02:59Z

Creating a ubfs.keys configuration file

← Older revision		Revision as of 12:02, 5 June 2018
Line 19:		Line 19:
	Of course, you need to replace '''YourUBname''' and '''YourUBpassword''' with your actual UBIT name and password (the same info you would use to log into any UB computer system, including your email).		Of course, you need to replace '''YourUBname''' and '''YourUBpassword''' with your actual UBIT name and password (the same info you would use to log into any UB computer system, including your email).

	'''Note:''' when the ubfs.keys credential file is parsed by the ubmount.sh command, the parser pays attention to ''every single character'', even whitespaces. Naturally, whitespace doesn't show up at all in the text editor -- the only clue that it's there is that there will be space at the end of the printable characters and the cursor. Make sure you don't have any unintended whitespace in your ubfs.keys file, ~~because~~ these whitespace characters will be assumed to be part of your username or password, which is probably not correct, and will lead to puzzling "permission denied" errors, as when there are trailing spaces in the example below (highlighted in gray for visibility):		'''Note:''' when the ubfs.keys credential file is parsed by the ubmount.sh command, the parser pays attention to ''every single character'', even whitespaces. Naturally, whitespace doesn't show up at all in the text editor -- the only clue that it's there is that there will be space at the end of the printable characters and the cursor. Make sure you don't have any unintended whitespace in your ubfs.keys file. If there are, these whitespace characters will be assumed to be part of your username or password (which is probably not correct) and will lead to puzzling "permission denied" errors, as when there are trailing spaces in the example below (highlighted in gray for visibility):

	username=joeshmoe<span style="background:#c0c0c0"> </span>		username=joeshmoe<span style="background:#c0c0c0"> </span>

Chris: /* Creating a ubfs.keys configuration file */

2018-06-05T15:42:52Z

Creating a ubfs.keys configuration file

← Older revision		Revision as of 11:42, 5 June 2018
Line 19:		Line 19:
	Of course, you need to replace '''YourUBname''' and '''YourUBpassword''' with your actual UBIT name and password (the same info you would use to log into any UB computer system, including your email).		Of course, you need to replace '''YourUBname''' and '''YourUBpassword''' with your actual UBIT name and password (the same info you would use to log into any UB computer system, including your email).

	'''Note:''' when the ubfs.keys credential file is parsed by the ubmount.sh command, the parser pays attention to ''every single character'', even whitespaces. Naturally, whitespace doesn't show up at all in the text editor -- the only clue that it's there is that there will be space at the end of the printable characters and the cursor. Make sure you don't have any unintended whitespace in your ubfs.keys file, because these whitespace characters will be assumed to be part of your username or password, which is probably not correct, and will lead to puzzling "permission denied" errors.		'''Note:''' when the ubfs.keys credential file is parsed by the ubmount.sh command, the parser pays attention to ''every single character'', even whitespaces. Naturally, whitespace doesn't show up at all in the text editor -- the only clue that it's there is that there will be space at the end of the printable characters and the cursor. Make sure you don't have any unintended whitespace in your ubfs.keys file, because these whitespace characters will be assumed to be part of your username or password, which is probably not correct, and will lead to puzzling "permission denied" errors, as when there are trailing spaces in the example below (highlighted in gray for visibility):

			username=joeshmoe<span style="background:#c0c0c0"> </span>
			password=mypassword<span style="background:#c0c0c0"> </span>
			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).		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).

Chris: /* Creating a ubfs.keys configuration file */

2018-06-05T15:37:23Z

Creating a ubfs.keys configuration file

← Older revision		Revision as of 11:37, 5 June 2018
Line 17:		Line 17:
	domain=AD		domain=AD

	Of course you need to replace '''YourUBname''' and '''YourUBpassword''' with your actual UBIT name and password (the same info you would use to log into any UB computer system, including your email).		Of course, you need to replace '''YourUBname''' and '''YourUBpassword''' with your actual UBIT name and password (the same info you would use to log into any UB computer system, including your email).

			'''Note:''' when the ubfs.keys credential file is parsed by the ubmount.sh command, the parser pays attention to ''every single character'', even whitespaces. Naturally, whitespace doesn't show up at all in the text editor -- the only clue that it's there is that there will be space at the end of the printable characters and the cursor. Make sure you don't have any unintended whitespace in your ubfs.keys file, because these whitespace characters will be assumed to be part of your username or password, which is probably not correct, and will lead to puzzling "permission denied" errors.

	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).		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).

108.168.1.253: /* Creating a ubfs.keys configuration file */

2017-06-15T20:04:13Z

Creating a ubfs.keys configuration file

← Older revision		Revision as of 16:04, 15 June 2017
Line 7:		Line 7:
	Move to the .config directory		Move to the .config directory
	cd ~/.config		cd ~/.config
	Check that the ubfs.keys file exists		Check that the ubfs.keys file exists (when you execute the <code>touch</code> command, if the file exists, the Last Accessed timestamp gets updated but nothing special otherwise happens. If the file doesn't exist, then it is automatically created).
	touch ubfs.keys		touch ubfs.keys
	Open the file to edit		Open the file to edit
Line 16:		Line 16:
	password=''YourUBpassword''		password=''YourUBpassword''
	domain=AD		domain=AD

			Of course you need to replace '''YourUBname''' and '''YourUBpassword''' with your actual UBIT name and password (the same info you would use to log into any UB computer system, including your email).

	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).		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).

192.168.1.1: /* UBFS Down */

2016-08-04T16:48:40Z

UBFS Down

← Older revision		Revision as of 12:48, 4 August 2016
Line 35:		Line 35:
	===Permission Denied===		===Permission Denied===
	Especially for new lab members, it is possible that you were not added to the '''lab''' group of users on a particular machine (or else if you were, that you had not logged out since that time). Check with a system administrator to see if you are part of the '''lab''' group, and ask to be added if not. If you are part of that group, try logging out and logging back in again.		Especially for new lab members, it is possible that you were not added to the '''lab''' group of users on a particular machine (or else if you were, that you had not logged out since that time). Check with a system administrator to see if you are part of the '''lab''' group, and ask to be added if not. If you are part of that group, try logging out and logging back in again.
	===UBFS ~~Down~~===		===UBFS Unavailable===
	When you run <code>ubmount.sh</code> you will get an <code>Input/Output Error</code> message if there is some sort of network problem at the UBIT end of things. This is out of our control, but you can check on the status of the UBFS system at the following website before bugging the UBIT people about a problem they are already working on:		When you run <code>ubmount.sh</code> you will get an <code>Input/Output Error</code> message if there is some sort of network problem at the UBIT end of things. This is out of our control, but you can check on the status of the UBFS system at the following website before bugging the UBIT people about a problem they are already working on:
	[http://www.buffalo.edu/content/www/ubit/news/alerts.html/ UBIT Alerts]		[http://www.buffalo.edu/content/www/ubit/news/alerts.html/ UBIT Alerts]
			Look for an alert with the heading '''UBFS Unavailable''' or something similar. If such an alert exists, just hang tight until it gets resolved. If not, ask a system administrator to file a ticket with the CASEIT group.

192.168.1.1 at 16:46, 4 August 2016

2016-08-04T16:46:58Z

← Older revision		Revision as of 12:46, 4 August 2016
Line 1:		Line 1:

	~~== UBFS ==~~

	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.		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.

	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.		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.

	=== Creating a ubfs.keys configuration file ===		== Creating a ubfs.keys configuration file ==
	Open a terminal (ctrl-alt-T).		Open a terminal (ctrl-alt-T).
	Move to the .config directory		Move to the .config directory
Line 22:		Line 19:
	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).		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===		== 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!		Is your ~/ubfs folder empty (or nonexistent)? Well guess what, you need to mount (or remount) it!

Line 28:		Line 25:
	ubmount.sh		ubmount.sh

	Your UBFS folder should be good as new!		Your UBFS folder should be good as new! If not, see below

	~~If not, we've got a bit more to add to this wikipage.~~
	==What am I looking for?==		==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:		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/		~/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)		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)

			== Mounting Errors ==
			===Permission Denied===
			Especially for new lab members, it is possible that you were not added to the '''lab''' group of users on a particular machine (or else if you were, that you had not logged out since that time). Check with a system administrator to see if you are part of the '''lab''' group, and ask to be added if not. If you are part of that group, try logging out and logging back in again.
			===UBFS Down===
			When you run <code>ubmount.sh</code> you will get an <code>Input/Output Error</code> message if there is some sort of network problem at the UBIT end of things. This is out of our control, but you can check on the status of the UBFS system at the following website before bugging the UBIT people about a problem they are already working on:
			[http://www.buffalo.edu/content/www/ubit/news/alerts.html/ UBIT Alerts]