![]() | EVMS Support Dropped in openSUSE 11.1 and SLES11 |
|---|---|
Since openSUSE 11.1 and SLES11, EVMS is no longer supported in the installation system. That means all support for EVMS in AutoYaST was dropped as well. All EVMS documentation here is only valid for SLES10 (all service packs) |
The following elements must be between the <partitioning config:type="list"><drive> ... </drive></partitioning> tags in the <profile> section.
|
Attribute |
Values |
Description |
|---|---|---|
|
device |
The device you want to configure in this <drive> section. You can use persistent device names via id, like /dev/disk/by-id/ata-WDC_WD3200AAKS-75L9A0_WD-WMAV27368122 or by-path,like /dev/disk/by-path/pci-0001:00:03.0-scsi-0:0:0:0. <device>/dev/hda</device> |
Optional. If left out, AutoYaST tries to guess the device (on openSUSE 12.2 and SLES11 SP2 you can influess the guessing - see below this table for instructions on how to do that). A RAID must always have "/dev/md" as device. |
|
initialize |
If set to "true", the partition table gets wiped out before AutoYaST starts the partition calculation. <initialize config:type="boolean" >true</initialize> |
Optional. The default is "false". |
|
partitions |
A list of <partition> entries (see table below). <partitions config:type="list"> <partition>...</partition> ... </partitions> |
Optional. If no partitions are specified, AutoYaST will create a reasonable partitioning (see Automated Partitioning below). |
|
pesize |
This value makes only sense with LVM/EVMS. <pesize>8M</pesize> |
Optional. Default is 4M for EVMS/LVM volume groups. |
|
use |
Specifies the strategy AutoYaST will use to partition the hard disk. Choose between:
|
This parameter should be provided. |
|
type |
Specify the type of the drive Choose between:
<type config:type="symbol">CT_LVM</type> |
Optional. Default is CT_DISK for a normal physical hard disk. |
|
disklabel |
Describes the type of the partition table. Choose between:
<disklabel>gpt</disklabel> |
Optional and available since openSUSE 12.1 and SLES11 SP2. By default YaST decides what makes sense (msdos in most cases). |
|
keep_unknown_lv |
This value only makes sense for type=CT_LVM drives. If you are reusing a LVG and you set this to "true", all existing LVs in that VG will not be touched unless they are specified in the <partitioning> section. So you can keep existing LVs without specifying them. <keep_unknown_lv config:type="boolean" >false</keep_unknown_lv> |
Optional and available since openSUSE 12.1 and SLES11 SP2. The default is "false". |
Since openSUSE 12.2 and SLES11 SP2 you can influence the device-guessing of AutoYaST for the case that you don't specify a <device> entry on your own. Usually AutoYaST would use the first device it can find and that looks reasonable but you can configure to skip some devices like this:
<partitioning config:type="list">
<drive>
<initialize config:type="boolean">true</initialize>
<!-- the skip_list is optional and available since openSUSE 12.2 and SLES11 SP2 -->
<skip_list config:type="list">
<listentry>
<!-- skip devices that use the usb-storage driver -->
<skip_key>driver</skip_key>
<skip_value>usb-storage</skip_value>
</listentry>
<listentry>
<!-- skip devices that are smaller than 1GB -->
<skip_key>size_k</skip_key>
<skip_value>1048576</skip_value>
<skip_if_less_than config:type="boolean">true</skip_if_less_than>
</listentry>
<listentry>
<!-- skip devices that are larger than 100GB -->
<skip_key>size_k</skip_key>
<skip_value>104857600</skip_value>
<skip_if_more_than config:type="boolean">true</skip_if_more_than>
</listentry>
</skip_list>
...
For a list of all possible <skip_key>, run "yast2 ayast_probe" on openSUSE 12.2 or SLES11SP2
The following elements must be between the <partitions config:type="list"><partition> ... </partition></partitions> tags in the <drive> section.
|
Attribute |
Values |
Description |
|---|---|---|
|
create |
Specify if this partition must be created or if it already exists. <create config:type="boolean" >false</create> |
If set to "false", provide information for AutoYaST which partition this is (like with partition_nr). |
|
mount |
The mountpoint of this partition. <mount>/</mount> <mount>swap</mount> |
You should have at least a root partition (/) and a swap partition. |
|
fstopt |
Mount options for this partition. <fstopt >ro,noatime,user,data=ordered,acl,user_xattr</fstopt> |
See man mount for available mount options. |
|
label |
The label of the partition (useful for the "mountby" parameter; see below). <label>mydata</label> |
See man e2label for an example. |
|
uuid |
The uuid of the partition (only useful for the "mountby" parameter; see below). <uuid >1b4e28ba-2fa1-11d2-883f-b9a761bde3fb</uuid> |
See man uuidgen. |
|
size |
The size of the partition, e.g. 4G, 4500M, etc. The /boot partition and the swap partition can have "auto" as size. Then AutoYaST calculates a reasonable size. One partition can have the value "max" to use all remaining space. You can specify the the size in percentage. So 10% will use 10% of the size of the hard disk or VG. You can mix auto, max, size, and percentage as you like. <size>10G</size> | |
|
format |
Specify if AutoYaST should format the partition. <format config:type="boolean">false</format> |
If you set "create" to "true", then you likely want this is option set to "true" as well. |
|
filesystem |
Specify the filesystem to use on this partition:
<filesystem config:type="symbol" >reiser</filesystem> |
Optional. The default is reiser |
|
partition_nr |
The partition number of this partition. If you have set create=false or if you use LVM, then you can specify the partition via partition_nr. You can force AutoYaST to only create primary partitions by assigning numbers below 5. <partition_nr config:type="integer" >2</partition_nr> |
In most cases, numbers 1 to 4 are primary partitions while 5 and higher are logical partitions. |
|
partition_id |
The partition_id sets the id of the partition. If you want different identifiers than 131 for Linux partition or 130 for swap, configure them with partition_id. <partition_id config:type="integer" >131</partition_id> |
The default is 131 for linux partition and 130 for swap. |
|
mountby |
Instead of a partition number, you can tell AutoYaST to mount a partition by device, label, uuid, path or id, which are the udev path and udev id (see /dev/disk/...). <mountby config:type="symbol" >label</mountby> |
See "label" and "uuid" documentation above. The default depends on YaST and is id in most cases. It was device in the past. |
|
subvolumes |
List of subvolumes to create for a filesystem of type btrfs. This key only make sense for filesystems of type btrfs. If there is a default subvolume used for the distribution (like e.g. "@" in SLES11 SP2) the name of this default subvolume is automatically prepended to the names in this list. <subvolumes config:type="list">
<path>tmp</path>
<path>opt</path>
<path>srv</path>
<path>var/crash</path>
<path>var/lock</path>
<path>var/run</path>
<path>var/tmp</path>
<path>var/spool</path>
...
</subvolumes>
|
this key is available since openSUSE 12.3 and SLES11 SP3 |
|
lv_name |
If this partition is in a logical volume in a volume group (LVM or EVMS) specify the logical volume name here (see is_lvm_vg or is_evms_vg parameter in drive configuration). <lv_name>opt_lv</lv_name> | |
|
stripes |
An integer that configures LVM striping. Specify across how many devices you want to stripe (spread data). <stripes config:type="integer">2</stripes> | |
|
stripesize |
Specify the size of each block in kb. <stripesize config:type="integer" >4</stripesize> | |
|
lvm_group |
If this is a physical partition used by (part of) a volume group (LVM), you have to specify the name of the volume group here. <lvm_group>system</lvm_group> | |
|
evms_group |
If this physical partition is used by a volume group (EVMS), you have to specify the name of the volume group here. <evms_group>system</evms_group> | |
|
raid_name |
If this physical volume is part of a RAID, specify the name of the RAID. <raid_name>/dev/md0</raid_name> | |
|
raid_type |
Specify the type of the RAID. <raid_type>raid1</raid_type> | |
|
raid_options |
Specify RAID options, see below. <raid_options>...</raid_options> | |
|
resize |
This boolean must be "true" if an existing partition should be resized. In this case, you want to set create to false and in most cases you don't want to format the partition. You need to tell AutoYaST the partition_nr and the size. The size can be in percentage of the original size or a number, like 800M. max and auto do not work as size here. <resize config:type="boolean" >false</resize> |
The resize only works with physical disks. Not with LVM/EVMS volumes. |
The following elements must be between the <partition><raid_options> ... </raid_options></partition> tags.
|
Attribute |
Values |
Description | |
|---|---|---|---|
|
chunk_size |
<chunk_size>4</chunk_size> | ||
|
parity_algorithm |
Possible values are: left_asymmetric, left_symmetric, right_asymmetric, right_symmetric. Since SLES11 SP2 and openSUSE 12.1 you can use: parity_first, parity_last, left_asymmetric_6, left_symmetric_6, right_asymmetric_6, right_symmetric_6, parity_first_6, n2, o2, f2, n3, o3, f3 for RAID6 and RAID10 <parity_algorithm >left_asymmetric</parity_algorithm> | ||
|
raid_type |
Possible values are: raid0,raid1 and raid5. <raid_type>raid1</raid_type> |
The default is raid1. | |
|
device_order |
this list contains the optional order of the physical devices <device_order config:type="list"> <device>/dev/sdb2</device> <device>/dev/sda1</device> ... </device_order> |
this is optional and the default is alphabetical order |
this key is available since openSUSE 12.2 and SLES11 SP3 |
For automated partitioning, you only need to provide the sizes and mount points of partitions. All other data needed for successful partitioning is calculated during installation—unless provided in the control file.
If no partitions are defined and the specified drive is also the drive where the root partition should be created, the following partitions are created automatically:
/boot
The size of the /boot partition is determined by the architecture of the target system.
swap
The size of the swap partition is determined by the amount of memory available in the system.
/ (root partition)
The size of the root partition is determined by the space left after creating swap and /boot.
Depending on the initial status of the drive and how it was previously partitioned, it is possible to create the default partitioning in the following ways:
Use free space
If the drive is already partitioned, it is possible to create the new partitions using the free space on the hard drive. This requires the availability of enough space for all selected packages in addition to swap.
Reuse all available space
Use this option to delete all existing partitions (Linux and non-Linux).
Reuse all available Linux partitions
This option deletes all existing Linux partitions. Other partitions (i.e. Windows) remain untouched. Note that this works only if the Linux partitions are at the end of the device.
Reuse only specified partitions
This option allows you to select specific partitions to delete. Start the selection with the last available partition.
Repartitioning only works if the selected partitions are neighbors and located at the end of the device.
![]() | Important Notice |
|---|---|
The value provided in the use property determines how existing data and partitions are treated. The value all means that ALL data on the disk will be erased. Make backups and use the confirm property if you are going to keep some partitions with important data. During automated installation, no popups will notify you about partitions being deleted. |
If multiple drives are present in the target system, identify all drives with their device names and specify how the partitioning should be performed.
Partition sizes can be given in gigabytes, megabytes or can be set to a flexible value using the keywords auto and max. max uses all available space on a drive, therefore should only be set for the last partition on the drive. With auto the size of a swap or boot partition is determined automatically, depending on the memory available and the type of the system.
A fixed size can be given as shown below:
1GB will create a partition of the size 1 GB. 1500MB will create a partition of the size 1.5 GB.
Example 4.3. Automated Partitioning
The following is an example of a single drive system, which is not pre-partitioned and should be automatically partitioned according to the described pre-defined partition plan. If you do not specify the device, it will be automatically detected. You do not have to create different profiles for /dev/sda or /dev/hda systems.
<partitioning config:type="list">
<drive>
<device>/dev/hda</device>
<use>all</use>
</drive>
</partitioning>
A more detailed example shows how existing partitions and multiple drives are handled.
Example 4.4. Detailed Automated Partitioning
<partitioning config:type="list">
<drive>
<device>/dev/hda</device>
<partitions config:type="list">
<partition>
<mount>/</mount>
<size>5gb</size>
</partition>
<partition>
<mount>swap</mount>
<size>1gb</size>
</partition>
</partitions>
</drive>
<drive>
<device>/dev/hdb</device>
<use>all</use>
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<mount>/data1</mount>
<size>15gb</size>
</partition>
<partition>
<filesystem config:type="symbol">jfs</filesystem>
<mount>/data2</mount>
<size>auto</size>
</partition>
</partitions>
<use>free</use>
</drive>
</partitioning>
In most cases this is not needed because AutoYaST can delete partitions one by one automatically, but you have the option to let AutoYaST clear the partition table instead of deleting partitions individually.
Go to the "drive" section and add:
<initialize config:type="boolean">true</initialize>
With this setting AutoYaST will delete the partition table before it starts to analyse the actual partitioning and calculates its partition plan. Of course this means, that you cannot keep any of your existing partitions.
By default a file system to be mounted is identified in
/etc/fstab by the device name. This
identification can be changed so the file system is found by searching
for a UUID or a volume label. Note that not all
file systems can be mounted by UUID or a volume
label. To specify how a partition is to be mounted, use the
mountby property which has the
symbol type. Possible options are:
device (default),
label,
UUID.
If you choose to mount the partition using a label, the name entered for the label property is used as the volume label.
Add any legal mount option in the fourth field of
/etc/fstab. Multiple options are separated by commas. Possible fstab options:
Mount read-only (ro): No write access to the file system. Default is "false".
No access time (noatime): Access times are not updated when a file is read. Default is "false".
Mountable by User (user): The file system can be mounted by a normal user. Default is "false".
Data Journaling Mode (ordered, journal, writeback): Specifies the journaling mode for file data.
All data is committed to the journal prior to being written to the main file system.
All data is directly written to the main file system before its meta data is committed to the journal.
Data ordering is not preserved.
Access Control List (acl): Enable access control lists on the file system.
Extended User Attributes (user_xattr): Allow extended user attributes on the file system.
Example 4.5. Mount Options
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<fstopt>ro,noatime,user,data=ordered,acl,user_xattr</fstopt>
<mount>/local</mount>
<mountby config:type="symbol">uuid</mountby>
<partition_id config:type="integer">131</partition_id>
<size>10gb</size>
</partition>
</partitions>
In some cases you may want to leave partitions untouched and only format specific target partitions, rather than creating them from scratch. For example, if different Linux installations coexist, or you have another operating system installed, likely you do not want to wipe these out. Or you may want to leave data partitions untouched.
Such scenarios require certain knowledge about the target systems and hard drives. Depending on the scenario, you might need to know the exact partition table of the target hard drive with partition ids, sizes and numbers. With this data you can tell AutoYaST to keep certain partitions, format others and create new partitions if needed.
The following example will keep partitions 1, 2 and 5 and delete partition 6 to create two new partitions. All remaining partitions will only be formatted.
Example 4.6. Keeping partitions
<partitioning config:type="list">
<drive>
<device>/dev/hdc</device>
<partitions config:type="list">
<partition>
<create config:type="boolean">false</create>
<format config:type="boolean">true</format>
<mount>/</mount>
<partition_nr config:type="integer">1</partition_nr>
</partition>
<partition>
<create config:type="boolean">false</create>
<format config:type="boolean">false</format>
<partition_nr config:type="integer">2</partition_nr>
<mount>/space</mount>
</partition>
<partition>
<create config:type="boolean">false</create>
<format config:type="boolean">true</format>
<filesystem config:type="symbol">swap</filesystem>
<partition_nr config:type="integer">5</partition_nr>
<mount>swap</mount>
</partition>
<partition>
<format config:type="boolean">true</format>
<mount>/space2</mount>
<size>50mb</size>
</partition>
<partition>
<format config:type="boolean">true</format>
<mount>/space3</mount>
<size>max</size>
</partition>
</partitions>
<use>6</use>
</drive>
</partitioning>
The last example requires exact knowledge of the existing partition table and the partition numbers of those partitions that should be kept. In some cases however, such data may not be available, especially in a mixed hardware environment with different hard drive types and configurations. The following scenario is for a system with a non-Linux OS with a designated area for a Linux installation.
In this scenario, shown in figure “Figure 4.1, “Keeping partitions””, AutoYaST will not create new partitions. Instead it searches for certain partition types on the system and uses them according to the partitioning plan in the control file. No partition numbers are given in this case, only the mount points and the partition types (additional configuration data can be provided, for example file system options, encryption and filesystem type).
Example 4.7. Auto-detection of partitions to be kept.
<partitioning config:type="list">
<drive>
<partitions config:type="list">
<partition>
<create config:type="boolean">false</create>
<format config:type="boolean">true</format>
<mount>/</mount>
<partition_id config:type="integer">131</partition_id>
</partition>
<partition>
<create config:type="boolean">false</create>
<format config:type="boolean">true</format>
<filesystem config:type="symbol">swap</filesystem>
<partition_id config:type="integer">130</partition_id>
<mount>swap</mount>
</partition>
</partitions>
</drive>
</partitioning>
![]() | New Feature |
|---|---|
This option will allow AutoYaST to use an existing
|
Although the default behaviour is to format all partitions, it is also possible to leave some partitions untouched and only mount them, for example data partitions. If multiple installations are found on the system (multiple root partitions with different fstab files, the installation will abort, unless the root partition is configured in the control file. The following example illustrates how this option can be used:
Example 4.8.
Reading existing /etc/fstab
<partitioning_advanced>
<fstab>
<!-- Read data from existing fstab. If multiple root partitions are
found, use the one specified below. Otherwise the first root
partition is taken -->
<!-- <root_partition>/dev/hda5</root_partition> -->
<use_existing_fstab config:type="boolean">true</use_existing_fstab>
<!-- all partitions found in fstab will be formatted and mounted
by default unless a partition is listed below with different
settings -->
<partitions config:type="list">
<partition>
<format config:type="boolean">false</format>
<mount>/bootmirror</mount>
</partition>
</partitions>
</fstab>
</partitioning_advanced>
To configure LVM, first create a physical volume using the normal partitioning method described above.
Example 4.9. Create LVM Physical Volume
The following example shows how to prepare for LVM in the partitioning resource:
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<partitions config:type="list">
<partition>
<lvm_group>system</lvm_group>
<partition_type>primary</partition_type>
<size>max</size>
</partition>
</partitions>
<use>all</use>
</drive>
</partitioning>
In the last example, a non-formatted partition is created on device
/dev/sda1 of the type LVM and
with the volume group system. This partition
will use all space available on the drive.
Example 4.10. LVM Logical Volumes (New syntax)
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<partitions config:type="list">
<partition>
<lvm_group>system</lvm_group>
<partition_type>primary</partition_type>
<size>max</size>
</partition>
</partitions>
<use>all</use>
</drive>
<drive>
<device>/dev/system</device>
<is_lvm_vg config:type="boolean">true</is_lvm_vg>
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<lv_name>user_lv</lv_name>
<mount>/usr</mount>
<size>500mb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<lv_name>opt_lv</lv_name>
<mount>/opt</mount>
<size>1500mb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<lv_name>var_lv</lv_name>
<mount>/var</mount>
<size>200mb</size>
</partition>
</partitions>
<pesize>4M</pesize>
<use>all</use>
</drive>
</partitioning>
With SUSE Linux 10.1 and all following versions, it is possible to set the size to max for the logical volumes. Of course, you can only use max for one(!) logical volume. You cannot set two logical volumes in one volume group to sizemax
SLES10 AutoYaST has EVMS support. SLES11 has not!
Using EVMS is quite similar to using LVM (see above). Switching from LVM to EVMS is just a small change in the AutoYaST profile. Change the "is_lvm_vg" element to "is_evms_vg" and the "lvm_group" element to "evms_group".
With AutoYaST it is not possible to mix LVM and EVMS.
Using the LVM example from above for EVMS, looks like this:
Example 4.11. EVMS Logical Volumes
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<partitions config:type="list">
<partition>
<evms_group>system</evms_group>
<partition_type>primary</partition_type>
<size>max</size>
</partition>
</partitions>
<use>all</use>
</drive>
<drive>
<device>/dev/system</device>
<is_evms_vg config:type="boolean">true</is_evms_vg>
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<lv_name>user_lv</lv_name>
<mount>/usr</mount>
<size>500mb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<lv_name>opt_lv</lv_name>
<mount>/opt</mount>
<size>1500mb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<lv_name>var_lv</lv_name>
<mount>/var</mount>
<size>200mb</size>
</partition>
</partitions>
<pesize>4M</pesize>
<use>all</use>
</drive>
</partitioning>
Using AutoYaST, you can create and assemble software RAID devices. The supported RAID levels are the following:
RAID 0: This level increases your disk performance. There is no redundancy in this mode. If one of the drives crashes, data recovery will not be possible.
RAID 1:This mode offers the best redundancy. It can be used with two or more disks. An exact copy of all data is maintained on all disks. As long as at least one disk is still working, no data is lost. The partitions used for this type of RAID should have approximately the same size.
RAID 5: This mode combines management of a larger number of disks and still maintains some redundancy. This mode can be used on three disks or more. If one disk fails, all data is still intact. If two disks fail simultaneously, all data is lost.
Multipath:This mode allows access to the same physical device via multiple controllers for redundancy against a fault in a controller card. This mode can be used with at least two devices.
As with LVM, you need to create all RAID partitions first and assign the partitions to the RAID device you want to create. Additionally you need to specify whether a partition or a device should be configured in the RAID or if it should be configured as a Spare device.
The following example shows a simple RAID1 configuration:
Example 4.12. RAID1 configuration
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<partitions config:type="list">
<partition>
<partition_id config:type="integer">253</partition_id>
<format config:type="boolean">false</format>
<raid_name>/dev/md0</raid_name>
<raid_type>raid</raid_type>
<size>4gb</size>
</partition>
<!-- Here come the regular partitions, i.e. / and swap -->
</partitions>
<use>all</use>
</drive>
<drive>
<device>/dev/sdb</device>
<partitions config:type="list">
<partition>
<format config:type="boolean">false</format>
<partition_id config:type="integer">253</partition_id>
<raid_name>/dev/md0</raid_name>
<raid_type>raid</raid_type>
<size>4gb</size>
</partition>
</partitions>
<use>all</use>
</drive>
<drive>
<device>/dev/md</device>
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/space</mount>
<partition_id config:type="integer">131</partition_id>
<partition_nr config:type="integer">0</partition_nr>
<raid_options>
<chunk_size>4</chunk_size>
<parity_algorithm>left-asymmetric</parity_algorithm>
<raid_type>raid1</raid_type>
</raid_options>
</partition>
</partitions>
<use>all</use>
</drive>
</partitioning>
Consider the following when configuring raid:
The device for raid is always /dev/md
The property partition_nr is used to determine the MD device number. If partition_nr is equal to 0, then /dev/md0 is configured.
All RAID-specific options are contained in the raid_options resource.
The following elements must be between the
<dasd> <devices config:type="list"> <listentry> ... </listentry> </devices> </dasd>
tags in the <profile> section. Each disk needs to be configured in a separate <listentry> ... </listentry> section.
|
Attribute |
Values |
Description |
|---|---|---|
|
device |
<device >DASD</dev_name> | |
|
dev_name |
The device ( <dev_name >/dev/dasda</dev_name> |
Optional but recommended. If left out, AutoYaST tries to guess the device. |
|
channel |
Channel by which the disk is accessed. <channel>0.0.0150</channel> |
Mandatory. |
|
diag |
Enable or disable the use of <diag config:type="boolean">true</diag> |
Optional. |
The following elements must be between the
<zfcp> <devices config:type="list"> <listentry> ... </listentry> </devices> </zfcp>
tags in the <profile> section. Each disk needs to be configured in a separate <listentry> ... </listentry> section.
|
Attribute |
Values |
Description |
|---|---|---|
|
controller_id |
Channel number <controller_id >0.0.fc00</controller_id> | |
|
fcp_lun |
Logical unit number <fcp_lun >0x4010400400000000</fcp_lun> | |
|
wwpn |
World wide port number <wwpn >0x500507630510473a</wwpn> |