Skip to main content

LVM2 Method of adding Swap Space

Ok, so- like any good admin.. you probably have your disks setup in LVM2.  If not, that's OK.  This post won't help you out.

Your first step is to disable temporarily for the particular swap LV you're working with.   This is probably best done during a maintenance cycle for your server.  Let's assume that your Swap LV is called SwapVolume and the VG that contains it is "VolumeGroup".   

First you'll need to check if you even have enough free space.   Do a "vgdisplay VolumeGroup" and see if you have enough free space.   The output is fairly clear wrt that.  If you don't have enough free space, you'll have to arrange for a disk to be added to the system somehow- either SAN or a physical hard disk.

Adding a disk is out of this post's scope, so we're assuming we have enough space.   I always like to keep a couple of gigs in my back pocket on each system I manage.

Disable swap:  swapoff -v /dev/VolumeGroup/SwapVolume

Resize the LV: lvresize /dev/VolumeGroup/SwapVolume -L +1G

Format the space:  mkswap /dev/VolumeGroup/SwapVolume

Re-enable the swap:  swapon -va

Check that you see the increased space:

cat /proc/swaps
free

Comments

Popular posts from this blog

Starting vmtoolsd as a service on Red Hat / CentOS

If you're like me;  you may manage virtual servers within vSphere.. Linux ones.  Red Hat ones, in particular, but this applies to CentOS as well.

A long, long time ago, in a galaxy far away, the vmware-tools setup procedure installed the necessary init script for you.  Lately though, for new images that I've been building - those init scripts aren't getting installed by the vmware tools installation package.  So they don't start up on reboot.  VMware based backups failed; clock were going askew, you name it.   I need that daemon started on reboot.

Without a SysV init script handy, I had to roll my own.. and this is the result;  despite having worked with Linux for well over 15 years, setting up SysV init scripts remain somewhat of a black art.  The ones on our older system were more complicated than we needed.  I was aiming for something simpler and portable.

With RHEL 7, the rumor mills are abuzz with systemd so that may change. But, I'm a practical system admini…

Attempting to use dd on Mac OSX? Resource Busy?

If you're trying to use the dd command to image a usb disk or another device and you're running into an error that looks like:

# dd: /dev/disk#: Resource busy

There is a simple solution.

Use OSX's Disk Utility and unmount any of the partitions you have mounted on that particular disk without unmounting or ejecting the disk itself.

Afterwards, attempt the dd command again.

Update:  

Attempting to use the umount utility in Mac OSX will result in a "Resource busy -- try 'diskutil unmount'".  The command-line equivalent would be:

# sudo diskutil unmount /Volumes/<disk in question>

E.g.  

# sudo diskutil unmount /Volumes/FLASHUSB

NetApp: Disabling snapshot for a volume on Data OnTAP

This is one of those things that isn't always very obvious. Sometimes, you need to disable snapshots for a volume.

Why in the world would someone want to disable a perfectly good feature of NetApp NAS Storage? Server/data migration for one. Disabling it temporarily will prevent the volume from filling up the snapshot directory. Maybe your volume doesn't need snapshots (data always changing, and can not be recoverable even with snapshots- such as oracle data dirs, in which case snapshots are useless).
You have to perform simple but important tasks. If your volume has a schedule, turn it off.

somefiler> snap sched rootvol Volume rootvol: 2 4 8@2,4,6,12,164
somefiler> snap sched rootvol 0 0 0 
somefiler> snap sched rootvol Volume rootvol: 0 0 0

That takes care of that. Next step is to disable the automatic snapshot option.

somefiler> vol options rootvol nosnap on

Now if you issue vol options rootvol You should see an option that says nosnap=on.

Lastly, you'l…