{"id":137935,"date":"2021-12-03T15:16:28","date_gmt":"2021-12-03T20:16:28","guid":{"rendered":"http:\/\/www.bu.edu\/tech\/?page_id=137935"},"modified":"2026-03-26T15:38:07","modified_gmt":"2026-03-26T19:38:07","slug":"file-system-structure","status":"publish","type":"page","link":"https:\/\/www.bu.edu\/tech\/support\/research\/system-usage\/using-file-system\/file-system-structure\/","title":{"rendered":"File System Structure"},"content":{"rendered":"<h2>Filesystem Structure<\/h2>\n<p>The Linux file system starts at the &#8220;<b>root<\/b>&#8221; (<code>\/<\/code>) and extends forward into directories that can contain both subdirectories and files. A series of descending directories can be strung together separated by forward slash characters &#8220;<code>\/<\/code>&#8221; to indicate a location on the filesystem. This string of folders is called a &#8220;<b>path<\/b>&#8221; and will look like <code class=\"inline-block\">\/project\/<span class=\"placeholder\">projectname<\/span>\/<span class=\"placeholder\">subfolder<\/span>\/<span class=\"placeholder\">file<\/span><\/code>.\u00a0 This path structure is much like those of other common operating systems. Below are the most common file storage locations you will use on the SCC.<\/p>\n<table border=\"0\">\n<tbody>\n<tr>\n<td><strong>Location<\/strong><\/td>\n<td><strong>Description<\/strong><\/td>\n<\/tr>\n<tr>\n<td><code>\/usr<span class=\"placeholder\">#<\/span>\/<span class=\"placeholder\">university_status<\/span>\/<span class=\"placeholder\">username<\/span><\/code> or <code>\/usr4\/<span class=\"placeholder\">coursename<\/span>\/<span class=\"placeholder\">username<\/span><\/code><\/td>\n<td>Each user has a &#8220;home directory,&#8221; this is the directory you are put in when you first log in each session. This will generally not be changed, even if your status changes or you are no longer in the course.<\/td>\n<\/tr>\n<tr>\n<td><code>\/project\/<span class=\"placeholder\">projectname<\/span><\/code><\/td>\n<td>Backed-up Project Disk Space. This is backed-up to another location each night.<\/td>\n<\/tr>\n<tr>\n<td><code>\/projectnb\/<span class=\"placeholder\">projectname<\/span><\/code><\/td>\n<td>Not backed-up (&#8220;nb&#8221;) Project Disk Space.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"highlight-yellow\">Note: For BUMC users with dbGaP or other confidential datasets, the <code>\/project\/<\/code> and <code>\/projectnb\/<\/code> shares are located in <code>\/restricted\/project\/<span class=\"placeholder\">project_name<\/span>\/<\/code> and <code>\/restricted\/projectnb\/<span class=\"placeholder\">project_name<\/span>\/<\/code>.<\/div>\n<h2><a name=\"DIRECTORIES\"><\/a>Places to Store Your Files<\/h2>\n<p>Users on the SCC are automatically granted several locations to store their files. Our overall <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/file-storage\/\">file storage system is described here<\/a>. Most users will be primarily storing files in three areas, all of which are generally accessible from all of the login and compute nodes; the exception is that the <code>\/restricted\/<\/code> partitions are only accessible from the <code><span class=\"command\">scc4.bu.edu<\/span><\/code> login node and all of the compute nodes. We have <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/file-storage\/proj-diskspace\/#BACKEDUPvsNOTBACKEDUP\">guidelines for what data should be stored in each partition<\/a>.<\/p>\n<ul>\n<li><b><a name=\"home_dir\"><\/a>Home Directory<\/b> &#8211; This directory is entirely controlled by you and the default permissions are that nobody else can see or otherwise access your files. Home directories have a quota of 10 GB and this will generally not be increased. You will naturally store files directly related to your account here, such as <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/system-usage\/scc-environment\/configuring-environment\/#DOTFILES\">dotfiles<\/a>. It is also commonly used to store personal files. Although it is possible to do work in your home directory if it fits within the 10GB limit, <b>we recommend<\/b> you use <b>Project Disk Space<\/b> in case you end up needing more space than you anticipate. Home directories are both protected by <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/file-storage\/#Snapshots\">Snapshots<\/a> and backed-up off-site.<\/li>\n<li><b><a name=\"proj_dir\"><\/a>Backed-Up Project Disk Space<\/b> &#8211; Projects are generally granted 200 GB of space under <code>\/project\/<span class=\"placeholder\">project_name<\/span>\/<\/code> (or <code>\/restricted\/project\/<span class=\"placeholder\">project_name<\/span>\/<\/code> for most BUMC projects) and that is the maximum space a project can have in this partition. This data is both protected by <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/file-storage\/#Snapshots\">Snapshots<\/a> and backed-up off-site. Depending on the workflow of the project, a reasonable approach is to keep code and files you hand-edit in <code>\/project\/<\/code> and files downloaded or generated by code or applications in <code>\/projectnb\/<\/code>.<\/li>\n<li style=\"padding-bottom: 10px;\"><b>Not Backed-Up Project Disk Space<\/b> &#8211; Projects are generally granted 800 GB of space under <code>\/projectnb\/<span class=\"placeholder\">project_name<\/span>\/<\/code> (or <code>\/restricted\/projectnb\/<span class=\"placeholder\">project_name<\/span>\/<\/code> for most BUMC projects). Additional Not Backed-Up space can be purchased through either <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/service-models\/buy-in\/\">Buy-In<\/a> or <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/file-storage\/proj-diskspace\/#SAAS\">Storage-as-a-Service<\/a>. Despite the name for this space, it is protected by both hardware RAID (protecting against disk failures) and daily <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/file-storage\/#Snapshots\">Snapshots<\/a> (protecting against accidental deletion of files). You will want to use this space for any large quantities of data you have.<\/li>\n<li>You can see which projects you belong to by running the command <code><span class=\"command\">groups<\/span><\/code> and see how much space each project has available and where by running <code><span class=\"command\">pquota<\/span><\/code>. Note that there are a few special groups like <b>gaussian<\/b> that do not have any disk space associated with them; <code><span class=\"command\">pquota<\/span><\/code> will tell you where you have disk space you can use. However, for those with space in <code>\/restricted\/project\/<\/code> or <code>\/restricted\/projectnb\/<\/code> <code><span class=\"command\">groups<\/span><\/code> will list the directories as <code>\/rproject\/<span class=\"placeholder\">project_name<\/span>\/<\/code> and <code>\/rproject\/<span class=\"placeholder\">project_name<\/span>\/<\/code> but you must type the full <code>\/restricted\/<span class=\"placeholder\">...<\/span><\/code> to access them.<\/li>\n<\/ul>\n<p>For those who need more than 200 GB of backed up space, there is also the option to use <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/file-storage#STASH\">Second Tier Ancillary Storage Heap (STASH) storage space<\/a> but you will need to maintain your own back-ups of the data to this space.<\/p>\n<h2>Temporary Storage using Scratch Disk Space<\/h2>\n<p>All SCC nodes have a fairly large local <code>\/scratch<\/code> directory that users can use for temporary storage of files. More details on this <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/file-storage\/#SCRATCH\">Scratch Space are available here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Filesystem Structure The Linux file system starts at the &#8220;root&#8221; (\/) and extends forward into directories that can contain both subdirectories and files. A series of descending directories can be strung together separated by forward slash characters &#8220;\/&#8221; to indicate a location on the filesystem. This string of folders is called a &#8220;path&#8221; and will&#8230;<\/p>\n","protected":false},"author":1692,"featured_media":0,"parent":137933,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/137935"}],"collection":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/users\/1692"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/comments?post=137935"}],"version-history":[{"count":22,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/137935\/revisions"}],"predecessor-version":[{"id":161351,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/137935\/revisions\/161351"}],"up":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/137933"}],"wp:attachment":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/media?parent=137935"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}