Version 1 - Replace in modules/gd/classes/GdToolkit.class:

case 'thumbnail':
        case 'scale':
            /* $parameters[0]: target width, [1]: optional target height */
            $targetHeight = empty($parameters[1]) ? $parameters[0] : $parameters[1];
            /* Don't enlarge images for a thumbnail */
            if ($operationName == 'thumbnail'
                    && $width <= $parameters[0] && $height <= $targetHeight) {
                break;

Version 1 - Replace in modules/imagemagick/classes/ImageMagickToolkit.class:

/* Don't enlarge images for a thumbnail */
 	    if ($width > $parameters[0] || $height > $parameters[0]) {
 		$this->_addResizeParam($transform, $parameters[0]);
 		list ($width, $height) =
 		    GalleryUtilities::scaleDimensionsToFit($width, $height, $parameters[0]);
 	    }

with:

/* Create the thumbnail with fixed width */
	    $aspect = $height / $width;
	    $targetWidth = $parameters[0];

If you attach to linux box a disk partitioned under FreeBSD or OS X, you will find this warning message on fdisk command:
"WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted."

In the following example, we will map npiv adapters by using 2 VIO servers.
If you do not understand at all what follows, you better not do it :)

1. Create the virtual adapters for both vios and lpar via HMC (graphical or console).

Not covered here yet. You will have to handle this yourself.

2. Map the adapters on VIO1:

List npivs and search for the ones you have created:

lsmap -all -npiv

During mksysb process you have the chance to encounter many errors. One of them is "An internal packing error occurred: incorrect size" and I will try below to aid you to get pass it.

The error:

# mksysb -eiX /backups-tmp/gzlpar-rootvg.sysb

Creating information file (/image.data) for rootvg.

Creating list of files to back up
Backing up 89961 files......................[color=red]An internal packing error occurred: incorrect size
./var/adm/wtmp will not be backed up.[/color]

Let's say you have created a snapshot, you have used it and now you want to remove it.
What you can do if you get the following message?

core:~# lvscan | grep mylv
  ACTIVE   Original '/dev/datavg/mylv' [2.00 GiB] inherit
  ACTIVE   Snapshot '/dev/datavg/snapmylv' [1.00 GiB] inherit
  
core:~# lvremove -f /dev/datavg/snapmylv
  [color=red]Can't remove open logical volume "snapmylv"[/color]

One way is to ask dmsetup for help:

By listing linked devices in /dev:

root@pluto:~# ls -la /dev/disk/by-path/*iscsi*
lrwxrwxrwx 1 root root  9 Dec  6 14:13 /dev/disk/by-path/ip-9.6.9.3:3260-iscsi-iqn.2014-07.ro.gz.sun:backups-btrfs-lun-0 -> ../../sdb
lrwxrwxrwx 1 root root  9 Dec  6 14:39 /dev/disk/by-path/ip-9.6.9.3:3260-iscsi-iqn.2014-07.ro.gz.sun:pluto-lun-0 -> ../../sdd
lrwxrwxrwx 1 root root  9 Dec  6 14:13 /dev/disk/by-path/ip-9.6.9.4:3260-iscsi-iqn.2014-07.ro.gz.ogle:backups-btrfs-lun-0 -> ../../sdc

I will make it simple. You are here because you need something. Read on and see if you can find below what you are looking for.

If you need extra info, do not be shy and visit mysql docs: https://dev.mysql.com/doc/refman/5.5/en/sql-syntax-server-administration.html

How to create mysql user:

In our example we create user drat with access from 192.168.69.69 and 192.168.69.1 and password verysimple.

[h3]How to move the services manually, to the secondary node (candy):[/h4]
This will also prevent the resource to automatically failover if the primary node is back online so keep that in mind when you plan several reboots on primary node and you don't want to be bothered.
crm resource migrate nfs-group candy

How to stop/start a resource group:

crm resource stop nfs-group
crm resource start nfs-group

The examples below are done on an environment where drbd volume resides on lvm logical volume and the filesystem is reiserfs.

a. If you want to shrink it, you will have to reduce first the filesystem on the primary node then the logical volume on both nodes. Afterwards you execute the resize command for drbd on primary node.
Be careful, in order to shrink the filesystem, you will have to umount it and obviously to stop the services before that (nfs, apache, etc.).

Primary node:

umount /nfs