Hi Neil,
check RHEL-7 Installation Guide, there is a section describing how to
add DASDs:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/chap-post-installation-configuration-s390#sect-post-installation-dasds-setting-online-persistently-s390
Also
I understand now that the PV NAME displayed by pvdisplay is not important.
This is on RHEL 7.
Here is the story so far.
I added a volume to the server at address 10a.
I added 010a to dasd.conf.
The Linux group added the new volume to the root vg.
Upon next reboot, it failed with
Buffer I/O
>>> On 12/12/2018 at 11:39 AM, Neal Scheffler wrote:
> The Linux group expanded the root vg to a second physical dasd volume.
> Doing a pvdisplay shows the PV Name of /dev/dasdm1
> zipl.conf was updated to include the parm "rd.dasd=0.0.010a" since
> this is part of the root file system.
>
>
Hi,
yes, by-path or by-uuid is more reliable than the /dev/dasdX name.
The /dev/dasdX name depends on the order that the disks are set online
in the system.
Depending on the distribution this can not reliably be predicted.
Regards,
Stefan
On 12.12.18 17:39, Neal Scheffler wrote:
> The Linux
: Wednesday, December 12, 2018 8:40 AM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] Expanding root VG issue
The Linux group expanded the root vg to a second physical dasd volume.
Doing a pvdisplay shows the PV Name of /dev/dasdm1
zipl.conf was updated to include the parm "rd.dasd=0.0.010a&q
The Linux group expanded the root vg to a second physical dasd volume.
Doing a pvdisplay shows the PV Name of /dev/dasdm1
zipl.conf was updated to include the parm "rd.dasd=0.0.010a" since
this is part of the root file system.
After reboot, dasd 010a is now /dev/dasdb1 so the server reboot
