LPAR freezes after switching of storage (lpar is mirrored)
Hi all,
I have the following configuration
2 ds3524 storage disk systems located over 2 locations
2 P720 server located over 2 locations
DS3524 are connected to san switch.
Each vio server has 1 fc adapter attached to a san switch.
per p720 server 2 virtual io servers. Vio 1 has 1 lun from 1 ds3524, Vio 2 has 1 lun from the other ds3524
On the lpar we use LVM mirroring.
The problem:
When we halt 1 DS3524 the lpar freezes for about 30 seconds and then is again available.
Is this normal behaviour? When i shutdown 1 vio server , everything on the lpar is ok , no freeze.
There can be configurations in IBM Server wherein a
standalone partition is created on some supported IBM Server
Or
A VIOS - VIOC LPARs created.
Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..?
On a... (2 Replies)
Hi Folks,
I am a newbie in AIX.
Can someone please tell me how to do root mirroring in AIX LPAR which is created from mksysb image via HMC/NIM. ?
AIX 5.3/6.1
Let me know.
Thanks in advance (2 Replies)
I have created a new LPAR using IVM.
I activated the LPAR, and start the window terminal (java), it prompt me for the padmin password.
After keyin the password, it will shows BOOTP parameter.
I am just wondering how come it didnt go to screen where i can select to go into SMS menu to pick... (0 Replies)
I am planning for System P with 2 number of 2-core processor (4 core in total).
Can I make 3 LPARS with this processor configuration without the support of micropartitioning, that means with simple LPAR only. (3 Replies)
Hi,
Is there a way to dynamically increase the size of virtual disk on the LPAR. The virtual disk is coming from my VIO Server. From my SAN I have allocated a disk to VIO Server and from VIO Server to my LPAR....If I increase the space of the logical SAN DISK (DS 4700 using IBM TotalStorage... (0 Replies)
Hi,
I have 2 lpars on my AIX that needs to be started manually after each reboot.
Because the servers are storing the NFS and NIS info, other servers won't run correctly until they start up.
I found in IBM documentation the steps to make it automatic.
My question is, I want to know if... (2 Replies)
I have a P570 that for some reason is not allowing the P1-T6 NIC to be recognized. I have confirmed from the HMC that it is set for the LPAR, but when I do a cfgmgr, it won't recognize it. It though is recognizing the slot cards just fine which are P1-C3 for one shelf and P1-C3 of another shelf.... (1 Reply)
SYSTEMD-GPT-AUTO-GENERATOR(8) systemd-gpt-auto-generator SYSTEMD-GPT-AUTO-GENERATOR(8)NAME
systemd-gpt-auto-generator - Generator for automatically discovering and mounting root, /home and /srv partitions, as well as discovering
and enabling swap partitions, based on GPT partition type GUIDs.
SYNOPSIS
/lib/systemd/system-generators/systemd-gpt-auto-generator
DESCRIPTION
systemd-gpt-auto-generator is a unit generator that automatically discovers root, /home, /srv and swap partitions and creates mount and
swap units for them, based on the partition type GUIDs of GUID partition tables (GPT). It implements the Discoverable Partitions
Specification[1]. Note that this generator has no effect on non-GPT systems, or where the directories under the mount points are already
non-empty. Also, on systems where the units are explicitly configured (for example, listed in fstab(5)), the units this generator creates
are overridden, but additional implicit dependencies might be created.
This generator will only look for root partitions on the same physical disk the EFI System Partition (ESP) is located on. It will only look
for the other partitions on the same physical disk the root file system is located on. These partitions will not be searched on systems
where the root file system is distributed on multiple disks, for example via btrfs RAID.
systemd-gpt-auto-generator is useful for centralizing file system configuration in the partition table and making manual configuration in
/etc/fstab or suchlike unnecessary.
This generator looks for the partitions based on their partition type GUID. The following partition type GUIDs are identified:
Table 1. Partition Type GUIDs
+-------------------------------------+--------------------------------+--------------------------------------+
|Partition Type GUID | Name | Explanation |
+-------------------------------------+--------------------------------+--------------------------------------+
|44479540-f297-41b2-9af7-d131d5f0458a | Root Partition (x86) | On 32-bit x86 systems, the first x86 |
| | | root partition on the disk the EFI |
| | | ESP is located on is mounted to the |
| | | root directory /. |
+-------------------------------------+--------------------------------+--------------------------------------+
|4f68bce3-e8cd-4db1-96e7-fbcaf984b709 | Root Partition (x86-64) | On 64-bit x86 systems, the first |
| | | x86-64 root partition on the disk |
| | | the EFI ESP is located on is mounted |
| | | to the root directory /. |
+-------------------------------------+--------------------------------+--------------------------------------+
|69dad710-2ce4-4e3c-b16c-21a1d49abed3 | Root Partition (32-bit ARM) | On 32-bit ARM systems, the first ARM |
| | | root partition on the disk the EFI |
| | | ESP is located on is mounted to the |
| | | root directory /. |
+-------------------------------------+--------------------------------+--------------------------------------+
|b921b045-1df0-41c3-af44-4c6f280d3fae | Root Partition (64-bit ARM) | On 64-bit ARM systems, the first ARM |
| | | root partition on the disk the EFI |
| | | ESP is located on is mounted to the |
| | | root directory /. |
+-------------------------------------+--------------------------------+--------------------------------------+
|993d8d3d-f80e-4225-855a-9daf8ed7ea97 | Root Partition (Itanium/IA-64) | On Itanium systems, the first |
| | | Itanium root partition on the disk |
| | | the EFI ESP is located on is mounted |
| | | to the root directory /. |
+-------------------------------------+--------------------------------+--------------------------------------+
|933ac7e1-2eb4-4f13-b844-0e14e2aef915 | Home Partition | The first home partition on the disk |
| | | the root partition is located on is |
| | | mounted to /home. |
+-------------------------------------+--------------------------------+--------------------------------------+
|3b8f8425-20e0-4f3b-907f-1a25a76f98e8 | Server Data Partition | The first server data partition on |
| | | the disk the root partition is |
| | | located on is mounted to /srv. |
+-------------------------------------+--------------------------------+--------------------------------------+
|0657fd6d-a4ab-43c4-84e5-0933c84b4f4f | Swap | All swap partitions located on the |
| | | disk the root partition is located |
| | | on are enabled. |
+-------------------------------------+--------------------------------+--------------------------------------+
|c12a7328-f81f-11d2-ba4b-00a0c93ec93b | EFI System Partition (ESP) | The first ESP located on the disk |
| | | the root partition is located on is |
| | | mounted to /boot or /efi, see below. |
+-------------------------------------+--------------------------------+--------------------------------------+
The /home and /srv partitions may be encrypted in LUKS format. In this case, a device mapper device is set up under the names
/dev/mapper/home and /dev/mapper/srv. Note that this might create conflicts if the same partition is listed in /etc/crypttab with a
different device mapper device name.
Mount and automount units for the EFI System Partition (ESP) are generated on EFI systems. The ESP is mounted to /boot, unless a mount
point directory /efi exists, in which case it is mounted there. Since this generator creates an automount unit, the mount will only be
activated on-demand, when accessed. On systems where /boot (or /efi if it exists) is an explicitly configured mount (for example, listed in
fstab(5)) or where the /boot (or /efi) mount point is non-empty, no mount units are generated.
When using this generator in conjunction with btrfs file systems, make sure to set the correct default subvolumes on them, using btrfs
subvolume set-default.
systemd-gpt-auto-generator implements systemd.generator(7).
SEE ALSO systemd(1), systemd.mount(5), systemd.swap(5), systemd-fstab-generator(8), systemd-cryptsetup@.service(8), cryptsetup(8), fstab(5),
btrfs(8)NOTES
1. Discoverable Partitions Specification
https://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/
systemd 237SYSTEMD-GPT-AUTO-GENERATOR(8)