Configuring NFS in SmartOS

In the past, I've written up configuring NFS in Solaris, FreeBSD,
and Linux. Now I'll turn my focus to SmartOS. Briefly, NFS
(network file system) provides access to remote filesystems which
appear similar to local resources on client hosts. The following

Intro SmartOS Setup pt 4

Following up from part 3, where we installed and configured our SmartOS
host (cn40), we now get to start checking out handling and management
of SmartOS OS VMs (SOSVMs). Jumping in where we left off in part 3, we
start with the configuration for our image repository hosted on "serv1"

Intro SmartOS Setup pt 3

In part 1, I detailed our general expectations and in part 2, our services
infrastructure VM (IVM) was configured. Here in part 3, we finally get to
check out our first SmartOS IVM and compute node, "cn40". The VirtualBox
(VBox) configuration for "cn40" is:

Intro SmartOS Setup pt 2

In part 1, I detailed the general expectations, layout, and router
infrastructure VM (IVM) for our SmartOS sandbox environment. In part 2,
we move on to our services IVM, "serv1". To recap, "serv1" will host
a name server, web server, and time server for our SmartOS compute nodes

Intro SmartOS Setup pt 1

For a while now, I've wanted to check out Joyent's SmartOS but until
recently, simply didn't have the time. This series of posts details my
initial setup and testing of SmartOS. (To jump straight to SmartOS within
VirtualBox (VBox), see part 3.) For better or worse, I really enjoy

Repartitioning Contiguous Space in Linux

As a follow up to the same under Solaris, I thought I'd detail
repartitioning in-use, contiguous space in Linux. To recap the
situational setup, a filesystem (FS) has run out of space and the data
contained on it couldn't be removed or compressed to free up space.

Repartitioning Contiguous Space in Solaris

Recently, a system owner aked me for help because they had run out of space on one of their filesystems (FS). As a result, this was causing problems with the application they had running. Unfortunately, this FS was being used for database files so we couldn't just remove or