CS 1550 – Project 4: File Systems
Directories
Due: Sunday, April 12, 2015, 11:59pm
Completed Due: Sunday,
April 19, 2015, 11:59pm
FUSE (http://fuse.sourceforge.net/) is a Linux kernel extension that allows for a user space program to provide the implementations for the various file-related syscalls. We will be using FUSE to create our own file system, managed via a single file that represents our disk device. Through FUSE and our implementation, it will be possible to interact with our newly created file system using standard UNIX/Linux programs in a transparent way.
From a user interface perspective, our file system will be a two level directory system, with the following restrictions/simplifications:
From an implementation perspective, the file system will keep data on “disk” via a linked list allocation strategy, outlined below.
FUSE consists of two major components: A kernel module that has already been installed, and a set of libraries and example programs that you need to install.
First, copy the source code to your /u/OSLab/USERNAME directory
cd /u/OSLab/USERNAME
cp /u/OSLab/original/fuse-2.7.0.tar.gz .
tar xvfz fuse-2.7.0.tar.gz
cd fuse-2.7.0
Now, we do the normal configure, compile, install procedure on UNIX, but omit the install step since that needs to be done as a superuser and has already been done.
./configure
make
(The third step would be make install, but if you try it, you will be met with many access denied errors.)
Let us now walk through one of the examples. Enter the following:
cd /u/OSLab/USERNAME/
cd fuse-2.7.0/examples
mkdir testmount
ls -al testmount
./hello testmount
ls -al testmount
You should see 3 entries: ., .., and hello. We just created this directory, and thus it was empty, so where did hello come from? Obviously the hello application we just ran could have created it, but what it actually did was lie to the operating system when the OS asked for the contents of that directory. So let’s see what happens when we try to display the contents of the file.
cat testmount/hello
You should get the familiar hello world quotation. If we cat a file that doesn’t really exist, how do we get meaningful output? The answer comes from the fact that the hello application also gets notified of the attempt to read and open the fictional file “hello” and thus can return the data as if it was really there.
Examine the contents of hello.c in your favorite text editor, and look at the implementations of readdir and read to see that it is just returning hard coded data back to the system.
The final thing we always need to do is to unmount the file system we just used when we are done or need to make changes to the program. Do so by:
fusermount -u testmount
The hello application we ran in the above example is a particular FUSE file system provided as a sample to demonstrate a few of the main ideas behind FUSE. The first thing we did was to create an empty directory to serve as a mount point. A mount point is a location in the UNIX hierarchical file system where a new device or file system is located. As an analogy, in Windows, “My Computer” is the mount point for your hard disks and CD-ROMs, and if you insert a USB drive or MP3 player, it will show up there as well. In UNIX, we can have mount points at any location in the file system tree.
Running the hello application and passing it the location of where we want the new file system mounted initiates FUSE and tells the kernel that any file operations that occur under our now mounted directory will be handled via FUSE and the hello application. When we are done using this file system, we simply tell the OS that it no longer is mounted by issuing the above fusermount -u command. At that point the OS goes back to managing that directory by itself.
Your job is to create the cs1550 file system as a FUSE application that provides the interface described in the first section. A code skeleton has been provided under the examples directory as cs1550.c. It is automatically built when you type make in the examples directory.
The cs1550 file system should be implemented using a single file, managed by the real file system in the directory that contains the cs1550 application. This file should keep track of the directories and the file data. We will consider the disk to have 512 byte blocks.
In order to manage the free or empty space, you will need to create bookkeeping block(s) in .disk that records what blocks have been previously allocated or not. Use a bitmap as we have discussed in class.
To create a 5MB disk image, execute the following:
dd bs=1K count=5K if=/dev/zero of=.disk
This will create a file initialized to contain all zeros, named .disk. You only need to do this once, or every time you want to completely destroy the disk. (This is our “format” command.)
Since the disk contains blocks that are directories and blocks that are file data, we need to be able to find and identify what a particular block represents. In our file system, the root only contains other directories, so we will use block 0 of .disk to hold the directory entry of the root and, from there, find our subdirectories.
The root directory entry will be a struct defined as below (the actual one we provide in the code has additional attributes and padding to force the structure to be 512 bytes):
struct cs1550_root_directory
{
int nDirectories; //How many subdirectories are in the root
//Needs to be less than MAX_DIRS_IN_ROOT
struct cs1550_directory
{
char dname[MAX_FILENAME + 1]; //directory name (plus space for nul)
long nStartBlock; //where the directory block is on disk
} directories[MAX_DIRS_IN_ROOT]; //There is an array of these
} ;
Since we are limiting our root to be one block in size, there is a limit of how many subdirectories we can create, MAX_DIRS_IN_ROOT.
Each subdirectory will have an entry in the directories array with its name and the block index of the subdirectory’s directory entry.
Directories will be stored in our .disk file as a single block-sized cs1550_directory_entry structure per subdirectory.
The structure is defined below (again the actual one we provide in the code has additional attributes and padding to force the structure to be 512 bytes):
struct cs1550_directory_entry
{
int nFiles; //How many files are in this directory.
//Needs to be less than MAX_FILES_IN_DIR
struct cs1550_file_directory
{
char fname[MAX_FILENAME + 1]; //filename (plus space for nul)
char fext[MAX_EXTENSION + 1]; //extension (plus space for nul)
size_t fsize; //file size
long nStartBlock; //where the first block is on disk
} files[MAX_FILES_IN_DIR]; //There is an array of these
};
Since we require each directory entry to only take up a single disk block, we are limited to a fixed number of files per directory.
Each file entry in the directory has a filename in 8.3 (name.extension) format. We also need to record the total size of the file, and the location of the file’s first block on disk.
Files will be stored alongside the directories in.disk. Data blocks are 512-byte structs of the format:
struct cs1550_disk_block
{
//The next disk block, if needed. This is the next pointer in the linked
//allocation list
long nNextBlock;
//All the space in the block can be used for actual data
//storage.
char data[MAX_DATA_IN_BLOCK];
};
This is how the resulting system is logically structured:
The root points to directory Dir1, which has two files, FileA and FileB. FileB spans two dis-contiguous blocks. FileC is referred to from some other directory, not shown.
To be able to have a simple functioning file system, we need to handle a minimum set of operations on files and directories. The functions are listed here in the order that I suggest you implement them in. The last three do not need implemented beyond what the skeleton code has already.
The syscalls need to return success or failure. Success is indicated by 0 and appropriate errors by the negation of the error code, as listed on the corresponding function’s man page.
cs1550_getattr |
|
||||||
cs1550_mkdir |
|
||||||
cs1550_readdir |
|
||||||
|
|
||||||
cs1550_rmdir |
This function should not be modified. |
||||||
Above this line are the directory calls required for the first due date |
|||||||
|
|
||||||
cs1550_mknod |
|
||||||
cs1550_write |
|
||||||
cs1550_read |
|
||||||
cs1550_unlink |
|
||||||
cs1550_truncate |
This function should not be modified. |
||||||
cs1550_open |
This function should not be modified, as you get the full path every time any of the other functions are called. |
||||||
cs1550_flush |
This function should not be modified. |
The cs1550.c file is included as part of the Makefile in the examples directory, so building your changes is as simple as typing make.
One suggestion for testing is to launch a FUSE application with the -d option (./cs1550 -d testmount). This will keep the program in the foreground, and it will print out every message that the application receives, and interpret the return values that you’re getting back. Just open a second terminal window and try your testing procedures. Note if you do a CTRL+C in this window, you may not need to unmount the file system, but on crashes (transport errors) you definitely need to.
Your first steps will involve simply testing with ls and mkdir. When that works, try using echo and redirection to write to a file. cat will read from a file, and you will eventually even be able to launch pico on a file.
Remember that you may want to delete your.disk file if it becomes corrupted. You can use the commands od -x to see the contents in hex of a file, or the command strings to grab human readable text out of a binary file.
One of the major contributions the university provides for the AFS file system is nightly backups. However, the /u/OSLab/ partition is not part of AFS space. Thus, any files you modify under your personal directory in /u/OSLab/ are not backed up. If there is a catastrophic disk failure, all of your work will be irrecoverably lost. As such, it is my recommendation that you:
Backup all the files you change under /u/OSLab to your ~/private/ directory frequently!
Loss of work not backed up is not grounds for an extension. You have been warned.
20% of the grade will be based upon the directory portion of the project that is due by the first due date.
There are two submission dates.
For the directories portion, you need to submit:
Make a tar.gz file as in the first assignment, named USERNAME-project4-dir.tar.gz
Copy it to ~jrmst106/submit/1550 by the deadline for credit.
For the complete project, you need to submit:
Make a tar.gz file as in the first assignment, named USERNAME-project4-complete.tar.gz
Copy it to ~jrmst106/submit/1550 by the deadline for credit.