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

Configuring AutoFS in FreeBSD

As a follow up to AutoFS in Linux, this post details simple usage of
AutoFS under FreeBSD, as controlled by 'amd'.  The purpose of AutoFS is
to mount volumes as they are needed and unmount them when they are not
in use.  The same setup I used in the Linux write up is presented here,

Configuring AutoFS in Linux

This post details simple usage of AutoFS under Linux.  The purpose of
AutoFS is to mount volumes as they are needed and unmount them when
they are not in use.  This is useful for sharing out home directories,
documentation, or applications to clients from a NAS cluster as well

Remounting Part of an FS Elsewhere

The following details loopback file system (FS) mounts. These allow one to effectively mount a portion of an FS elsewhere, providing access to the underlying sub-tree(s) via alternate pathnames wherein a symlink may not be appropriate. Our host details are:

new utility: timetrans.pl

I've posted a new utility, timetrans.pl, to the Tools page.  The following are both the "help" and "sample usage output" for timetrans.pl:

somehost [0] timetrans.pl -h

vSphere 5 Lab Setup pt 7

Continuing from part 6, we now come to the point where we can power on our
VMs .  Still using “dstor.lab.none” as a stand in for “dstor0”,
right-click on the VM within the vSphere client and select “Open
Console”:

vSphere 5 Lab Setup pt 6

In part 5, we created our infrastructure VMs, now we'll take care
of additional VM configuration and adding our boot ISOs to our local
datastore on pesx0.  Picking up where we left off in part 5, in the
left pane, select dstor0 (dstor.lab.none will stand in in the following)