Berthold,
I am new to btrfs as well as with SLES 12. I was simply trying to create an
extensible filesystem the way I did with SLES 11 to be used as a repository for
the SLES 12 iso file.
When installing SLES 12 I let it default when I selected 'Configure DASD disks'
in the Disk Activation screen. So, I'm not sure what you are asking for in
'clarify the exact setup'.
Output from 'df -h':
Filesystem Size Used Avail Use% Mounted on
/dev/dasdb2 6.7G 3.0G 3.5G 47% /
devtmpfs 62M 0 62M 0% /dev
tmpfs 68M 0 68M 0% /dev/shm
tmpfs 68M 5.5M 63M 8% /run
tmpfs 68M 0 68M 0% /sys/fs/cgroup
/dev/dasdb2 6.7G 3.0G 3.5G 47% /var/opt
/dev/dasdb2 6.7G 3.0G 3.5G 47% /var/spool
/dev/dasdb2 6.7G 3.0G 3.5G 47% /var/tmp
/dev/dasdb2 6.7G 3.0G 3.5G 47% /var/log
/dev/dasdb2 6.7G 3.0G 3.5G 47% /var/lib/pgsql
/dev/dasdb2 6.7G 3.0G 3.5G 47% /var/lib/named
/dev/dasdb2 6.7G 3.0G 3.5G 47% /usr/local
/dev/dasdb2 6.7G 3.0G 3.5G 47% /tmp
/dev/dasdb1 194M 23M 161M 13% /boot/zipl
/dev/dasdb2 6.7G 3.0G 3.5G 47% /var/lib/mailman
/dev/dasdb2 6.7G 3.0G 3.5G 47% /var/crash
/dev/dasdb2 6.7G 3.0G 3.5G 47% /srv
/dev/dasdb2 6.7G 3.0G 3.5G 47% /opt
/dev/dasdb2 6.7G 3.0G 3.5G 47% /home
/dev/dasdb2 6.7G 3.0G 3.5G 47% /boot/grub2/s390x-emu
Contents of /etc/fstab:
/dev/disk/by-path/ccw-0.0.0300-part1 swap swap defaults
0 0
/dev/disk/by-path/ccw-0.0.0301-part1 swap swap defaults
0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde / btrfs
defaults 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /boot/grub2/s390x-emu btrfs
subvol=@/boot/grub2/s390x-emu 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /home btrfs
subvol=@/home 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /opt btrfs
subvol=@/opt 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /srv btrfs
subvol=@/srv 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /tmp btrfs
subvol=@/tmp 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /usr/local btrfs
subvol=@/usr/local 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /var/crash btrfs
subvol=@/var/crash 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /var/lib/mailman btrfs
subvol=@/var/lib/mailman 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /var/lib/named btrfs
subvol=@/var/lib/named 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /var/lib/pgsql btrfs
subvol=@/var/lib/pgsql 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /var/log btrfs
subvol=@/var/log 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /var/opt btrfs
subvol=@/var/opt 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /var/spool btrfs
subvol=@/var/spool 0 0
UUID=bd25dbd4-e2ce-44f3-b8a1-18573cf53cde /var/tmp btrfs
subvol=@/var/tmp 0 0
/dev/disk/by-path/ccw-0.0.0100-part1 /boot/zipl ext2
acl,user_xattr 1 2
I will investigate using btrfs to do what I need instead of creating an LVM
with a btrfs filesystem.
Thank you.
Harley
-----Original Message-----
From: Berthold Gunreben [mailto:[email protected]]
Sent: Monday, December 15, 2014 9:27 AM
To: Linker Harley - hlinke
Cc: [email protected]
Subject: Re: Need help with LVM in SLES 12 on System z
Hi,
just to make sure: You use btrfs on top of LVM? I am asking because the
standard setup just uses subvolumes of btrfs and no LVM below. There might be
good reasons to use LVM below, but a major part of the LVM functionality is
also there in btrfs.
In any case you will need a different partition with a filesystem that is
supported by zipl and mounted below /boot/zipl.
Could you clarify the exact setup?
Thanks
Berthold
On Mon, 15 Dec 2014 14:14:10 +0000
Linker Harley - hlinke <[email protected]> wrote:
> I am running SLES 12 (base install - no maintenance) as a guest under
> z/VM 6.3 non-SSI mainly to play with SLES 12 and identify the
> differences between it and SLES 11 SP3. Not that it matters, but this
> is a sandbox z/VM that has no access to the internet so I can't easily
> obtain and install maintenance.
>
> Almost immediately installing SLES 12 I created a LV using the btrfs
> filesystem on a single 3390-9 - the filesystem utilizes all of the
> space. After creating the LVM, I created the entry in /etc/fstab and
> mounted it using 'mount -a'. I worked on the system for a while and
> then decided to reboot. My system went into recovery mode as my new
> filesystem could not be found at boot time. Luckily, I has saved a
> copy of fstab and was able to save the exist fstab as fstab.new and
> copied the backup copy to fstab.
>
> When I rebooted I was able to bring up the full system and logged in
> with PuTTY. The output of the lvdisplay command shows the LV Status
> as 'NOT available'. I issued 'vgchange -ay' and the lvdisplay
> output showed the status as 'available'. If I reboot the system the
> LVM is again marked 'NOT available'.
>
> I never had this problem with earlier SLES versions, 'vgchange -ay'
> resolved the problem permanently. What do I need to do to force the
> LV to be available after every reboot in SLES 12?
>
>
> LV and fstab setup:
> I created the LV using the following commands (via PuTTY):
> pvcreate /dev/dasdd1
> vgcreate sysg1 /dev/dasdd1
> lvcreate -l 1760 -n system-lv1 sysg1
> mkfs.btrfs /dev/sysg1/system-lv1
>
> I obtained the 1760 in the lvcreate command from the 'Total PE' value
> as output from command 'vgdisplay sysg1' .
>
> I then updated /etc/fstab (after copying fstab to fstab.orig). I
> wanted to mount this new filesystem at /srv to eventually serve as a
> repository for the SLES 12 DVD1 iso file. I edited fstab to
> add: /dev/sysg1/system-lv1 /srv/ftp/repository
> btrfs defaults 0 0
>
>
> Harley
>
>
> HARLEY LINKER JR.
> Sr. Systems Programmer (z/Linux, z/OS, z/VM)
>
> [Acxiom_IT_color]
>
> Acxiom Corporation
> EML [email protected]<mailto:[email protected]>
> TEL +1 630.944.5111
> 3333 Finley Road, 8th Floor - NW, Downers Grove, IL, 60515, USA
> www.acxiomit.com<http://www.acxiomit.com/>
>
>
> [Friend Us on Facebook]<http://www.facebook.com/acxiomcorp> [Link Us
> on LinkedIn]
> <http://www.linkedin.com/groupRegistration?gid=2901735> [Follow Us
> on Twitter] <http://twitter.com/acxiom>
>
>
> **********************************************************************
> ***** The information contained in this communication is confidential,
> is intended only for the use of the recipient named above, and may be
> legally privileged.
>
> If the reader of this message is not the intended recipient, you are
> hereby notified that any dissemination, distribution or copying of
> this communication is strictly prohibited.
>
> If you have received this communication in error, please resend this
> communication to the sender and delete the original message or any
> copy of it from your computer system.
>
> Thank You.
> **********************************************************************
> ******
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to [email protected] 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/
--
----------------------------------------------------------------------
Berthold Gunreben Build Service Team
http://www.suse.de/ Maxfeldstr. 5
SUSE LINUX GmbH D-90409 Nuernberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham
Norton HRB 21284 (AG Nürnberg)
