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 <mp...@suse.com>
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 <LINUX-390@VM.MARIST.EDU>



>>> On 1/26/2017 at 04:14 PM, Michael J Nash <miken...@us.ibm.com> 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/

Reply via email to