Otmanix' Blog » Archive for svm

Posts Tagged “svm”

10 04 2009

flying zones für Arme – Teil 2: Liveupgrade mit Solaris10 Update6 und ZFS-root

Geschrieben von otmanix in EMC, Solaris, VMware, Virtualisierung, ZFS, tags: Container, Liveupgrade, recommended patch cluster, Solaris, svm, upgrade-on-attach, VMware, ZFS, zones

Zuletzt habe ich darüber geschrieben wie man mit Vmware Server 2.01 und Solaris10 ein sog. “flying zones”-Szenario aufbauen kann. D.h. man installiert eine Solaris-Zone auf einer shared disk und kann dann eine sog. Zonenmigration durchführen. D.h. die Zone und die Filesysteme der Zone werden am ersten Rechner exportiert und am zweiten Rechner wird das Ganze dann wieder importiert.

serielles Patching und Zonen

Ein leidiges Thema, insbesondere bei Solaris Zonen, ist das Installieren von Patches. In regelmäßigen Abständen wird man z.B. dazu angehalten das “recommended patch cluster” zu installieren. In der Regel befinden sich Kernelpatches in den Patch-Sammlungen, so dass eine Installation im Single-User-Modus erforderlich ist. Zudem müssen auch alle Zonen beim Patchen verfügbar sein (nicht detached!). Das Standard-Patchinstallationstool von Sun arbeitet dann die Patchinstallation sequentiell ab. Bei einer größeren Anzahl Zonen kann das u.U. zeitkrisch werden.

Parallel Patching, Solaris Liveupgrade, Neuerungen in Solaris10u6 10/08

Gute Neuigkeiten gibt es bei Jeff Victor. Demnächst soll also eine neue Version des patchadd-Kommandos das parallele Patchen von Zonen beherrschen. Aber auch das ist u.U. noch zu zeitinsiv. Seit längerem gibt es bereits die Software Solaris Liveupgrade, die zum Patchen oder Upgraden auf ein neues Release benutzt werden kann. Dabei wird zunächst vom laufenden Solaris eine Kopie erzeugt, ein sog. boot environment (BE), auf der dann die Patches bzw. das Upgrade angewendet werden. Das ganze passiert im normalen Onlinebetrieb. Ist die Aktionen abgeschlossen, wird vom alternativen BE gebootet. Gibt es Ärger hat man ein Fallback auf das verherige BE.

Zunächst wurde Liveupgrade “zone aware” gemacht. D.h. auch Zonen können seit einiger Zeit damit aktualisiert werden. Im Solaris10u6 kam dann die Unterstützung für ZFS-root (ZFS-Pool als Bootumgebung für das Rootfilesystem) und “upgrade-on-attach”. War eine Zone beim Upgrade detached und hat somit einen älteren Stand kann nun beim Attach die Aktualisierung nachgeholt werden.

Infos zum Thema gibt es hier:

Solaris 10 10/08 Installation Guide: Solaris Live Upgrade and Upgrade Planning

Solution 206844: Solaris[TM] Live Upgrade Software: Minimum Patch Requirements

Solaris Liveupgrade bei S10u6 im Praxiseinsatz

Ich möchte also nun die Umgebung aus dem letzten Artikel auf Basis Solaris10u6 mit Hilfe von Liveupgrade auf das aktuelle recommended patch cluster patchen.

bash-3.00# cat /etc/release
Solaris 10 10/08 s10x_u6wos_07b X86
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 27 October 2008

# zoneadm list -cv
ID NAME             STATUS     PATH                           BRAND    IP
0 global           running    /                              native   shared
1 zone1            running    /zone1                         native   shared

# lustatus
ERROR: No boot environments are configured on this system
ERROR: cannot determine list of all boot environment names

# lucreate -n s10u6_recpatches
Checking GRUB menu…
Analyzing system configuration.
No name for current boot environment.
INFORMATION: The current boot environment is not named – assigning name <s10x_u6wos_07b>.
Current boot environment is named <s10x_u6wos_07b>.
Creating initial configuration for primary boot environment <s10x_u6wos_07b>.
The device </dev/dsk/c1t0d0s0> is not a root device for any boot environment; cannot get BE ID.
PBE configuration successful: PBE name <s10x_u6wos_07b> PBE Boot Device </dev/dsk/c1t0d0s0>.
Comparing source boot environment <s10x_u6wos_07b> file systems with the
file system(s) you specified for the new boot environment. Determining
which file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <s10u6_recpatches>.
Source boot environment is <s10x_u6wos_07b>.
Creating boot environment <s10u6_recpatches>.
Cloning file systems from boot environment <s10x_u6wos_07b> to create boot environment <s10u6_recpatches>.
Creating snapshot for <rpool/ROOT/s10x_u6wos_07b> on <rpool/ROOT/s10x_u6wos_07b@s10u6_recpatches>.
Creating clone for <rpool/ROOT/s10x_u6wos_07b@s10u6_recpatches> on <rpool/ROOT/s10u6_recpatches>.
Setting canmount=noauto for </> in zone <global> on <rpool/ROOT/s10u6_recpatches>.
Creating snapshot for <zone1> on <zone1@s10u6_recpatches>.
cannot create ‘.’: missing dataset name
Creating clone for <zone1@s10u6_recpatches> on <zone1-s10u6_recpatches>.
ERROR: cannot create ‘zone1-s10u6_recpatches’: missing dataset name
ERROR: Unable to clone <> on <>.
/usr/lib/lu/luclonefs: zone1@s10u6_recpatches: not found
cannot open ‘zone1-s10u6_recpatches’: dataset does not exist
cannot open ‘zone1-s10u6_recpatches’: dataset does not exist
cannot open ‘zone1-s10u6_recpatches’: dataset does not exist
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <s10u6_recpatches> as <mount-point>//boot/grub/menu.lst.prev.
File </boot/grub/menu.lst> propagation successful
Copied GRUB menu from PBE to ABE
No entry for BE <s10u6_recpatches> in GRUB menu
Population of boot environment <s10u6_recpatches> successful.
Creation of boot environment <s10u6_recpatches> successful.

# lustatus
Boot Environment           Is       Active Active    Can    Copy
Name                       Complete Now    On Reboot Delete Status
————————– ——– —— ——— —— ———-
s10x_u6wos_07b             yes      yes    yes       no     -
s10u6_recpatches           yes      no     no        yes    -

bash-3.00# zpool list
NAME    SIZE   USED AVAIL    CAP HEALTH ALTROOT
rpool 7.94G 6.78G 1.15G    85% ONLINE -
zone1 1.98G   546M 1.45G    26% ONLINE -

bash-3.00# zfs list
NAME                                         USED AVAIL REFER MOUNTPOINT
rpool                                       7.07G   766M 38.5K /rpool
rpool/ROOT                                  5.68G   766M    18K legacy
rpool/ROOT/s10u6_recpatches                  156K   766M 3.77G /a/
rpool/ROOT/s10x_u6wos_07b                   5.68G   766M 5.67G /
rpool/ROOT/s10x_u6wos_07b@s10u6_recpatches 12.0M      - 3.77G -
rpool/dump                                   900M   766M   900M -
rpool/export                                  37K   766M    19K /export
rpool/export/home                             18K   766M    18K /export/home
rpool/swap                                   512M 1.03G   222M -
zone1                                        546M 1.42G   545M /zone1
zone1@s10u6_recpatches                       619K      -   545M -

bash-3.00# cd /patches/10_x86_Recommended

bash-3.00# lumount s10u6_recpatches /a
ERROR: unable to mount zones:
/a/zone1 must not be group readable.
/a/zone1 must not be group executable.
/a/zone1 must not be world readable.
/a/zone1 must not be world executable.
could not verify zonepath /a/zone1 because of the above errors.
zoneadm: zone zone1 failed to verify
ERROR: unable to mount zone <zone1> in </a>
ERROR: unmounting partially mounted boot environment file systems
ERROR: No such file or directory: error unmounting <rpool/ROOT/s10u6_recpatches>
ERROR: umount: warning: rpool/ROOT/s10u6_recpatches not in mnttab
umount: rpool/ROOT/s10u6_recpatches no such file or directory
ERROR: cannot unmount <rpool/ROOT/s10u6_recpatches>
ERROR: cannot mount boot environment by name <s10u6_recpatches>

bash-3.00# lustatus
Boot Environment           Is       Active Active    Can    Copy
Name                       Complete Now    On Reboot Delete Status
————————– ——– —— ——— —— ———-
s10x_u6wos_07b             yes      yes    yes       no     -
s10u6_recpatches           yes      no     no        yes    -

bash-3.00# ludelete s10u6_recpatches
System has findroot enabled GRUB
Checking if last BE on any disk…
ERROR: unable to mount zones:
/.alt.s10u6_recpatches/zone1 must not be group readable.
/.alt.s10u6_recpatches/zone1 must not be group executable.
/.alt.s10u6_recpatches/zone1 must not be world readable.
/.alt.s10u6_recpatches/zone1 must not be world executable.
could not verify zonepath /.alt.s10u6_recpatches/zone1 because of the above errors.
zoneadm: zone zone1 failed to verify
ERROR: unable to mount zone <zone1> in </.alt.s10u6_recpatches>
ERROR: unmounting partially mounted boot environment file systems
ERROR: No such file or directory: error unmounting <rpool/ROOT/s10u6_recpatches>
ERROR: umount: warning: rpool/ROOT/s10u6_recpatches not in mnttab
umount: rpool/ROOT/s10u6_recpatches no such file or directory
ERROR: cannot unmount <rpool/ROOT/s10u6_recpatches>
ERROR: cannot mount boot environment by name <s10u6_recpatches>
ERROR: Failed to mount BE <s10u6_recpatches>.
ERROR: Failed to mount BE <s10u6_recpatches>.
cat: cannot open /tmp/.lulib.luclb.dsk.5254.s10u6_recpatches
ERROR: This boot environment <s10u6_recpatches> is the last BE on the above disk.
ERROR: Deleting this BE may make it impossible to boot from this disk.
ERROR: However you may still boot solaris if you have BE(s) on other disks.
ERROR: You *may* have to change boot-device order in the BIOS to accomplish this.
ERROR: If you still want to delete this BE <s10u6_recpatches>, please use the force option (-f).
Unable to delete boot environment.

bash-3.00# ludelete -f s10u6_recpatches
System has findroot enabled GRUB
No entry for BE <s10u6_recpatches> in GRUB menu
Determining the devices to be marked free.
Updating boot environment configuration database.
Updating boot environment description database on all BEs.
Updating all boot environment configuration databases.
Boot environment <s10u6_recpatches> deleted.

bash-3.00# lustatus
Boot Environment           Is       Active Active    Can    Copy
Name                       Complete Now    On Reboot Delete Status
————————– ——– —— ——— —— ———-
s10x_u6wos_07b             yes      yes    yes       no     -

bash-3.00# zfs list
NAME                        USED AVAIL REFER MOUNTPOINT
rpool                      7.11G   715M 38.5K /rpool
rpool/ROOT                 5.73G   715M    18K legacy
rpool/ROOT/s10x_u6wos_07b 5.73G   715M 5.73G /
rpool/dump                  900M   715M   900M -
rpool/export                 37K   715M    19K /export
rpool/export/home            18K   715M    18K /export/home
rpool/swap                  512M   984M   243M -
zone1                       546M 1.42G   545M /zone1
zone1@s10u6_recpatches      619K      -   545M -

bash-3.00# zfs destroy zone1@s10u6_recpatches

Na bravo! Das war ja der totale Reinfall…

Scheinbar kommt Liveupgrade nicht damit klar, dass die Zone in einem seperaten ZFS-Pool liegt. Das ist aber für die Zonenmigration unabdingbar.

neuer Versuch – Liveupgrade ohne Zonen, nur für ZFS-root

Dazu also erst einmal die Zone1 verschwinden lassen…

bash-3.00# zoneadm -z zone1 detach

bash-3.00# metaset -s zone1data -r

bash-3.00# metaset
Set name = zone1data, Set number = 1
Host                Owner
horst1
horst2
Drive    Dbase
c2t1d0   Yes
c3t1d0   Yes

bash-3.00# zpool export zone1

bash-3.00# zpool list
NAME      SIZE   USED AVAIL    CAP HEALTH ALTROOT
patches 7.94G 2.69G 5.25G    33% ONLINE -
rpool    7.94G 4.93G 3.01G    62% ONLINE -

bash-3.00# lucreate -n s10u6_recpatches
Checking GRUB menu…
System has findroot enabled GRUB
Analyzing system configuration.
Comparing source boot environment <s10x_u6wos_07b> file systems with the
file system(s) you specified for the new boot environment. Determining
which file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <s10u6_recpatches>.
Source boot environment is <s10x_u6wos_07b>.
Creating boot environment <s10u6_recpatches>.
Cloning file systems from boot environment <s10x_u6wos_07b> to create boot environment <s10u6_recpatches>.
Creating snapshot for <rpool/ROOT/s10x_u6wos_07b> on <rpool/ROOT/s10x_u6wos_07b@s10u6_recpatches>.
Creating clone for <rpool/ROOT/s10x_u6wos_07b@s10u6_recpatches> on <rpool/ROOT/s10u6_recpatches>.
Setting canmount=noauto for </> in zone <global> on <rpool/ROOT/s10u6_recpatches>.
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <s10u6_recpatches> as <mount-point>//boot/grub/menu.lst.prev.
File </boot/grub/menu.lst> propagation successful
Copied GRUB menu from PBE to ABE
No entry for BE <s10u6_recpatches> in GRUB menu
Population of boot environment <s10u6_recpatches> successful.
Creation of boot environment <s10u6_recpatches> successful.

Na gut, das Erstellen des alternate BE hat also soweit geklappt. Nun zum Patchen..

bash-3.00# cd /patches/10_x86_Recommended/

bash-3.00# luupgrade -n s10u6_recpatches -s /patches/10_x86_Recommended -t `cat patch_order`
System has findroot enabled GRUB
No entry for BE <s10u6_recpatches> in GRUB menu
Validating the contents of the media </patches/10_x86_Recommended>.
The media contains 152 software patches that can be added.
Mounting the BE <s10u6_recpatches>.
Adding patches to the BE <s10u6_recpatches>.
Validating patches…
Loading patches installed on the system…
Done!
Loading patches requested to install.
Version of package SUNWmctag from directory SUNWmctag in patch 121212-02 differs from the package installed on the system.
Version of package SUNWmcosx from directory SUNWmcosx in patch 121212-02 differs from the package installed on the system.
Version of package SUNWmcon from directory SUNWmcon in patch 121212-02 differs from the package installed on the system.
Version of package SUNWmcos from directory SUNWmcos in patch 121212-02 differs from the package installed on the system.
Done!
The following requested patches have packages not installed on the system
Package SUNWgzipS from directory SUNWgzipS in patch 120720-02 is not installed on the system. Changes for package SUNWgzipS will not be applied to the system.
Package SUNWbzipS from directory SUNWbzipS in patch 126869-03 is not installed on the system. Changes for package SUNWbzipS will not be applied to the system.
Package SUNWbreg from directory SUNWbreg in patch 121454-02 is not installed on the system. Changes for package SUNWbreg will not be applied to the system.
Package SUNWdc from directory SUNWdc in patch 121454-02 is not installed on the system. Changes for package SUNWdc will not be applied to the system.
Package SUNWbreg from directory SUNWbreg in patch 121454-02 is not installed on the system. Changes for package SUNWbreg will not be applied to the system.
Package SUNWdc from directory SUNWdc in patch 121454-02 is not installed on the system. Changes for package SUNWdc will not be applied to the system.
Package SUNWsmaS from directory SUNWsmaS in patch 120273-25 is not installed on the system. Changes for package SUNWsmaS will not be applied to the system.
Package SUNWsmbaS from directory SUNWsmbaS in patch 119758-14 is not installed on the system. Changes for package SUNWsmbaS will not be applied to the system.
Package SUNWpostgr-jdbcS from directory SUNWpostgr-jdbcS in patch 123591-09 is not installed on the system. Changes for package SUNWpostgr-jdbcS will not be applied to the system.
Package SUNWpostgrS from directory SUNWpostgrS in patch 123591-09 is not installed on the system. Changes for package SUNWpostgrS will not be applied to the system.
Package SUNWpostgr-tclS from directory SUNWpostgr-tclS in patch 123591-09 is not installed on the system. Changes for package SUNWpostgr-tclS will not be applied to the system.
Package SUNWkxplt from directory SUNWkxplt in patch 120415-23 is not installed on the system. Changes for package SUNWkxplt will not be applied to the system.
Package SUNWinleu from directory SUNWinleu in patch 120415-23 is not installed on the system. Changes for package SUNWinleu will not be applied to the system.
Package SUNWhkleu from directory SUNWhkleu in patch 120415-23 is not installed on the system. Changes for package SUNWhkleu will not be applied to the system.
Package SUNWcxplt from directory SUNWcxplt in patch 120415-23 is not installed on the system. Changes for package SUNWcxplt will not be applied to the system.
Package SUNWhleu from directory SUNWhleu in patch 120415-23 is not installed on the system. Changes for package SUNWhleu will not be applied to the system.
Package SUNWhleu2 from directory SUNWhleu2 in patch 120415-23 is not installed on the system. Changes for package SUNWhleu2 will not be applied to the system.
Package SUNWkleu from directory SUNWkleu in patch 120415-23 is not installed on the system. Changes for package SUNWkleu will not be applied to the system.
Package SUNWtleu from directory SUNWtleu in patch 120415-23 is not installed on the system. Changes for package SUNWtleu will not be applied to the system.
Package SUNWhkplt from directory SUNWhkplt in patch 120415-23 is not installed on the system. Changes for package SUNWhkplt will not be applied to the system.
Package SUNWinplt from directory SUNWinplt in patch 120415-23 is not installed on the system. Changes for package SUNWinplt will not be applied to the system.
Package SUNWtxplt from directory SUNWtxplt in patch 120415-23 is not installed on the system. Changes for package SUNWtxplt will not be applied to the system.
Package SUNWhxplt from directory SUNWhxplt in patch 120415-23 is not installed on the system. Changes for package SUNWhxplt will not be applied to the system.
Package SUNWsunpinyin from directory SUNWsunpinyin in patch 120415-23 is not installed on the system. Changes for package SUNWsunpinyin will not be applied to the system.
Package SUNWsibi from directory SUNWsibi in patch 119082-25 is not installed on the system. Changes for package SUNWsibi will not be applied to the system.
Package SUNWapchS from directory SUNWapchS in patch 122912-15 is not installed on the system. Changes for package SUNWapchS will not be applied to the system.
Package SUNWgrubS from directory SUNWgrubS in patch 138884-01 is not installed on the system. Changes for package SUNWgrubS will not be applied to the system.
Package SUNWsibi from directory SUNWsibi in patch 124629-10 is not installed on the system. Changes for package SUNWsibi will not be applied to the system.
Package SUNWsibi from directory SUNWsibi in patch 119253-31 is not installed on the system. Changes for package SUNWsibi will not be applied to the system.
Package SUNWTkS from directory SUNWTkS in patch 137872-02 is not installed on the system. Changes for package SUNWTkS will not be applied to the system.
Package SUNWipmiS from directory SUNWipmiS in patch 119765-06 is not installed on the system. Changes for package SUNWipmiS will not be applied to the system.
Package SUNWj5jmp from directory SUNWj5jmp in patch 118668-19 is not installed on the system. Changes for package SUNWj5jmp will not be applied to the system.
Package SUNWpngS from directory SUNWpngS in patch 137081-01 is not installed on the system. Changes for package SUNWpngS will not be applied to the system.
Package SUNWsibi from directory SUNWsibi in patch 124631-24 is not installed on the system. Changes for package SUNWsibi will not be applied to the system.
Package SUNWgtarS from directory SUNWgtarS in patch 139100-01 is not installed on the system. Changes for package SUNWgtarS will not be applied to the system.
Package SUNWbindS from directory SUNWbindS in patch 119784-10 is not installed on the system. Changes for package SUNWbindS will not be applied to the system.
Package SUNWzebraS from directory SUNWzebraS in patch 126207-04 is not installed on the system. Changes for package SUNWzebraS will not be applied to the system.
Package SUNWcleu2 from directory SUNWcleu2 in patch 120413-09 is not installed on the system. Changes for package SUNWcleu2 will not be applied to the system.
Package SUNWmysqlS from directory SUNWmysqlS in patch 120293-02 is not installed on the system. Changes for package SUNWmysqlS will not be applied to the system.
Package SUNWimagickS from directory SUNWimagickS in patch 136883-02 is not installed on the system. Changes for package SUNWimagickS will not be applied to the system.
Package SUNWapch2S from directory SUNWapch2S in patch 120544-14 is not installed on the system. Changes for package SUNWapch2S will not be applied to the system.
Package SUNWlxmlS from directory SUNWlxmlS in patch 125732-04 is not installed on the system. Changes for package SUNWlxmlS will not be applied to the system.
The following requested patches are already installed on the system
Requested patch 120720-02 is already installed on the system.
Requested patch 121297-01 is already installed on the system.
Requested patch 122035-05 is already installed on the system.
Requested patch 118344-14 is already installed on the system.
Requested patch 118919-21 is already installed on the system.
Requested patch 120901-03 is already installed on the system.
Requested patch 121334-04 is already installed on the system.
Requested patch 123840-04 is already installed on the system.
Requested patch 127756-01 is already installed on the system.
Requested patch 117435-02 is already installed on the system.
Requested patch 121264-01 is already installed on the system.
Requested patch 119575-02 is already installed on the system.
Requested patch 113000-07 is already installed on the system.
Requested patch 138218-01 is already installed on the system.
Requested patch 121454-02 is already installed on the system.
Requested patch 121454-02 is already installed on the system.
Requested patch 118855-36 is already installed on the system.
Requested patch 126424-03 is already installed on the system.
Requested patch 122641-06 is already installed on the system.
Requested patch 125548-02 is already installed on the system.
Requested patch 125504-02 is already installed on the system.
Requested patch 120012-14 is already installed on the system.
Requested patch 127128-11 is already installed on the system.
Requested patch 119318-01 is already installed on the system.
Requested patch 123612-05 is already installed on the system.
Requested patch 123591-09 is already installed on the system.
Requested patch 128412-01 is already installed on the system.
Requested patch 125542-03 is already installed on the system.
Requested patch 121976-01 is already installed on the system.
Requested patch 138182-01 is already installed on the system.
Requested patch 120202-06 is already installed on the system.
Requested patch 119082-25 is already installed on the system.
Requested patch 138884-01 is already installed on the system.
Requested patch 137138-09 is already installed on the system.
Requested patch 124445-01 is already installed on the system.
Requested patch 126541-02 is already installed on the system.
Requested patch 136999-05 is already installed on the system.
Requested patch 137872-02 is already installed on the system.
Requested patch 138276-01 is already installed on the system.
Requested patch 119765-06 is already installed on the system.
Requested patch 138362-01 is already installed on the system.
Requested patch 119811-05 is already installed on the system.
Requested patch 120330-02 is already installed on the system.
Requested patch 138323-02 is already installed on the system.
Requested patch 128001-01 is already installed on the system.
Requested patch 124189-02 is already installed on the system.
Requested patch 138270-02 is already installed on the system.
Requested patch 119131-33 is already installed on the system.
Requested patch 119901-06 is already installed on the system.
Requested patch 137081-01 is already installed on the system.
Requested patch 123614-01 is already installed on the system.
Requested patch 138624-02 is already installed on the system.
Requested patch 118960-03 is already installed on the system.
Requested patch 128329-01 is already installed on the system.
Requested patch 136840-01 is already installed on the system.
Requested patch 121013-02 is already installed on the system.
Requested patch 119116-34 is already installed on the system.
Requested patch 124458-01 is already installed on the system.
Requested patch 124998-01 is already installed on the system.
Requested patch 138877-01 is already installed on the system.
Requested patch 126207-04 is already installed on the system.
Requested patch 120236-01 is already installed on the system.
Requested patch 138266-01 is already installed on the system.
Requested patch 138105-01 is already installed on the system.
Requested patch 127854-02 is already installed on the system.
Requested patch 138374-02 is already installed on the system.
Requested patch 137033-01 is already installed on the system.
Requested patch 119813-08 is already installed on the system.
Requested patch 120293-02 is already installed on the system.
Requested patch 123939-01 is already installed on the system.
Requested patch 137094-01 is already installed on the system.
Requested patch 121096-02 is already installed on the system.
Requested patch 124939-03 is already installed on the system.
Requested patch 119987-03 is already installed on the system.
Requested patch 137322-01 is already installed on the system.
Requested patch 119904-02 is already installed on the system.
Requested patch 120831-06 is already installed on the system.
Requested patch 126441-01 is already installed on the system.
Requested patch 125280-05 is already installed on the system.
The following requested patches do not update any packages installed on the system
No Packages from patch 121212-02 are installed on the system.
Checking patches that you specified for installation.
Done!
The following requested patches will not be installed because
they have been made obsolete by other patches already
installed on the system or by patches you have specified for installation.
0 All packages from patch 118844-20 are patched by higher revision patches.
1 All packages from patch 122661-08 are patched by higher revision patches.
2 All packages from patch 124205-05 are patched by higher revision patches.
The following requested patches will not be installed because
the packages they patch are not installed on this system.
0 No Packages from patch 120415-23 are installed on the system.
1 No Packages from patch 120413-09 are installed on the system.
Approved patches will be installed in this order:
126869-03 126420-02 119255-65 126539-02 121119-15 120273-25 119758-14 126366-14
120740-05 119060-45 120411-30 122912-15 141009-01 125556-02 137122-06 138628-07
124629-10 119253-31 138372-06 125540-06 137128-05 119214-18 140775-03 123896-10
118668-19 139499-04 121309-16 119314-26 122213-32 139463-02 125185-11 121395-03
138857-02 118669-19 140384-01 120200-15 124631-24 138264-03 139100-01 138286-02
119784-10 119091-32 138224-03 138882-02 139482-01 138242-05 140145-01 119247-35
120223-31 139580-02 125165-13 125953-18 139501-02 139561-02 125333-05 139484-05
141015-01 124394-09 140456-01 136883-02 120095-22 125720-28 120544-14 125732-04
126364-07 138254-02 138867-02 138889-08
Checking installed patches…
Verifying sufficient filesystem capacity (dry run method)…
Installing patch packages…
Patch 126869-03 has been successfully installed.
See /a/var/sadm/patch/126869-03/log for details
Patch packages installed:
SUNWbzip
SUNWsfman
Checking installed patches…
Verifying sufficient filesystem capacity (dry run method)…
Installing patch packages…
Patch 126420-02 has been successfully installed.
See /a/var/sadm/patch/126420-02/log for details
Patch packages installed:
SUNWcsr
SUNWcsu
…
Patch 138889-08 has been successfully installed.
See /a/var/sadm/patch/138889-08/log for details
Patch packages installed:
SUNWcakr
SUNWckr
SUNWcpcu
SUNWcsd
SUNWcsl
SUNWcslr
SUNWcsr
SUNWcsu
SUNWdtrc
SUNWesu
SUNWhea
SUNWib
SUNWibsdpib
SUNWipfh
SUNWipfu
SUNWmdb
SUNWmdbr
SUNWnxge
SUNWos86r
SUNWrds
SUNWroute
SUNWtavor
Unmounting the BE <s10u6_recpatches>.
The patch add to the BE <s10u6_recpatches> completed.

Nach dem erfolgreichen Patchen nun also vom neuen BE starten…

bash-3.00# luactivate s10u6_recpatches
System has findroot enabled GRUB
Generating boot-sign, partition and slice information for PBE <s10x_u6wos_07b>
Saving existing file </etc/bootsign> in top level dataset for BE <s10x_u6wos_07b> as <mount-point>//etc/bootsign.prev.
A Live Upgrade Sync operation will be performed on startup of boot environment <s10u6_recpatches>.

Generating boot-sign for ABE <s10u6_recpatches>
Saving existing file </etc/bootsign> in top level dataset for BE <s10u6_recpatches> as <mount-point>//etc/bootsign.prev.
Generating partition and slice information for ABE <s10u6_recpatches>
Copied boot menu from top level dataset.
Generating multiboot menu entries for PBE.
Generating multiboot menu entries for ABE.
Disabling splashimage
Re-enabling splashimage
No more bootadm entries. Deletion of bootadm entries is complete.
GRUB menu default setting is unaffected
Done eliding bootadm entries.

**********************************************************************

The target boot environment has been activated. It will be used when you
reboot. NOTE: You MUST NOT USE the reboot, halt, or uadmin commands. You
MUST USE either the init or the shutdown command when you reboot. If you
do not use either init or shutdown, the system will not boot using the
target BE.

**********************************************************************

In case of a failure while booting to the target BE, the following process
needs to be followed to fallback to the currently working boot environment:

1. Boot from Solaris failsafe or boot in single user mode from the Solaris
Install CD or Network.

2. Mount the Parent boot environment root slice to some directory (like
/mnt). You can use the following command to mount:

mount -Fzfs /dev/dsk/c1t0d0s0 /mnt

3. Run <luactivate> utility with out any arguments from the Parent boot
environment root slice, as shown below:

/mnt/sbin/luactivate

4. luactivate, activates the previous working boot environment and
indicates the result.

5. Exit Single User mode and reboot the machine.

**********************************************************************

Modifying boot archive service
Propagating findroot GRUB for menu conversion.
File </etc/lu/installgrub.findroot> propagation successful
File </etc/lu/stage1.findroot> propagation successful
File </etc/lu/stage2.findroot> propagation successful
File </etc/lu/GRUB_capability> propagation successful
Deleting stale GRUB loader from all BEs.
File </etc/lu/installgrub.latest> deletion successful
File </etc/lu/stage1.latest> deletion successful
File </etc/lu/stage2.latest> deletion successful
Activation of boot environment <s10u6_recpatches> successful.

bash-3.00# lustatus
Boot Environment           Is       Active Active    Can    Copy
Name                       Complete Now    On Reboot Delete Status
————————– ——– —— ——— —— ———-
s10x_u6wos_07b             yes      yes    no        no     -
s10u6_recpatches           yes      no     yes       no     -

bash-3.00# init 6
updating /platform/i86pc/boot_archive
…

Achtung: Es muss zwingend mit init oder shutdown neu gestartet werden!

bash-3.00# lustatus
Boot Environment           Is       Active Active    Can    Copy
Name                       Complete Now    On Reboot Delete Status
————————– ——– —— ——— —— ———-
s10x_u6wos_07b             yes      no     no        yes    -
s10u6_recpatches           yes      yes    yes       no     -

bash-3.00# zoneadm list -cv
ID NAME             STATUS     PATH                           BRAND    IP
0 global           running    /                              native   shared
- zone1            configured /zone1                         native   shared

bash-3.00# zpool import zone1

bash-3.00# zpool list
NAME      SIZE   USED AVAIL    CAP HEALTH ALTROOT
patches 7.94G 2.69G 5.25G    33% ONLINE -
rpool    7.94G 6.36G 1.58G    80% ONLINE -
zone1    1.98G   547M 1.45G    26% ONLINE -

bash-3.00# metaset -s zone1data -t

bash-3.00# metaset
Set name = zone1data, Set number = 1
Host                Owner
horst1
horst2             Yes
Drive    Dbase
c2t1d0   Yes
c3t1d0   Yes

Patchen der Zone mit ugrade-on-attach

bash-3.00# zoneadm -z zone1 attach
These patches installed on the source system are inconsistent with this system:
118668: version mismatch
(17) (19)
118669: version mismatch
(17) (19)
119060: version mismatch
(44) (45)
119091: version mismatch
(31) (32)
119214: version mismatch
(17) (18)
119247: version mismatch
(34) (35)
119253: version mismatch
(29) (31)
119255: version mismatch
(59) (65)
119314: version mismatch
(24) (26)
119758: version mismatch
(12) (14)
119784: version mismatch
(07) (10)
120095: version mismatch
(21) (22)
120200: version mismatch
(14) (15)
120223: version mismatch
(29) (31)
120273: version mismatch
(23) (25)
120411: version mismatch
(29) (30)
120544: version mismatch
(11) (14)
120740: version mismatch
(04) (05)
121119: version mismatch
(13) (15)
121309: version mismatch
(14) (16)
121395: version mismatch
(01) (03)
122213: version mismatch
(28) (32)
122912: version mismatch
(13) (15)
123896: version mismatch
(05) (10)
124394: version mismatch
(08) (09)
124629: version mismatch
(09) (10)
124631: version mismatch
(19) (24)
125165: version mismatch
(12) (13)
125185: version mismatch
(08) (11)
125333: version mismatch
(03) (05)
125540: version mismatch
(04) (06)
125720: version mismatch
(24) (28)
125732: version mismatch
(02) (04)
125953: version mismatch
(17) (18)
126364: version mismatch
(06) (07)
126366: version mismatch
(12) (14)
126420: version mismatch
(01) (02)
126539: version mismatch
(01) (02)
126869: version mismatch
(02) (03)
136883: version mismatch
(01) (02)
137122: version mismatch
(03) (06)
137128: version mismatch
(02) (05)
138224: version mismatch
(02) (03)
138242: version mismatch
(01) (05)
138254: version mismatch
(01) (02)
138264: version mismatch
(02) (03)
138286: version mismatch
(01) (02)
138372: version mismatch
(02) (06)
138628: version mismatch
(02) (07)
138857: version mismatch
(01) (02)
138867: version mismatch
(01) (02)
138882: version mismatch
(01) (02)
These patches installed on this system were not installed on the source system:
125556-02
138889-08
139100-01
139463-02
139482-01
139484-05
139499-04
139501-02
139561-02
139580-02
140145-01
140384-01
140456-01
140775-03
141009-01
141015-01

bash-3.00# zoneadm -z zone1 attach -u
Getting the list of files to remove
Removing 1209 files
Remove 198 of 198 packages
Installing 1315 files
Add 198 of 198 packages
Updating editable files
The file </var/sadm/system/logs/update_log> within the zone contains a log of the zone update.

bash-3.00# zoneadm list -cv
ID NAME             STATUS     PATH                           BRAND    IP
0 global           running    /                              native   shared
- zone1            installed /zone1                         native   shared

bash-3.00# zoneadm -z zone1 boot

bash-3.00# zlogin zone1
[Connected to zone 'zone1' pts/4]
Last login: Thu Apr 9 09:06:23 on pts/5
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
#
# exit
[Connection to zone 'zone1' pts/4 closed]

Upgrade-on-attach zum Patchen der Zone hat hier wunder geklappt.

weiterer Test nach Einspielen des recommended patch clusters

Nachdem nun Solaris10u6 mit neuestem recommended patch cluster installiert ist möchte ich das Liveupgrade inclusive Zone nochmals testen.

bash-3.00# zoneadm list -cv
ID NAME             STATUS     PATH                           BRAND    IP
0 global           running    /                              native   shared
2 zone1            running    /zone1                         native   shared

bash-3.00# lucreate -n s10u6_zonetest
Checking GRUB menu…
System has findroot enabled GRUB
Analyzing system configuration.
Comparing source boot environment <s10u6_recpatches> file systems with the
file system(s) you specified for the new boot environment. Determining
which file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <s10u6_zonetest>.
Source boot environment is <s10u6_recpatches>.
Creating boot environment <s10u6_zonetest>.
Cloning file systems from boot environment <s10u6_recpatches> to create boot environment <s10u6_zonetest>.
Creating snapshot for <rpool/ROOT/s10u6_recpatches> on <rpool/ROOT/s10u6_recpatches@s10u6_zonetest>.
Creating clone for <rpool/ROOT/s10u6_recpatches@s10u6_zonetest> on <rpool/ROOT/s10u6_zonetest>.
Setting canmount=noauto for </> in zone <global> on <rpool/ROOT/s10u6_zonetest>.
Creating snapshot for <zone1> on <zone1@s10u6_zonetest>.
cannot create ‘.’: missing dataset name
Creating clone for <zone1@s10u6_zonetest> on <zone1-s10u6_zonetest>.
ERROR: cannot create ‘zone1-s10u6_zonetest’: missing dataset name
ERROR: Unable to clone <> on <>.
/usr/lib/lu/luclonefs: zone1@s10u6_zonetest: not found
cannot open ‘zone1-s10u6_zonetest’: dataset does not exist
cannot open ‘zone1-s10u6_zonetest’: dataset does not exist
cannot open ‘zone1-s10u6_zonetest’: dataset does not exist
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <s10x_u6wos_07b> as <mount-point>//boot/grub/menu.lst.prev.
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <s10u6_zonetest> as <mount-point>//boot/grub/menu.lst.prev.
File </boot/grub/menu.lst> propagation successful
Copied GRUB menu from PBE to ABE
No entry for BE <s10u6_zonetest> in GRUB menu
Population of boot environment <s10u6_zonetest> successful.
Creation of boot environment <s10u6_zonetest> successful.
bash-3.00#

bash-3.00# ludelete -n s10u6_zonetest -f
System has findroot enabled GRUB
No entry for BE <s10u6_zonetest> in GRUB menu
Determining the devices to be marked free.
Updating boot environment configuration database.
Updating compare databases on boot environment <s10x_u6wos_07b>.
Updating boot environment description database on all BEs.
Updating all boot environment configuration databases.
Boot environment <s10u6_zonetest> deleted.

bash-3.00# zfs destroy zone1@s10u6_zonetest

Tja, auch nach Installieren der aktuell empfohlen Patches klappt das nicht wie gewünscht.

Hat jemand zu diesem Thema eigene Erfahrungen oder Workarounds? Auf Kommentare oder Tips würde ich mich freuen…

Comments Kommentare deaktiviert

05 04 2009

flying zones für Arme im Eigenbau mit Solaris10 und Vmware Server 2

Geschrieben von otmanix in EMC, NAS, SAN, Solaris, VMware, Virtualisierung, tags: Container, disk set, Solaris, svm, UFS, VMware, ZFS, zones

Solaris Zones / Container

Sun Microsystems hat Solaris10 eine interessante OS-Virtualisierungslösung kostenlos beigelegt – Solaris Zones, ähnlich zu BSD jails. Im Gegensatz zu XVM (Xen im Solaris-Kernel für X86) oder Logical Domains (Hypervisor für CMT/Niagara) gibt es bei Zones kaum Overhead durch die Virtualisierung. Zudem steht es sowohl im Sparc- als auch im X86-Umfeld zur Verfügung. In einer Zone werden Resourcen der sog. “globalen Zone” genutzt. Es gibt aber auch z.T. die Möglichkeit dediziert Resourcen zuzuweisen, z.B. einen eigenen IP-Stack. Den OS-Kernel hingegen gibt es nur einmal. Die Kombination von OS-Virtualisierung mit Zones und dem Resourcemanagement wird als Container bezeichnet.

Container werden i.d.R. genutzt um Applikationen oder Applikationsschichten voneinander abzuschotten und die Resourcenverteilung zu steuern. So kann ein Container ein SAP ERP Entwicklungs- und Testsystem beinhalten und ein weiterer das Produktionssystem. Die Systeme haben je eine eigene Netzwerkkonfiguration und können weiche oder harten Grenzen für CPU-Auslastung und Speicherverbrauch besitzen.

flying zones

Heruntergefahrene Zonen kann man klonen oder exportieren. Kopiert man die Filesysteme der Zone auf einen anderen Rechner kann man sie dort importieren und die Zone wieder in Betrieb nehmen. Legt man die Filesysteme auf shared storage kann man durch Zuweisen der relevanten Disks auf allen relevanten Rechnern die Filesysteme je nach Bedarf am passenden System in Betrieb nehmen. Danach kann auch die Zone dort wieder in Betrieb genommen werden. Das Verfahren nennt man Zonenmigration. Das wird genutzt um bei Rechnerausfällen Zonen umzuziehen oder um eine bessere Auslastung der vorhandenen Systeme zu erzielen. Als Basis für den Umzug der Filesysteme kann sowohl ZFS als auch UFS auf shared disk sets genutzt werden.

Möchte man den Umzug von Zonen auf andere Rechner automatisieren, die Verfügbarkeit der Zonen/Rechner überwachen lassen und automische Reaktionen in Problemfällen haben, dann kann man den Sun Cluster 3.2 mit dem Zonenagent einsetzen.

Sun verkauft die Implementierung einer solchen Gesamtlösung unter dem Titel “flying zones“. Dabei wird noch das Monitoringtool N1AA Analyzer beigelegt. Dort kann man z.B. den Resourcenverbrauch von best. Zonen aufsummieren lassen und prüfen, ob das denn so zusammen auf einer best. Hardware laufen würde. Außerdem wird einem noch das Softwareinstallationssystem N1AA ans Herz gelegt.

flying zones für Arme im Eigenbau

Im kostenlosen Vmware Server 2.01 auf meinem PC habe ich eine Testumgebung aufgebaut um die Grundzüge von flying zones nachzustellen und zu testen. Wichtig war mir eine realistische Umgebung wie im Betriebsalltag, deshalb bin ich von 2 virt. Rechenzentren ausgegangen. In jedem virt. RZ befindet sich ein Solaris-Host und ein Storagesystem. Auf das Storagesystem jedes RZs kann jeder Server zugreifen. Die Platten im Storagesystem sind als shared disks konfiguriert. Es soll mit host based mirroring erreicht werden, dass trotz Ausfall eines kompletten Storagesystems den Betrieb der Zone nicht gestört wird, egal auf welchem host die Zone aktiv läuft. Auf den Einsatz kostenpflichtiger Clustersoftware zur Automatisierung verzichte ich in diesem Test.

In der Testumgebung gibt es nur eine Zone. In der Realität wären das natürlich mehr.

Auf jedem Solaris-Host ist Solaris10u6 (10/08) installiert. Dabei wurde ein lokale Platte genutzt um darauf das OS zu installieren. Dabei wurde bereits die neue Funktionalität genutzt ZFS als Rootfilesystem einzusetzen. Eine weitere kleine lokale Platte steht darüber hinaus zur Verfügung. Auf die Grundinstallation der Solaris-hosts gehe ich hier nicht näher ein. Die shared disks sind ebenfalls bereits den hosts bereitgestellt.

Testumgebung auf Vmware Server 2.01

Am Vmware Server ist eigentlich nur die Konfiguration der shared disks interessant. Die Disks werden zunächst in einer virt. Maschine erstellt, dann deren vmx-Dateien angepasst und die relevanten Teile der vmx-Datei in die des anderen hosts übertragen.

Benötigt werden also folgende Platten:

lokale disks pro System:

1 Disk mit >= 5GB für den ZFS-RootPool
1 Disk >= 20MB für die lokale State Database

shared disks (insgesamt):

2 shared Disks (preaallocated) für Zonen-Root (ZFS) 2GB
2 shared Disks (preaallocated) mit Zonen-Daten (UFS) 50MB

relevanter Teil der vmx-Dateien:

scsi1.present = "TRUE"
scsi1.sharedBus = "virtual"
scsi1.virtualDev = "lsilogic"

scsi1:0.present = "TRUE"
scsi1:0.fileName = "D:\Virtual Machines\ext1disk1.vmdk"
scsi1:0.writeThrough = "TRUE"
scsi1:0.mode = "independent-persistent"

scsi1:1.present = "TRUE"
scsi1:1.fileName = "D:\Virtual Machines\ext1disk2.vmdk"
scsi1:1.writeThrough = "TRUE"
scsi1:1.mode = "independent-persistent"

scsi2.present = "TRUE"
scsi2.sharedBus = "virtual"
scsi2.virtualDev = "lsilogic"

scsi2:0.present = "TRUE"
scsi2:0.fileName = "D:\Virtual Machines\ext2disk1.vmdk"
scsi2:0.writeThrough = "TRUE"
scsi2:0.mode = "independent-persistent"

scsi2:1.present = "TRUE"
scsi2:1.fileName = "D:\Virtual Machines\ext2disk2.vmdk"
scsi2:1.writeThrough = "TRUE"
scsi2:1.mode = "independent-persistent"

disk.locking = "FALSE"

Hier ein Blick auf das System nach der Solaris-Installation:

bash-3.00# zpool list
NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
rpool  7.94G  4.65G  3.28G    58%  ONLINE  -

bash-3.00# zpool status rpool
pool: rpool
state: ONLINE
scrub: none requested
config:
NAME        STATE     READ WRITE CKSUM
rpool       ONLINE       0     0     0
c1t0d0s0  ONLINE       0     0     0
errors: No known data errors

bash-3.00# zfs list
NAME                        USED  AVAIL  REFER  MOUNTPOINT
rpool                      5.15G  2.67G  35.5K  /rpool
rpool/ROOT                 3.77G  2.67G    18K  legacy
rpool/ROOT/s10x_u6wos_07b  3.77G  2.67G  3.77G  /
rpool/dump                  900M  2.67G   900M  -
rpool/export                 37K  2.67G    19K  /export
rpool/export/home            18K  2.67G    18K  /export/home
rpool/swap                  512M  3.16G  5.54M  -

bash-3.00# df -h
Filesystem             size   used  avail capacity  Mounted on
rpool/ROOT/s10x_u6wos_07b 7.8G   3.8G   2.7G    59%    /
/devices                 0K     0K     0K     0%    /devices
ctfs                     0K     0K     0K     0%    /system/contract
proc                     0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
swap                   532M   364K   532M     1%    /etc/svc/volatile
objfs                    0K     0K     0K     0%    /system/object
sharefs                  0K     0K     0K     0%    /etc/dfs/sharetab
/usr/lib/libc/libc_hwcap2.so.1 6.4G   3.8G   2.7G    59%    /lib/libc.so.1
fd                       0K     0K     0K     0%    /dev/fd
swap                   535M   2.7M   532M     1%    /tmp
swap                   532M    32K   532M     1%    /var/run
rpool/export           7.8G    19K   2.7G     1%    /export
rpool/export/home      7.8G    18K   2.7G     1%    /export/home
rpool                  7.8G    35K   2.7G     1%    /rpool
/hgfs                   16G   4.0M    16G     1%    /hgfs
/tmp/VMwareDnD           0K     0K     0K     0%    /var/run/vmblock

bash-3.00# swap -l
swapfile             dev  swaplo blocks   free
/dev/zvol/dsk/rpool/swap 181,1       8 1048568 1047280

Arbeiten mit den shared disks

ZFS für Zonenroot, RAID1 gespiegelt

bash-3.00# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <DEFAULT cyl 4092 alt 2 hd 128 sec 32>
/pci@0,0/pci15ad,1976@10/sd@0,0
1. c1t1d0 <DEFAULT cyl 47 alt 2 hd 64 sec 32>
/pci@0,0/pci15ad,1976@10/sd@1,0
2. c2t0d0 <VMware,-VMware Virtual S-1.0-2.00GB>
/pci@0,0/pci15ad,790@11/pci15ad,1976@0/sd@0,0
3. c2t1d0 <DEFAULT cyl 47 alt 2 hd 64 sec 32>
/pci@0,0/pci15ad,790@11/pci15ad,1976@0/sd@1,0
4. c3t0d0 <VMware,-VMware Virtual S-1.0-2.00GB>
/pci@0,0/pci15ad,790@11/pci15ad,1976@1/sd@0,0
5. c3t1d0 <DEFAULT cyl 47 alt 2 hd 64 sec 32>
/pci@0,0/pci15ad,790@11/pci15ad,1976@1/sd@1,0
Specify disk (enter its number): 0
selecting c1t0d0
[disk formatted]
/dev/dsk/c1t0d0s0 is part of active ZFS pool rpool. Please see zpool(1M).
/dev/dsk/c1t0d0s2 is part of active ZFS pool rpool. Please see zpool(1M).

bash-3.00# zpool create zone1 mirror c2t0d0 c3t0d0
bash-3.00# zpool list zone1
NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
zone1  1.98G    94K  1.98G     0%  ONLINE  -

bash-3.00# zpool status zone1
pool: zone1
state: ONLINE
scrub: none requested
config:
NAME        STATE     READ WRITE CKSUM
zone1       ONLINE       0     0     0
mirror    ONLINE       0     0     0
c2t0d0  ONLINE       0     0     0
c3t0d0  ONLINE       0     0     0
errors: No known data errors

bash-3.00# zfs list
NAME                        USED  AVAIL  REFER  MOUNTPOINT
rpool                      5.15G  2.67G  35.5K  /rpool
rpool/ROOT                 3.77G  2.67G    18K  legacy
rpool/ROOT/s10x_u6wos_07b  3.77G  2.67G  3.77G  /
rpool/dump                  900M  2.67G   900M  -
rpool/export                 37K  2.67G    19K  /export
rpool/export/home            18K  2.67G    18K  /export/home
rpool/swap                  512M  3.16G  5.54M  -
zone1                       106K  1.95G    18K  /zone1

Datenbereich mit UFS-Filesystem auf SVM shared disk set, RAID1 gespiegelt

bash-3.00# metaset -s zone1data -a c2t1d0 c3t1d0 -h horst1 horst2
metaset: horst1: there are no existing databases

Es existiert noch keine lokale state database. Deshalb auf horst1 und horst2 die zweite lokale Platte partitionieren und in der Slice7 eine lokale State Database anlegen.

bash-3.00# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <DEFAULT cyl 4092 alt 2 hd 128 sec 32>
/pci@0,0/pci15ad,1976@10/sd@0,0
1. c1t1d0 <DEFAULT cyl 47 alt 2 hd 64 sec 32>
/pci@0,0/pci15ad,1976@10/sd@1,0
2. c2t0d0 <VMware,-VMware Virtual S-1.0-2.00GB>
/pci@0,0/pci15ad,790@11/pci15ad,1976@0/sd@0,0
3. c2t1d0 <DEFAULT cyl 47 alt 2 hd 64 sec 32>
/pci@0,0/pci15ad,790@11/pci15ad,1976@0/sd@1,0
4. c3t0d0 <VMware,-VMware Virtual S-1.0-2.00GB>
/pci@0,0/pci15ad,790@11/pci15ad,1976@1/sd@0,0
5. c3t1d0 <DEFAULT cyl 47 alt 2 hd 64 sec 32>
/pci@0,0/pci15ad,790@11/pci15ad,1976@1/sd@1,0
Specify disk (enter its number): 1
selecting c1t1d0
[disk formatted]
FORMAT MENU:
disk       - select a disk
type       - select (define) a disk type
partition  - select (define) a partition table
current    - describe the current disk
format     - format and analyze the disk
fdisk      - run the fdisk program
repair     - repair a defective sector
label      - write label to the disk
analyze    - surface analysis
defect     - defect list management
backup     - search for backup labels
verify     - read and display labels
save       - save new disk/partition definitions
inquiry    - show vendor, product and revision
volname    - set 8-character volume name
!<cmd>     - execute <cmd>, then return
format> fdisk
No fdisk table exists. The default partition for the disk is:
a 100% "SOLARIS System" partition
Type "y" to accept the default partition,  otherwise type "n" to edit the
partition table.
y
quit
format> part
PARTITION MENU:
0      - change `0' partition
1      - change `1' partition
2      - change `2' partition
3      - change `3' partition
4      - change `4' partition
5      - change `5' partition
6      - change `6' partition
7      - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name   - name the current table
print  - display the current table
label  - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition> print
Current partition table (original):
Total disk cylinders available: 46 + 2 (reserved cylinders)
Part      Tag    Flag     Cylinders      Size            Blocks
0 unassigned    wm       0             0         (0/0/0)      0
1 unassigned    wm       0             0         (0/0/0)      0
2     backup    wu       0 - 45       46.00MB    (46/0/0) 94208
3 unassigned    wm       0             0         (0/0/0)      0
4 unassigned    wm       0             0         (0/0/0)      0
5 unassigned    wm       0             0         (0/0/0)      0
6 unassigned    wm       0             0         (0/0/0)      0
7 unassigned    wm       0             0         (0/0/0)      0
8       boot    wu       0 -  0        1.00MB    (1/0/0)   2048
9 unassigned    wm       0             0         (0/0/0)      0
partition> 7
Part      Tag    Flag     Cylinders      Size            Blocks
7 unassigned    wm       0             0         (0/0/0)      0
Enter partition id tag[unassigned]:
Enter partition permission flags[wm]:
Enter new starting cyl[0]:
Enter partition size[0b, 0c, 0e, 0.00mb, 0.00gb]: 46c
partition> print
Current partition table (unnamed):
Total disk cylinders available: 46 + 2 (reserved cylinders)
Part      Tag    Flag     Cylinders      Size            Blocks
0 unassigned    wm       0             0         (0/0/0)      0
1 unassigned    wm       0             0         (0/0/0)      0
2     backup    wu       0 - 45       46.00MB    (46/0/0) 94208
3 unassigned    wm       0             0         (0/0/0)      0
4 unassigned    wm       0             0         (0/0/0)      0
5 unassigned    wm       0             0         (0/0/0)      0
6 unassigned    wm       0             0         (0/0/0)      0
7 unassigned    wm       0 - 45       46.00MB    (46/0/0) 94208
8       boot    wu       0 -  0        1.00MB    (1/0/0)   2048
9 unassigned    wm       0             0         (0/0/0)      0
partition> label
Ready to label disk, continue? y
partition> quit
FORMAT MENU:
disk       - select a disk
type       - select (define) a disk type
partition  - select (define) a partition table
current    - describe the current disk
format     - format and analyze the disk
fdisk      - run the fdisk program
repair     - repair a defective sector
label      - write label to the disk
analyze    - surface analysis
defect     - defect list management
backup     - search for backup labels
verify     - read and display labels
save       - save new disk/partition definitions
inquiry    - show vendor, product and revision
volname    - set 8-character volume name
!<cmd>     - execute <cmd>, then return
quit
format> quit
bash-3.00#

bash-3.00# metadb -a -f c1t1d0s7

bash-3.00# metadb
flags           first blk       block count
a        u         16              8192            /dev/dsk/c1t1d0s7
bash-3.00# echo "set md:mirrored_root_flag=1" >> /etc/system

Auf horst1 nun das shared disk set anlegen.

bash-3.00# metaset -s zone1data -a -h horst1 horst2
metaset: horst2: rpc.metad: Permission denied

Dem Dienst fehlen die Berechtigungen.

Auf horst1

bash-3.00# echo horst2 > /.rhosts

Auf horst2

bash-3.00# echo horst1 > /.rhosts

Auf horst1 nun das shared disk set erstellen:

bash-3.00# metaset -s zone1data -a -h horst1 horst2

bash-3.00# metaset -s zone1data -a c2t1d0 c3t1d0

bash-3.00# metaset
Set name = zone1data, Set number = 1
Host                Owner
horst1             Yes
horst2
Drive    Dbase
c2t1d0   Yes
c3t1d0   Yes

bash-3.00# metadb -s zone1data
flags           first blk       block count
a        u         16              8192            /dev/dsk/c2t1d0s7
a        u         16              8192            /dev/dsk/c3t1d0s7

Nun die RAID1-Spiegelung mit Solaris Volummanager (SVM) aufsetzen:

bash-3.00# metainit -s zone1data d11 1 1 c2t1d0s0
zone1data/d11: Concat/Stripe is setup

bash-3.00# metainit -s zone1data d12 1 1 c3t1d0s0
zone1data/d12: Concat/Stripe is setup

bash-3.00# metainit -s zone1data d10 -m d11
zone1data/d10: Mirror is setup

bash-3.00# metattach -s zone1data d10 d12
zone1data/d10: submirror zone1data/d12 is attached

bash-3.00# metastat -s zone1data
zone1data/d10: Mirror
Submirror 0: zone1data/d11
State: Okay
Submirror 1: zone1data/d12
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 86016 blocks (42 MB)
zone1data/d11: Submirror of zone1data/d10
State: Okay
Size: 86016 blocks (42 MB)
Stripe 0:
Device     Start Block  Dbase        State Reloc Hot Spare
c2t1d0s0          0     No            Okay   Yes
zone1data/d12: Submirror of zone1data/d10
State: Okay
Size: 86016 blocks (42 MB)
Stripe 0:
Device     Start Block  Dbase        State Reloc Hot Spare
c3t1d0s0          0     No            Okay   Yes
Device Relocation Information:
Device   Reloc  Device ID
c3t1d0   Yes    id1,sd@f0000000049d7b0e80006e5c10004
c2t1d0   Yes    id1,sd@f0000000049d7b0e80004846b0003

Im Anschluss die Platte mit UFS formatieren:

bash-3.00# newfs /dev/md/zone1data/rdsk/d10
/dev/md/zone1data/rdsk/d10: Unable to find Media type. Proceeding with system determined parameters.
newfs: construct a new file system /dev/md/zone1data/rdsk/d10: (y/n)? y
/dev/md/zone1data/rdsk/d10:     86016 sectors in 42 cylinders of 64 tracks, 32 sectors
42.0MB in 3 cyl groups (16 c/g, 16.00MB/g, 7680 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 32832, 65632,

Konfiguration und Installation der Zone zone1

bash-3.00# zonecfg -z zone1
zone1: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:zone1> create
zonecfg:zone1> set zonepath=/zone1
zonecfg:zone1> set autoboot=false
zonecfg:zone1> add fs
zonecfg:zone1:fs> set dir=/daten
zonecfg:zone1:fs> set special=/dev/md/zone1data/dsk/d10
zonecfg:zone1:fs> set raw=/dev/md/zone1data/rdsk/d10
zonecfg:zone1:fs> set type=ufs
zonecfg:zone1:fs> end
zonecfg:zone1> add net
zonecfg:zone1:net> set physical=e100g0
zonecfg:zone1:net> set address=192.168.178.61
zonecfg:zone1:net> end
zonecfg:zone1> exit

bash-3.00# zoneadm list -c
global
zone1

bash-3.00# cat /etc/zones/index
# Copyright 2004 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#
# ident "@(#)zones-index        1.2     04/04/01 SMI"
#
# DO NOT EDIT: this file is automatically generated by zoneadm(1M)
# and zonecfg(1M).  Any manual changes will be lost.
#
global:installed:/
zone1:configured:/zone1:

bash-3.00# cat /etc/zones/zone1.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN" "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1">
<!--
DO NOT EDIT THIS FILE.  Use zonecfg(1M) instead.
-->
<zone name="zone1" zonepath="/zone1" autoboot="false">
<inherited-pkg-dir directory="/lib"/>
<inherited-pkg-dir directory="/platform"/>
<inherited-pkg-dir directory="/sbin"/>
<inherited-pkg-dir directory="/usr"/>
<filesystem special="/dev/md/zone1data/dsk/d10" raw="/dev/md/zone1data/rdsk/d10" directory="/daten" type="ufs"/>
<network address="192.168.178.61" physical="e100g0"/>
</zone>

bash-3.00# chmod 700 /zone1

bash-3.00# zoneadm -z zone1 install
Preparing to install zone <zone1>.
Checking <ufs> file system on device </dev/md/zone1data/rdsk/d10> to be mounted at </zone1/root>
Creating list of files to copy from the global zone.
Copying <8135> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1186> packages on the zone.
Initialized <1186> packages on zone.
Zone <zone1> is initialized.
The file </zone1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.

bash-3.00# zoneadm list -cv
ID NAME             STATUS     PATH                           BRAND    IP
0 global           running    /                              native   shared
- zone1            installed  /zone1                         native   shared

bash-3.00# zoneadm -z zone1 boot

bash-3.00# zlogin -C zone1
[Connected to zone 'zone1' console]
143/143
Reading ZFS config: done.
Select a Language
0. English
1. German
2. es
3. fr
Please make a choice (0 - 3), or press h or ? for help:1
...
Auf welcher Art von Terminal arbeiten Sie?
1) ANSI Standard CRT
2) DEC VT52
3) DEC VT100
4) Heathkit 19
5) Lear Siegler ADM31
6) PC-Konsole
7) Sun-Kommando-Shell
  Sun-Workstation
9) Televideo 910
10) Televideo 925
11) Wyse Modell 50
12) X Terminal Emulator (xterms)
13) CDE Terminal Emulator (dtterm)
14) Andere
Geben Sie die gewünschte Zahl ein und drücken Sie Eingabetaste: 3
...
System identification is completed.
rebooting system due to change(s) in /etc/default/init
[NOTICE: Zone rebooting]
SunOS Release 5.10 Version Generic_137138-09 64-bit
Copyright 1983-2008 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Hostname: zone1
Reading ZFS config: done.
zone1 console login: Apr  5 13:33:22 zone1 sendmail[6008]: My unqualified host name (localhost) unknown; sleeping for retry
root
Password:
Apr  5 13:33:44 zone1 login: ROOT LOGIN /dev/console
Sun Microsystems Inc.   SunOS 5.10      Generic January 2005

# svcadm disable svc:*sendmail*

bash-3.00# df -h
Dateisystem           Größe belegt verfügbar Kapazität Eingehängt auf
/                        0K   541M   1,4G    28%    /
/daten                  39M   1,0M    34M     3%    /daten
/dev                   2,0G   541M   1,4G    28%    /dev
/lib                   6,4G   3,8G   2,7G    59%    /lib
/platform              6,4G   3,8G   2,7G    59%    /platform
/sbin                  6,4G   3,8G   2,7G    59%    /sbin
/usr                   6,4G   3,8G   2,7G    59%    /usr
proc                     0K     0K     0K     0%    /proc
ctfs                     0K     0K     0K     0%    /system/contract
mnttab                   0K     0K     0K     0%    /etc/mnttab
objfs                    0K     0K     0K     0%    /system/object
swap                   452M   316K   452M     1%    /etc/svc/volatile
/usr/lib/libc/libc_hwcap2.so.1 6,4G   3,8G   2,7G    59%    /lib/libc.so.1
fd                       0K     0K     0K     0%    /dev/fd
swap                   452M    36K   452M     1%    /tmp
swap                   452M    12K   452M     1%    /var/run
bash-3.00# exit
# ^D
zone1 console login: ~.
[Connection to zone 'zone1' console closed]

Zonenmigration

Zone exportieren

bash-3.00# zlogin zone1 init 0

bash-3.00# zoneadm list -cv
ID NAME             STATUS     PATH                           BRAND    IP
0 global           running    /                              native   shared
- zone1            installed  /zone1                         native   shared

bash-3.00# zoneadm -z zone1 detach
bash-3.00# zoneadm list -cv
ID NAME             STATUS     PATH                           BRAND    IP
0 global           running    /                              native   shared
- zone1            configured /zone1                         native   shared

bash-3.00# ls -l /zone1
total 3343
-rw-r--r--   1 root     root     1618163 Apr  5 14:25 SUNWdetached.xml
drwxr-xr-x  13 root     root          52 Apr  5 14:22 dev
drwxr-xr-x  19 root     root          21 Apr  5 13:44 root

ZFS-Pool mit Zonenroot exportieren

bash-3.00# zpool export zone1

bash-3.00# zpool list
NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
rpool  7.94G  5.02G  2.92G    63%  ONLINE  -

SVM disk set mit UFS-Filesystem für Daten exportieren

bash-3.00# metaset
Set name = zone1data, Set number = 1
Host                Owner
horst1             Yes
horst2
Drive    Dbase
c2t1d0   Yes
c3t1d0   Yes

bash-3.00# metaset -s zone1data -r

bash-3.00# metaset
Set name = zone1data, Set number = 1
Host                Owner
horst1
horst2
Drive    Dbase
c2t1d0   Yes
c3t1d0   Yes

Auf horst2:

ZFS-Pool importieren

bash-3.00# zpool list
NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
rpool  7.94G  4.65G  3.28G    58%  ONLINE  -

bash-3.00# zpool import
pool: zone1
id: 12609083278336438915
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
zone1       ONLINE
mirror    ONLINE
c2t0d0  ONLINE
c3t0d0  ONLINE

bash-3.00# zpool import zone1

bash-3.00# zpool list
NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
rpool  7.94G  4.65G  3.28G    58%  ONLINE  -
zone1  1.98G   544M  1.45G    26%  ONLINE  -

SVM disk set importieren

bash-3.00# metaset
Set name = zone1data, Set number = 1
Host                Owner
horst1
horst2
Drive    Dbase
c2t1d0   Yes
c3t1d0   Yes

bash-3.00# metaset -s zone1data -t

bash-3.00# metaset
Set name = zone1data, Set number = 1
Host                Owner
horst1
horst2             Yes
Drive    Dbase
c2t1d0   Yes
c3t1d0   Yes

bash-3.00# metastat -s zone1data d10
zone1data/d10: Mirror
Submirror 0: zone1data/d11
State: Okay
Submirror 1: zone1data/d12
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 86016 blocks (42 MB)
zone1data/d11: Submirror of zone1data/d10
State: Okay
Size: 86016 blocks (42 MB)
Stripe 0:
Device     Start Block  Dbase        State Reloc Hot Spare
c2t1d0s0          0     No            Okay   Yes
zone1data/d12: Submirror of zone1data/d10
State: Okay
Size: 86016 blocks (42 MB)
Stripe 0:
Device     Start Block  Dbase        State Reloc Hot Spare
c3t1d0s0          0     No            Okay   Yes
Device Relocation Information:
Device   Reloc  Device ID
c2t1d0   Yes    id1,sd@f0000000049d7b0e80004846b0003
c3t1d0   Yes    id1,sd@f0000000049d7b0e80006e5c10004

Zone zone1 importieren und wieder in Betrieb nehmen:

bash-3.00# zonecfg -z zone1
zone1: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:zone1> create -a /zone1
zonecfg:zone1> exit

bash-3.00# zoneadm list -cv
ID NAME             STATUS     PATH                           BRAND    IP
0 global           running    /                              native   shared
- zone1            configured /zone1                         native   shared

bash-3.00# zoneadm -z zone1 attach

bash-3.00# zoneadm list -cv
ID NAME             STATUS     PATH                           BRAND    IP
0 global           running    /                              native   shared
- zone1            installed  /zone1                         native   shared

bash-3.00# zoneadm -z zone1 boot

bash-3.00# zoneadm list -cv
ID NAME             STATUS     PATH                           BRAND    IP
0 global           running    /                              native   shared
2 zone1            running    /zone1                         native   shared

bash-3.00# zlogin zone1
[Connected to zone 'zone1' pts/5]
Last login: Sun Apr  5 14:22:15 on pts/5
Sun Microsystems Inc.   SunOS 5.10      Generic January 2005

# df -h
Filesystem             size   used  avail capacity  Mounted on
/                        0K   545M   1.4G    28%    /
/daten                  39M   5.0M    30M    15%    /daten
/dev                   2.0G   545M   1.4G    28%    /dev
/lib                   6.4G   3.8G   2.7G    59%    /lib
/platform              6.4G   3.8G   2.7G    59%    /platform
/sbin                  6.4G   3.8G   2.7G    59%    /sbin
/usr                   6.4G   3.8G   2.7G    59%    /usr
proc                     0K     0K     0K     0%    /proc
ctfs                     0K     0K     0K     0%    /system/contract
mnttab                   0K     0K     0K     0%    /etc/mnttab
objfs                    0K     0K     0K     0%    /system/object
swap                   437M   300K   437M     1%    /etc/svc/volatile
/usr/lib/libc/libc_hwcap2.so.1 6.4G   3.8G   2.7G    59%    /lib/libc.so.1
fd                       0K     0K     0K     0%    /dev/fd
swap                   437M    36K   437M     1%    /tmp
swap                   437M    12K   437M     1%    /var/run

# ls -l /daten
total 8176
-rw-r--r--   1 root     root     4165061 Apr  5 14:14 lksf_book_alpha.pdf
drwx------   2 root     root        8192 Apr  5 12:13 lost+found

Fazit

Zonen sind ne nette Sache. Mit der Möglichkeit der Zonenmigration wird das Thema aber erst richtig interessant und RZ-tauglich.

Weiterführende Literatur, etc.

Solaris Volume Manager Administration Guide

ZFS Administration Guide

Solaris Containers

Devices and Filesystems

Solaris10u6 10/08

Blog O’Matty zu shared disks unter Vmware Server 2

P.S.

Der nächste Test wird Liveupgrade mit ZFS-Rootfilesystem und Zonen zum Thema haben…

Comments 3 Kommentare »

18 03 2009

Automatisiertes Schreiben von disk label unter Solaris

Geschrieben von otmanix in OpenSolaris, Solaris, tags: fmthard, format, OpenSolaris, prtvtoc, Solaris, svm

Wer unter Solaris mit UFS-Filesystemen arbeitet muss vor der Benutzung einer Platte selbige mit einem disk label (vtoc bzw. Partitionstabelle) versehen. Dazu startet man den Befehl “format”, wählt die gewünschte Disk aus, ändert unter “partition” die Größen für die Partitionen, speichert das mit “label” und beendet das Programm mit “quit”.

root@server # format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /ssm@0,0/pci@1a,700000/pci@1/SUNW,isptwo@4/sd@0,0
       1. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /ssm@0,0/pci@1b,700000/pci@1/SUNW,isptwo@4/sd@0,0
       2. c2t40d41 <EMC-SYMMETRIX-5772 cyl 49598 alt 2 hd 30 sec 128>
          /ssm@0,0/pci@1a,600000/pci@1/lpfc@4/sd@28,29
...

Specify disk (enter its number): 0
selecting c0t0d0
[disk formatted]

FORMAT MENU:
        disk       - select a disk
        type       - select (define) a disk type
        partition  - select (define) a partition table
        current    - describe the current disk
        format     - format and analyze the disk
        repair     - repair a defective sector
        label      - write label to the disk
        analyze    - surface analysis
        defect     - defect list management
        backup     - search for backup labels
        verify     - read and display labels
        save       - save new disk/partition definitions
        inquiry    - show vendor, product and revision
        volname    - set 8-character volume name
        !<cmd>     - execute <cmd>, then return
        quit
format> partition

PARTITION MENU:
        0      - change `0' partition
        1      - change `1' partition
        2      - change `2' partition
        3      - change `3' partition
        4      - change `4' partition
        5      - change `5' partition
        6      - change `6' partition
        7      - change `7' partition
        select - select a predefined table
        modify - modify a predefined partition table
        name   - name the current table
        print  - display the current table
        label  - write partition map and label to the disk
        !<cmd> - execute <cmd>, then return
        quit
partition> print
Current partition table (original):
Total disk cylinders available: 24620 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
  0       root    wm       0 -  6812        9.39GB    (6813/0/0)  19682757
  1       swap    wu    6813 - 21330       20.00GB    (14518/0/0) 41942502
  2     backup    wm       0 - 24619       33.92GB    (24620/0/0) 71127180
  3 unassigned    wm       0                0         (0/0/0)            0
  4 unassigned    wm       0                0         (0/0/0)            0
  5        var    wm   21331 - 24233        4.00GB    (2903/0/0)   8386767
  6 unassigned    wm   24234 - 24596      512.06MB    (363/0/0)    1048707
  7 unassigned    wm   24597 - 24619       32.44MB    (23/0/0)       66447

partition> quit

FORMAT MENU:
        disk       - select a disk
        type       - select (define) a disk type
        partition  - select (define) a partition table
        current    - describe the current disk
        format     - format and analyze the disk
        repair     - repair a defective sector
        label      - write label to the disk
        analyze    - surface analysis
        defect     - defect list management
        backup     - search for backup labels
        verify     - read and display labels
        save       - save new disk/partition definitions
        inquiry    - show vendor, product and revision
        volname    - set 8-character volume name
        !<cmd>     - execute <cmd>, then return
        quit
format> quit

Im Bereich “partition” kann man mit “print” die aktuelle Partitionstabelle ansehen. Bei neuen Platten wird ein Standardvorschlag zur Partitionierung angezeigt, der natürlich abgeändert werden kann. Wird dies nicht getan und trotzdem “label” ausgeführt, wird dieser default-label geschrieben.

Hat man nun die Aufgabe eine größere Anzahl Platten zu partitionieren möchte man dann den Vorgang doch irgendwie automatisieren. Dazu gibt es die Tools prtvtoc und fmthard. Mit prtvtoc kann die Partitionstabelle einer Platte als Text in genormter Form ausgegeben werden.

root@server # prtvtoc /dev/rdsk/c0t0d0s0

* /dev/rdsk/c0t0d0s2 partition map

* Dimensions:

*     512 bytes/sector

*     107 sectors/track

*      27 tracks/cylinder

*    2889 sectors/cylinder

*   24622 cylinders

*   24620 accessible cylinders

* Flags:

*   1: unmountable

*  10: read-only

*                          First     Sector    Last

* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory

       0      2    00          0  19682757  19682756

       1      3    01   19682757  41942502  61625258

       2      5    00          0  71127180  71127179

       5      7    00   61625259   8386767  70012025

       6      0    00   70012026   1048707  71060732

       7      0    00   71060733     66447  71127179

Diese Ausgabe läßt sich nun als Vorlage nutzen um Platten mit “fmthard” zu partitionieren. Sinn ergibt das natürlich nur bei Disks mit gleicher Größe.

prtvtoc /dev/rdsk/c0t0d0s2 | fmthard -s - /dev/rdsk/c1t0d0s2

Dummerweise bekommt man nun ziemlich wahrscheinlich einen I/O-error beim Schreiben der Partitionstabelle auf die zweite Platte (wenn diese neu ist). Hier des Rätsels Lösung:

manpage zu “fmthard”

For disks under one terabyte, fmthard cannot write a VTOC on an unlabeled disk. Use format(1M) for this purpose.
SunOS 5.10 Last change: 11 Apr 2005

Na klasse, da läßt sich das Tool zum Automatisieren in der Masse der Anwendungsfälle also nicht nutzen. Weniger bekannt ist der folgende Workaround:

Man automatisiert das Schreiben eines Standard disk label mit “Format” und benutzt im Anschluss wie oben gezeigt “prtvtoc” und “fmthard” (üblicherweise wird immer die Slice 2 angegeben, da diese per Definition die komplette Disk umfassen sollte!).

echo label > /tmp/input
echo quit >> /tmp/input
format -d c1t0d0  -f /tmp/input
prtvtoc /dev/rdsk/c0t0d0s2 | fmthard -s - /dev/rdsk/c1t0d0s2

Um eine größere Zahl Disks zu partitionieren schreibt man ein kleines Skript:

cd /dev/rdsk/
echo label > /tmp/input
echo quit >> /tmp/input
DISKS=$(ls c4t50d*s2|sed 's/s2//')
export DISKS
for i in $DISKS
do
format -d $i -f /tmp/input
done

In diesem Beispiel werden alle LUNs am Controller 4 / Target 50 mit einem Standard disk label versehen.

Danach kann man z.B. das Partitionslayout einer Platte auf alle neuen Platten übertragen:

for i in $DISKS
do
prtvtoc /dev/rdsk/c0t0d0s2 | fmthard -s - /dev/rdsk/${i}s2
done

Alternativ könnte man aber auch die neuen Platten einem Diskset hinzufügen:

for i in $DISKS
do
metaset -s oradb -a $i
done

P.S.

Die Skripte kann man natürlich noch schöner schreiben. Ich will hier nur das Prinzip zeigen…

Hier noch etwas Lesestoff: http://docs.sun.com/app/docs/doc/817-5093/disksprep-103?a=view

Comments Kommentare deaktiviert

01 05 2008

Parameter für SAP/Oracle-Testsystem auf Solaris10u5, EMC und ZFS

Geschrieben von otmanix in EMC, Oracle, SAN, Solaris, Storage, ZFS, tags: dmx, EMC, fc, mpxio, Solaris, svm, ZFS

- Anschluß EMC DMX-Speichersystem an Sun Fire V490
- Sun/Emulex-FC-HBAs an SAN-Switch
- UFS für / und swap auf internen FC-Disks
- Mirroring der Boot-Disk per SVM
- ZFS für EMC Disks
- Multpathing per mpxio
- Solaris 10 u5 enthält alle relevanten EMC und SAP/Oracle recommended Patches

Informationshilfen:
http://www.solarisinternals.com//wiki/index.php?title=Category:ZFS – ZFS tuning
http://www.sun.com/bigadmin/content/submitted/svm_mirroring.jsp – SVM Bootdisk Mirroring
http://powerlink.emc.com > EMC E-Lab-Navigator für Supportmatrix

E-Lab-Navigator Supportmatrix für EMC DMX und SF V490

Tools:

https://HOSTNAME:6789/zfs/zfsmodule/Index – ZFS Webgui

Installiertes Solaris-Release?
# cat /etc/release
Solaris 10 5/08 s10s_u5wos_10 SPARC
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 24 March 2008

Kernelparameter für SVM, ZFS, EMC, SAP/Oracle
# cat /etc/system

…
* Begin MDD root info (do not edit)
rootdev:/pseudo/md@0:0,10,blk
set md:mirrored_root_flag=1
* End MDD root info (do not edit)

* ZFS
* http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide

* disk-cache flush aus
set zfs:zfs_nocacheflush=1

* 4GB RAM max. fuer ZFS-Arc-Cache (0xWERT , WERT = MB*1024*1024 > HEX)
set zfs:zfs_arc_max=0×100000000

* File-Level-Prefetching
* set zfs:zfs_prefetch_disable = 1

* Device-Level-Prefetching (13 = 8k-Bloecke fuer disks reads, OLTP-tuning)
set zfs:zfs_vdev_cache_bshift = 13

* Device-Level-Prefetching ausschalten
* set zfs:zfs_vdev_cache_max = 0×1

* Device I/O Queue Size (I/O Concurrency)
* I/O queue depth pro LUN, default=35
* bei lokalen SATA-disks auf 10 setzen
* ansonsten gleich ssd_max_throttle setzen
set zfs:zfs_vdev_max_pending = 32

* EMC

* Queue-Laenge (empfohlen 20, bei Metadevices ggf. 32)
set ssd:ssd_max_throttle=32

* Timeout in HEX, recommended 0×3c = 60s bei multipathing, sonst 0×78
set ssd:ssd_io_time=0×3c

* Verzoegerung bis device als offline betrachtet wird
set fcp:fcp_offline_delay=20

* SAP / Oracle

* max. file descriptors pro Prozess
set rlim_fd_cur=8192

* security: stack nicht ausfuehrbar
set noexec_user_stack=1

Emulex-Treiber für Anschluß an SAN-Switch konfigurieren
# cat emlxs.conf
…
# +++ Variables relating to IP networking support. +++
#
# network-on: Enable/Disable IP networking support in the driver.
#
# 0 = Disables IP networking suppport in the driver.
# 1 = Enables IP networking suppport in the driver.
#
# Range: Min:0 Max:1 Default:1
#
#network-on=1;
network-on=0;
#
# +++ Fibre Channel specific parameters +++
#
# topology: link topology for initializing the Fibre Channel connection.
#
# 0 = attempt loop mode, if it fails attempt point-to-point mode
# 2 = attempt point-to-point mode only
# 4 = attempt loop mode only
# 6 = attempt point-to-point mode, if it fails attempt loop mode
#
# Set point-to-point mode if you want to run as an N_Port.
# Set loop mode if you want to run as an NL_Port.
#
# Range: Min:0 Max:6 Default:0
#
#topology=0;
topology=2;
# link-speed: Sets the link speed setting for initializing the Fibre Channel
# connection.
#
# 0 = auto select
# 1 = 1 Gigabaud
# 2 = 2 Gigabaud
# 4 = 4 Gigabaud
# 8 = 8 Gigabaud
#
# Range: Min:0 Max:8 Default:0
#
link-speed=0;
…

Multipathing konfigurieren
# cat fp.conf
…
#
# I/O multipathing feature (MPxIO) can be enabled or disabled using
# mpxio-disable property. Setting mpxio-disable=”no” will activate
# I/O multipathing; setting mpxio-disable=”yes” disables the feature.
#
# Global mpxio-disable property:
#
# To globally enable MPxIO on all fp ports set:
# mpxio-disable=”no”;
#
# To globally disable MPxIO on all fp ports set:
# mpxio-disable=”yes”;
#
# Per port mpxio-disable property:
#
# You can also enable or disable MPxIO on a per port basis.
# Per port settings override the global setting for the specified ports.
# To disable MPxIO on port 0 whose parent is /pci@8,600000/SUNW,qlc@4 set:
# name=”fp” parent=”/pci@8,600000/SUNW,qlc@4″ port=0 mpxio-disable=”yes”;
#
# NOTE: If you just want to enable or disable MPxIO on all fp ports, it is
# better to use stmsboot(1M) as it also updates /etc/vfstab.
#
#
# You can describe a list of target port WWNs and LUN numbers which will
# not be configured. LUN numbers will be interpreted as decimal. White
# spaces and ‘,’ can be used in the list of LUN numbers.
#
# pwwn-lun-blacklist=
# “target-port-wwn,lun-list”
#
# To prevent LUNs 1 and 2 from being configured for target
# port 510000f010fd92a1 and target port 510000e012079df1, set:
#
# pwwn-lun-blacklist=
# “510000f010fd92a1,1,2″,
# “510000e012079df1,1,2″;
#
# mpxio einschalten
mpxio-disable=”no”;
# mpxio fuer interne FC disks ausschalten
name=”fp” parent=”/pci@9,600000/SUNW,qlc@2″ port=0 mpxio-disable=”yes”;

Multipathing für Zusammenarbeit mit EMC DMX konfigurieren
# cat /kernel/drv/scsi_vhci.conf
…
# Load balancing global configuration: setting load-balance=”none” will cause
# all I/O to a given device (which supports multipath I/O) to occur via one
# path. Setting load-balance=”round-robin” will cause each path to the device
# to be used in turn.
#
load-balance=”round-robin”;
#
# Automatic failback configuration
# possible values are auto-failback=”enable” or auto-failback=”disable”
auto-failback=”enable”;
#
# For enabling MPxIO support for 3rd party symmetric device need an
# entry similar to following in this file. Just replace the “SUN SENA”
# part with the Vendor ID/Product ID for the device, exactly as reported by
# Inquiry cmd.
#
# device-type-scsi-options-list =
# “SUN SENA”, “symmetric-option”;
#
# symmetric-option = 0×1000000;
# Konfiguration fuer EMC Symmetrix
# zwischen EMC und SYMMETRIX 5 Leerzeichen!!!
device-type-scsi-options-list = “EMC SYMMETRIX”, “symmetric-option”;
symmetric-option = 0×1000000;

Zum Aktivieren der Konfiguration:
# reboot — -r

Dies stellt nur eine kurze Übersicht der relevanten Parameter für ein Testsystem dar. Kommentare und konstruktive Kritik sind willkommen

Comments Kommentare deaktiviert

21 04 2008

Solaris als Storageserver

Geschrieben von otmanix in EMC, NAS, Netapp, OpenSolaris, SAN, Samba, Solaris, Storage, VMware, Windows, ZFS, tags: CIFS, fc, fcoe, iscsi, iSNS, mpxio, multipathing, NAS, NFS, OpenSolaris, SAN, Solaris, Storage, svm, UFS, ZFS

“Wo liegt der Reiz an Solaris?” werde ich immer wieder gefragt. Eines der Sahnestücke von Solaris ist meiner Meinung nach der Einsatz als universelle Storageplattform auf LowCost-Hardware, z.B. als günstiger Ersatz für einen Netapp-Filer. Wer die Opensolaris-Entwicklung etwas mitverfolgt erlebt hier beinahe monatlich neue Features im Storageumfeld. Hier ist bei weitem noch kein Ende der Entwicklung in Sicht.

http://www.opensolaris.org/os/community/storage/

SVM, UFS, ZFS – Volumemanager, Filesysteme, Volumes, Snapshots, uvm.

Traditionell wird unter Solaris der SVM als Volumemanager benutzt, UFS ist das Standard-Filesystem. Mit Multiterabyte-Support und Journaling per SVM wurde UFS im Nachhinein aufgebohrt. UFS-Snapshots funktionieren, wirken aber irgendwie wie ein angestückelter Fremdkörper. Das Handling von SVM ist sehr gewöhnungsbedürftig, Freunde gewinnt man so sicherlich nicht. SVM/UFS ist heute nach wie vor für die Spiegelung von lokalen Bootdevices üblich.

Der große Wurf gelang Sun mit ZFS. ZFS ist Volumemanager und Filesystem zugleich. Damit ist die Liste der Features aber noch lange nicht erschöpft. Prinzipiell werden Platten oder Slices (Partitionen) einem Pool zugewiesen, ein entsprechender RAID-Level gesetzt (Striping, Mirroring, RAID-Z) und diverse Parameter wie z.B. Blocksize gesetzt. In einem Pool können dann ZFS-Filesysteme oder Volumes (ähnlich RAW-devices) angelegt und mit Parametern, wie z.B. Quota und Reservierung, versehen werden. Auf Volumes können beliebige Filesysteme aufgebracht werden.

Auf ZFS-Pools, -Filesysteme und -Volumes können Snapshots angewendet werden. Diese können auch geclont und damit beschreibbar wiederverwendet werden.

Mit zfs send/receive können ZFS-Daten über IP repliziert werden.

ZFS Pools können exportiert und auf einem anderen Rechner wieder importiert werden. Geänderte Hardwarepfade, etc. spielen keine Rolle – so lange alle Platten eines Pools zur Verfügung stehen klappt der Import.

ZFS ist (noch?) nicht als Shared Filesystem geeignet. D.h. im Cluster kann es nur für Failoverszenarien eingesetzt werden.

Die Performance von ZFS ist abhängig vom Szenario, wo es zum Einsatz kommen soll. Mittlerweile in den meisten Bereichen UFS ebenbürtig gibt es noch Potential zu VxFS. Tuning ist oft sinnvoll. Je höher das Solaris-Release, desto mehr Möglichkeiten zur Optimierung gibt es.

ZFS bietet neben der eingängen Shell-Kommandos auch ein Webgui.

ZFS hat eingebaute Mechanismen wie “Self Healing” und Schutz gegen “silent data corruption”.

http://blogs.sun.com/chrisg/entry/latency_bubble_in_your_io

http://przemol.blogspot.com/2008/02/zfs-vs-vxfs-vs-ufs-on-x4500-thumper.html

http://blogs.sun.com/SC/entry/why_sunw_nfs_is_required

http://www.solarisinternals.com//wiki/index.php?title=Category:ZFS

http://www.opensolaris.org/os/community/zfs/docs/

http://wiki.edv-widhalm.com/index.php/Solaris_Volume_Manager_%28HowTo%29

http://wiki.edv-widhalm.com/index.php/Zfs_%28HowTo%29

http://www.learning-solaris.com/index.php/category/unix-solaris-storage-volume-management/

http://www.osnews.com/story/19665/Solaris_Filesystem_Choices

http://blogs.digitar.com/jjww/?itemid=52

NAS – iSCSI

Solaris beherrscht iSCSI Initiator (Zugriff auf iSCSI-Volume) und iSCSI Target (Bereitstellen
eines iSCSI Volumes). Dabei kann z.B. ein ZFS Volume als iSCSI Target genutzt werden. Das kann man z.B. nutzen um einem Windows- oder VMware-ESX-Server Diskspace zur Verfügung zu stellen. Von den ZFS Volumes können dann Snapshots erstellt werden.

http://blogs.sun.com/mhuff/entry/introduction_to_iscsi_in_solaris

http://www.opensolaris.org/os/project/iscsitgt/

http://www.opensolaris.org/os/project/isns/

http://blogs.sun.com/lokibear/entry/download_isns_web_based_management

NAS Freigaben – NFS und CIFS

ZFS-Filesysteme beherrschen UNIX- und Windows-ACLs (W2K kompatibel) – damit entfallen viele Hürden als Netzwerkspeicher. Darüber hinaus können in ZFS-Filesystemen NFS- und CIFS-Freigaben als Eigenschaften eingerichtet werden. Eine ADS-Integration ist auch möglich. Der brandneue CIFS-Server mit ZFS-Integration dürfte unter Solaris eine ernsthafte Konkurrenz zu Samba werden.

http://blogs.sun.com/timthomas/entry/opensolaris_as_a_storageos_the

http://blogs.sun.com/dougm/

http://blogs.sun.com/amw/entry/cifs_in_solaris

SAN – Fibrechannel, FCoE

Im Bereich Fibrechannel wurde zuletzt in erster Linie in leichtere Administration auf der Shell investiert. Interessant sind die OpenSolaris-Projekte Comstar und FC over Ethernet. Hier bewegt sich einiges, gerade auch im Bereich Virtualisierung mit NPIV (virtuelle FC-HBAs).

http://www.opensolaris.org/os/project/comstar/

http://www.opensolaris.org/os/project/fcoe/

http://www.opensolaris.org/os/project/npiv/

mpxio – Multipathing

Solaris unterstützt mit mpxio Multipathing für SCSI-, FC-, SAS- und iSCSI-Disks. Speichersysteme mit SCSI SPC-2/3 werrden automatisch erkannt, eine manuelle Zuordnung in der Konfigurationsdatei durch Vendor und Product ist auch möglich, z.B. “EMC SYMMETRIX”. Es wird Failover und Roundrobin als Verfahren unterstützt. Mit dem mpathadm-Kommando ist die Administration sehr eingängig. Durch mpxio wird aus den verschiedenen Hardwarepfaden (verschiedene Controller/Targets, gleiche LUN) ein virtueller Pfad erstellt, der dann für die Konfiguration im Volumemanager benutzt wird.

http://www.opensolaris.org/os/project/mpxio/

last but not least: ZFS in der Praxis … (Achtung! US-Propaganda)

Comments 7 Kommentare »

Suche
Archiv
Kategorien
Online Translator
Schlagwörter

AIX Auto Backup Blog BRTOOLS CIFS Datenschutz DDS EMC Humor Indiana installation iscsi ksh93 LDom Linux Max Bögl Mediaserver mysap.ERP2005 Netapp Networker niagara II OpenSolaris Oracle playstation 3 PMS point in time recovery PS3 ps3mediaserver Recovery Restore SAN SAP Solaris Storage Streaming Sun t2 Tape Library VMware wordpress Xen xvm ZFS zones
Letzte Kommentare
- Waldi bei PS3 Media Server 1.20 build 405
- MrMorgan bei PS3 Media Server 1.20 build 405
- otmanix bei PS3 Media Server 1.20 build 405
- Waldi bei PS3 Media Server 1.20 build 405
- otmanix bei PS3 Media Server 1.20 build 405
Letzte Artikel
Blogroll
Meta
Privat

Webmail 1und1
Webmail GMX
Webspace 1und1

Otmanix’ Blog

Wissenswertes und Belangloses aus dem Leben eines Admins

Posts Tagged “svm”

flying zones für Arme – Teil 2: Liveupgrade mit Solaris10 Update6 und ZFS-root

serielles Patching und Zonen

Parallel Patching, Solaris Liveupgrade, Neuerungen in Solaris10u6 10/08

Solaris Liveupgrade bei S10u6 im Praxiseinsatz

neuer Versuch – Liveupgrade ohne Zonen, nur für ZFS-root

Patchen der Zone mit ugrade-on-attach

weiterer Test nach Einspielen des recommended patch clusters

flying zones für Arme im Eigenbau mit Solaris10 und Vmware Server 2

Solaris Zones / Container

flying zones

flying zones für Arme im Eigenbau

Testumgebung auf Vmware Server 2.01

Arbeiten mit den shared disks

ZFS für Zonenroot, RAID1 gespiegelt

Datenbereich mit UFS-Filesystem auf SVM shared disk set, RAID1 gespiegelt

Konfiguration und Installation der Zone zone1

Zonenmigration

Fazit

Weiterführende Literatur, etc.

Automatisiertes Schreiben von disk label unter Solaris

Parameter für SAP/Oracle-Testsystem auf Solaris10u5, EMC und ZFS

Solaris als Storageserver

Suche

Archiv

Kategorien

Online Translator

Letzte Kommentare

Letzte Artikel

Blogroll

Meta

Privat

Otmanix’ Blog

Wissenswertes und Belangloses aus dem Leben eines Admins

Posts Tagged “svm”

flying zones für Arme – Teil 2: Liveupgrade mit Solaris10 Update6 und ZFS-root

serielles Patching und Zonen

Parallel Patching, Solaris Liveupgrade, Neuerungen in Solaris10u6 10/08

Solaris Liveupgrade bei S10u6 im Praxiseinsatz

neuer Versuch – Liveupgrade ohne Zonen, nur für ZFS-root

Patchen der Zone mit ugrade-on-attach

weiterer Test nach Einspielen des recommended patch clusters

flying zones für Arme im Eigenbau mit Solaris10 und Vmware Server 2

Solaris Zones / Container

flying zones

flying zones für Arme im Eigenbau

Testumgebung auf Vmware Server 2.01

Arbeiten mit den shared disks

ZFS für Zonenroot, RAID1 gespiegelt

Datenbereich mit UFS-Filesystem auf SVM shared disk set, RAID1 gespiegelt

Konfiguration und Installation der Zone zone1

Zonenmigration

Fazit

Weiterführende Literatur, etc.

Automatisiertes Schreiben von disk label unter Solaris

Parameter für SAP/Oracle-Testsystem auf Solaris10u5, EMC und ZFS

Solaris als Storageserver

Suche

Archiv

Kategorien

Online Translator

Schlagwörter

Letzte Kommentare

Letzte Artikel

Blogroll

Meta

Privat