Re: Unable to IPL the system after resizing "/" btrfs filesystem
>>> On 1/30/2017 at 05:33 PM, Alan Altmark wrote: > I would generally agree with this, but Michael pointed out that multiple > versions and distros are being booted in the same guest. He asked me why I recommended disabling cio_ignore, so I told him. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Unable to IPL the system after resizing "/" btrfs filesystem
On Monday, 01/30/2017 at 08:31 GMT, Mark Post wrote: > In general, it's a PITA for guests. I would generally agree with this, but Michael pointed out that multiple versions and distros are being booted in the same guest. If that is going to be the case, then cio_ignore is reasonable for fencing off the disks that are considered "private" to the distro/version. And Michael may have a perfectly good reason to be using the same guest. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems & Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Unable to IPL the system after resizing "/" btrfs filesystem
In my experience, the majority of the devices a Linux guest finds, at least the ones not needed, are DASD devices. So set up a single minidisk that all servers link to RR as their 191 disk. The common PROFILE EXEC can then be tuned to perform work common to all servers (e.g. CP DETACH any unneeded MDISKs), and also perform special setup for special servers, and then IPL from the proper Linux server boot disk. With one PROFILE EXEC for all servers, site-wide changes become consistent, and easy (as long as the change was tested on a different server first, and then renaming the current PROFILE EXEC on the common 191 disk to something like "-1PROFILE EXEC"), and copying the updated PROFILE EXEC to the common 191 disk. Mike Walter -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Monday, January 30, 2017 2:15 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Unable to IPL the system after resizing "/" btrfs filesystem >>> On 1/30/2017 at 09:19 AM, Michael J Nash wrote: > Greetings Mark, thank you for your reply. > Please explain the reasoning for disabling cio_ignore. > The reason I would not want to do this is because these guest systems > may be used for IPL of different distributions and/or releases. > I may IPL a SUSE 12, Red Hat 6.7, or a Red Hat 7.2 system. Having > disks visible used by other systems may cause problems. > Also, LVM volumes may conflict with naming conventions, For example: > both systems using the same volume group name. The cio_ignore feature was introduced primarily for LPAR installations. It helps speed up booting because the kernel doesn't try to enumerate every single device it can find. For z/VM environments that have relatively very few devices available, it's not needed. I can't speak for RHEL systems, but I think it's pretty much the same as for SLES. That is, unless you make a device persistently online, it's not going to come online by itself, so you shouldn't run into problems with LVM, extraneous DASD volumes being online, etc. Disabling cio_ignore in a guest means that people won't be constantly tripping over it when it's something they've not had to do for over 15 years. There are a number of things that you have to remember to do yourself when cio_ignore is active if you're not using YaST to do things. In general, it's a PITA for guests. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Unable to IPL the system after resizing "/" btrfs filesystem
>>> On 1/30/2017 at 09:19 AM, Michael J Nash wrote: > Greetings Mark, thank you for your reply. > Please explain the reasoning for disabling cio_ignore. > The reason I would not want to do this is because these guest systems may > be used for IPL of different distributions and/or releases. > I may IPL a SUSE 12, Red Hat 6.7, or a Red Hat 7.2 system. Having disks > visible used by other systems may cause problems. > Also, LVM volumes may conflict with naming conventions, For example: both > systems using the same volume group name. The cio_ignore feature was introduced primarily for LPAR installations. It helps speed up booting because the kernel doesn't try to enumerate every single device it can find. For z/VM environments that have relatively very few devices available, it's not needed. I can't speak for RHEL systems, but I think it's pretty much the same as for SLES. That is, unless you make a device persistently online, it's not going to come online by itself, so you shouldn't run into problems with LVM, extraneous DASD volumes being online, etc. Disabling cio_ignore in a guest means that people won't be constantly tripping over it when it's something they've not had to do for over 15 years. There are a number of things that you have to remember to do yourself when cio_ignore is active if you're not using YaST to do things. In general, it's a PITA for guests. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Unable to IPL the system after resizing "/" btrfs filesystem
Greetings Mark, I have found two methods that work for resizing the btrfs
"/" filesystem.
The two methods are to update /etc/fstab or update the kernel and then
update grub2.
I have a couple of questions.
1 - When I extend a xfs filesystem I do not need to update the kernel
or /etc/fstab.
2 - When I update the kernel I had to specify both disks.
The IPL volume and the dasd the I use to extend the filesystem.
I thought it odd that I had to specify the IPL volume.
Is there a reason for this? The 3120 address is the IPL volume.
Note: this is probably true for updating /etc/fstab but I did not try this
variation.
Method 1: Update /etc/fstab
cio_ignore -r 0.0.0604
chccwdev -e 0.0.0604
lsdasd - check dasd location
dasdfmt -b 4096 -f /dev/dasdb -p -y
fdasd -sa /dev/dasdb
Yast - make device persistent
reboot
btrfs device add /dev/dasda1 /
btrfs filesystem resize max /
Update /etc/fstab
UUID=b273239f-1943-4607-ad44-2e007624ee1b / btrfs
device=/dev/dasda1,device=/dev/dasdb3 0 0
grub2-install
Method 2: Update the kernel.
cio_ignore -r 0.0.0604
chccwdev -e 0.0.0604
lsdasd - check dasd location
dasdfmt -b 4096 -f /dev/dasdb -p -y
fdasd -sa /dev/dasdb
Yast - make device persistent
reboot
btrfs device add /dev/dasda1 /
btrfs filesystem resize max /
Yast update kernel parameters - !0.0.0604,!0.0.3120 and dasd=0604,3120
grub2-install
From: Mark Post
To: LINUX-390@VM.MARIST.EDU
Date: 01/27/2017 06:28 PM
Subject: Re: Unable to IPL the system after resizing "/" btrfs
filesystem
Sent by:Linux on 390 Port
>>> On 1/27/2017 at 11:31 AM, Michael J Nash wrote:
> cio_ignore -r 0.0.0604
If this is a z/VM environment and not an LPAR, I strongly recommend
completely disabling cio_ignore.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: Unable to IPL the system after resizing "/" btrfs filesystem
Greetings Mark, thank you for your reply.
Please explain the reasoning for disabling cio_ignore.
The reason I would not want to do this is because these guest systems may
be used for IPL of different distributions and/or releases.
I may IPL a SUSE 12, Red Hat 6.7, or a Red Hat 7.2 system. Having disks
visible used by other systems may cause problems.
Also, LVM volumes may conflict with naming conventions, For example: both
systems using the same volume group name.
From: Mark Post
To: LINUX-390@VM.MARIST.EDU
Date: 01/27/2017 06:28 PM
Subject:Re: Unable to IPL the system after resizing "/" btrfs
filesystem
Sent by:Linux on 390 Port
>>> On 1/27/2017 at 11:31 AM, Michael J Nash wrote:
> cio_ignore -r 0.0.0604
If this is a z/VM environment and not an LPAR, I strongly recommend
completely disabling cio_ignore.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: Unable to IPL the system after resizing "/" btrfs filesystem
>>> On 1/27/2017 at 11:31 AM, Michael J Nash wrote: > cio_ignore -r 0.0.0604 If this is a z/VM environment and not an LPAR, I strongly recommend completely disabling cio_ignore. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Unable to IPL the system after resizing "/" btrfs filesystem
Greetings Mark, I followed the process documented below to achieve my desired results. The interesting side effect is that I am able to restore the /etc/fstab to it's original form. I updated /etc/fstab after the kernel updates but it may also work before the kernel updates. It then may also work without the grub-2install. If I have time this afternoon I will try this procedure. cio_ignore -r 0.0.0604 chccwdev -e 0.0.0604 lsdasd - check dasd location dasdfmt -b 4096 -f /dev/dasdb -p -y fdasd -sa /dev/dasdb Yast - make device persistent reboot btrfs device add /dev/dasda1 / btrfs filesystem resize max / Update kernel parameters - !0.0.0604 and dasd=0604 Update /etc/fstab UUID=b273239f-1943-4607-ad44-2e007624ee1b / btrfs device=/dev/dasda1,device=/dev/dasdb3 0 0 grub2-mkconfig -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Unable to IPL the system after resizing "/" btrfs filesystem
Greetings Mark, I finally am able to successfully reboot the system.
I will try to test to see what actually worked.
From: Mark Post
To: LINUX-390@VM.MARIST.EDU
Date: 01/26/2017 06:19 PM
Subject:Re: Unable to IPL the system after resizing "/" btrfs
filesystem
Sent by:Linux on 390 Port
>>> On 1/26/2017 at 04:14 PM, Michael J Nash wrote:
> Greetings!
> I have a z/linux SLES12 system built with the btrfs file system.
> I successfully add and resize the "/" file system.
> When I reboot the system I hit an endless loop on the system with a
"start
> job".
>
> btrfs device add /dev/dasda /
Never use the base device for anything. Always use a partition.
> btrfs filesystem resize max /
> A start job is running for dev-disk-by\x2duuid-b2732... 5s
>
> Same results when I add !0.0.0604 and dasd=0604 using YAST.
> hvc_iucv=8 TERM=dumb resume=/dev/disk/by-path/ccw-0.0.3120-part2
> crashkernel=204M-:102M cio_ignore=all,!0.0.0604,!ipldev,!condev dasd=0604
If this is a z/VM system, you should disable cio_ignore entirely. Either
way, for a SLES12 (not SP1 and not SP2) system, when you add another device
to the root file system, you will need to manually re-run grub2-install.
Also, make sure that you used dasd_configure or YaST to bring the DASD
volume online. Those are the two ways to make it come online across
reboots.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: Unable to IPL the system after resizing "/" btrfs filesystem
Greetings Mark, thank you for your reply. Although I did not mention it , I have already tried tried grub2-install after updating the kernel through YAST. Also, I have made the device persistent. The resizing process appears to work when executed. I verify this with the "df -h" and "btrfs filesystem show /" commands. I did format and partition the dasd but also tried this formatted without a partition. Another thing I tried was to update /etc/fstab with "device=" for the parameters and changing "UUID" to "/dev/dasd". /dev/dasdb3 / btrfs device=/dev/dasda1,device=/dev/dasdb3 0 0 or UUID=b273239f-1943-4607-ad44-2e007624ee1b / btrfs device=/dev/dasda1,device=/dev/dasdb3 0 0 Tried several variations but I always hit the loop when I reboot the system. From: Mark Post To: LINUX-390@VM.MARIST.EDU Date: 01/26/2017 06:19 PM Subject: Re: Unable to IPL the system after resizing "/" btrfs filesystem Sent by:Linux on 390 Port >>> On 1/26/2017 at 04:14 PM, Michael J Nash wrote: > Greetings! > I have a z/linux SLES12 system built with the btrfs file system. > I successfully add and resize the "/" file system. > When I reboot the system I hit an endless loop on the system with a "start > job". > > btrfs device add /dev/dasda / Never use the base device for anything. Always use a partition. > btrfs filesystem resize max / > A start job is running for dev-disk-by\x2duuid-b2732... 5s > > Same results when I add !0.0.0604 and dasd=0604 using YAST. > hvc_iucv=8 TERM=dumb resume=/dev/disk/by-path/ccw-0.0.3120-part2 > crashkernel=204M-:102M cio_ignore=all,!0.0.0604,!ipldev,!condev dasd=0604 If this is a z/VM system, you should disable cio_ignore entirely. Either way, for a SLES12 (not SP1 and not SP2) system, when you add another device to the root file system, you will need to manually re-run grub2-install. Also, make sure that you used dasd_configure or YaST to bring the DASD volume online. Those are the two ways to make it come online across reboots. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Unable to IPL the system after resizing "/" btrfs filesystem
>>> On 1/26/2017 at 04:14 PM, Michael J Nash wrote: > Greetings! > I have a z/linux SLES12 system built with the btrfs file system. > I successfully add and resize the "/" file system. > When I reboot the system I hit an endless loop on the system with a "start > job". > > btrfs device add /dev/dasda / Never use the base device for anything. Always use a partition. > btrfs filesystem resize max / > A start job is running for dev-disk-by\x2duuid-b2732... 5s > > Same results when I add !0.0.0604 and dasd=0604 using YAST. > hvc_iucv=8 TERM=dumb resume=/dev/disk/by-path/ccw-0.0.3120-part2 > crashkernel=204M-:102M cio_ignore=all,!0.0.0604,!ipldev,!condev dasd=0604 If this is a z/VM system, you should disable cio_ignore entirely. Either way, for a SLES12 (not SP1 and not SP2) system, when you add another device to the root file system, you will need to manually re-run grub2-install. Also, make sure that you used dasd_configure or YaST to bring the DASD volume online. Those are the two ways to make it come online across reboots. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
