... | ... | @@ -32,16 +32,16 @@ On the `boss` node there is only one Emulab-related file hierarchy to worry abou |
|
|
|
|
|
* **/usr/testbed** Space for testbed software, data, and logs, as well as standard disk images. The requirements here are mostly about how many images you are likely to have and how long you want to keep logs. Anywhere from 100GB to 1TB is a good choice. [800GB]
|
|
|
|
|
|
While we have split `/usr/testbed` into multiple filesystems (e.g., `/usr/testbed`, /usr/testbed/data`, `/usr/testbed/logs`) at some sites, there is not a particularly compelling reason to do so for most people.
|
|
|
**Note:** While we have split `/usr/testbed` into multiple filesystems (e.g., `/usr/testbed`, `/usr/testbed/data`, `/usr/testbed/logs`) at some sites, there is not a particularly compelling reason to do so for most people.
|
|
|
|
|
|
### Using UFS
|
|
|
#### Using UFS
|
|
|
|
|
|
The traditional UFS filesystem is best used with a single redundant underlying volume, either
|
|
|
a hardware RAID provided volume, or a virtual disk provided by the VM host. Otherwise you are taking your chances with a disk failure. While you can use FreeBSD's `gvinum` or `graid` to implement RAID or interact with a software RAID controller, it is recommended that you [use ZFS instead](#using-zfs) if you need to build a multi-disk redundant configuration.
|
|
|
|
|
|
Here are two examples of configuring space on a single disk, either for a system with a large single disk shared by both the OS and Emulab, or with a second disk dedicated to Emulab bits.
|
|
|
|
|
|
#### Shared Single Disk
|
|
|
##### Shared Single Disk
|
|
|
|
|
|
This example creates a separate filesystem for `/usr/testbed`. It assumes you have modified the FreeBSD install and swap partitions during installation to leave space for this filesystem. You can use `gpart show` to determine what device ("geom") to specify, use the one with the most free space. It will most likely be "ada0s1" as is shown in the following.
|
|
|
```
|
... | ... | @@ -57,7 +57,7 @@ echo '/dev/ada0s1d /usr/testbed ufs rw 1 2' >> /etc/fstab |
|
|
mount /usr/testbed
|
|
|
```
|
|
|
|
|
|
#### Second Dedicated Disk
|
|
|
##### Second Dedicated Disk
|
|
|
|
|
|
If you have a second disk (/dev/ada1) available for just Emulab, then the process is similar, but the disk first has to be prepared. We use GPT partitioning in this case to be consistant with the `ops` node configuration.
|
|
|
```
|
... | ... | @@ -77,7 +77,7 @@ echo '/dev/ada1p1 /usr/testbed ufs rw 1 2' >> /etc/fstab |
|
|
mount /usr/testbed
|
|
|
```
|
|
|
|
|
|
### Using ZFS
|
|
|
#### Using ZFS
|
|
|
|
|
|
The major reason to use ZFS for the `boss` node Emulab filesystem is if you have multiple physical disks available for Emulab storage and they are not combined using hardware RAID. Otherwise you might as well [use UFS](#using-ufs).
|
|
|
|
... | ... | |