cannot label 'c0t5000CCA0251EF65Cd0': EFI labeled devices are not supported on root pools Post: 302651005

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

passthrough devices vs. named devices

I am having trouble understanding the difference between a passthrough device and a named device and when you would use one or the other to access equipment. As an example, we have a tape library and giving the command "camcontrol devlist" gives the following output: akx# camcontrol...

2. Solaris

Help:"Bad checksum in disk label" and "Can't open disk label package"?

Hello, I'm brand new to Sun/Solaris. I have a Sun Blade 150, with SunOS 5.8. I wanted to make a backup to prevent future data loss, so I put the disk in a normal PC with Windows XP to try to make a backup with Norton Ghost, the disk was detected, but not the file volume, so I place the disk...

3. Solaris

Installing Sun Cluster on ZFS root pools

Hi All! I have been tasked with creating a clustered file system for two systems running Sol 10 u8. These systems have 3 zones each and the global zone has ZFS on the boot disk. We currently have one system sharing an NFS mount to both of these systems. The root zfs pool status (on the...

4. Solaris

Flash Archive Jumpstart with multiple ZFS Pools

Hi, I'm trying to get a Flash Archive Jumpstart Running with ZFS Filesystem. For Testing I set up a VirtualBox VM with 2 Disks attached. On the first disk I have the ZFS root pool, on the second Disk I have some more ZFS Pools which I use for 2 additional Zones I've set up. Restoring works fine if...

LEARN ABOUT CENTOS

crm_diff

PACEMAKER(8)						  System Administration Utilities					      PACEMAKER(8)

NAME

       Pacemaker - Part of the Pacemaker cluster resource manager

SYNOPSIS

       crm_diff original_xml operation [options]

DESCRIPTION

       crm_diff - A utility for comparing Pacemaker configurations (XML format)

       The tool produces a custom (diff-like) output which it can also apply like a patch

OPTIONS

       -?, --help
	      This text

       -$, --version
	      Version information

       -V, --verbose
	      Increase debug output

   Original XML:
       -o, --original=value
	      XML is contained in the named file

       -O, --original-string=value
	      XML is contained in the supplied string

   Operation:
       -n, --new=value
	      Compare the original XML to the contents of the named file

       -N, --new-string=value
	      Compare the original XML to the contents of the supplied string

       -p, --patch=value
	      Patch the original XML with the contents of the named file

   Additional Options:
       -c, --cib
	      Compare/patch the inputs as a CIB (includes versions details)

       -f, --filter
	      Suppress irrelevant differences between the two inputs

EXAMPLES

       Obtain the two different configuration files by running cibadmin on the two cluster setups to compare:

	      # cibadmin --query > cib-old.xml

	      # cibadmin --query > cib-new.xml

       Calculate and save the difference between the two files:

	      # crm_diff --original cib-old.xml --new cib-new.xml > patch.xml

       Apply the patch to the original file:

	      # crm_diff --original cib-old.xml --patch patch.xml > updated.xml

       Apply the patch to the running cluster:

	      # cibadmin --patch patch.xml

AUTHOR

       Written by Andrew Beekhof

REPORTING BUGS

       Report bugs to pacemaker@oss.clusterlabs.org

Pacemaker 1.1.10-29.el7 					     June 2014							      PACEMAKER(8)