Re: 7.5 package levels

2018-05-24 Thread Viktor VM Mihajlovski
On 24.05.2018 06:59, Timothy Sipples wrote:
> Russ Herrold wrote:
>> It may turn out that we (ClefOS) need to fork and offer two
>> variants
>
> I guess I'd call them "streams" rather than "forks."
>
> For what it's worth, Red Hat seems to offer at least 3 major streams now:
> Fedora (their "community" release), RHEL Structure A, and RHEL. The RHEL
> Structure A/RHEL pair of streams is a unique offering for the s390x
> architecture branch, at least for now. (Is it a one-time aberration or the
> start of something new? I have no idea, so ask Red Hat, I guess.) In RHEL
> 7.5, Red Hat decided to offer kernel 3.10 (only) for all POWER processors
> prior to POWER9, and (only) kernel 4.14 for POWER9. For X86-64 it's only
> 3.10, and for ARM64 it's only 4.14.
>
> There are certain newer capabilities that RHEL 7.5 doesn't support on s390x
> that RHEL 7.5 Structure A does. Red Hat's release notes explain all that.
> But it's possible to mix RHEL and RHEL Structure A instances on the same
> machine and in a Red Hat supported way. (And, for that matter, other
> supported RHEL releases.)
>
Specifically, RHEL Structure A is required to run KVM guests on IBM Z.
Guests can be either RHEL and RHEL Structure A. Another thing to keep in
mind is that the s390utils-* releases are different. For RHEL it's
1.23.0 and for RHEL Structure A it's 2.1.0.
> It looks like the minimum RHEL 7.5/RHEL 7.5 Structure A machine model
> requirement hasn't changed since RHEL 7.4, so it's z196/z114 processors or
> higher, which includes all LinuxONE machines.
>
> I don't have a strong view on the "right" approach for Linux release
> streams. It really depends on end users and what they prefer, and they
> might choose particular Linux distributors based on their different
> release/service stream approaches. There are some important principles,
> though. I'd say that maintaining security currency is quite important, as a
> notable example. But that'll likely mean not waiting too long to exploit
> new system features since many of those new features are often
> security-related.
>
> 
> Timothy Sipples
> IT Architect Executive, Industry Solutions, IBM Z & LinuxONE,
> Multi-Geography
> E-Mail: sipp...@sg.ibm.com
>
> --
> 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/
>


--
Regards,
  Viktor Mihajlovski

--
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: LVM volume size

2018-05-04 Thread Viktor VM Mihajlovski
On 23.04.2018 19:41, Mariusz Walczak wrote:
> The below email is classified: Internal
> 
> Hello group,
> 
> Recently we had a DASD failure and I had to delete and recreate logical 
> volume in LVM. We had two model-9 DASDs defined as two logical volumes 
> (different volume groups). I used lvcreate -l 1760  to make sure the number 
> of extents is the same as before. When I mount it, df command shows 110MB 
> difference from old volume. In LVM number of Allocated PE are the same.
> Volume db4lv was created by LVM2 version 2.02.39 back in 2014...  Volume 
> db1lv created by LVM2 version 2.02.98(2). They have to match in size.
> Any ideas what can be the reason of this ?
> 
>   Filesystem1K-blocksUsed Available 
> Use% Mounted on
> /dev/mapper/DB4VG-db4lv 7208008  978512   6229496  14% /DB4
> /dev/mapper/DB1VG-db1lv 7095808   15828   6719532   1% /DB1
> 
> 
> # vgs -a -o +devices
>   DB1VG  1   1   0 wz--n-  6.88g0  /dev/dasdae1(0)
>   DB2VG  1   1   0 wz--n-  6.88g0  /dev/dasdaa1(0)
> 
> 
> Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
> ==
> 0.0.0305   active  dasdaa94:104   ECKD  4096   7042MB1802880
> 0.0.0309   active  dasdae94:120   ECKD  4096   7042MB1802880
> 
> # pvdisplay
>   --- Physical volume ---
>   PV Name   /dev/dasdae1
>   VG Name   DB1VG
>   PV Size   6.88 GiB / not usable 2.41 MiB
>   Allocatable   yes (but full)
>   PE Size   4.00 MiB
>   Total PE  1760
>   Free PE   0
>   Allocated PE  1760
> 
>   --- Physical volume ---
>   PV Name   /dev/dasdaa1
>   VG Name   TSM1DB2VG
>   PV Size   6.88 GiB / not usable 2.41 MiB
>   Allocatable   yes (but full)
>   PE Size   4.00 MiB
>   Total PE  1760
>   Free PE   0
>   Allocated PE  1760
> 
> 
> 
> Thanks,
> Mariusz
> Infrastructure Support
> zVM zLinux
> Deutsche Börse Services s.r.o.
> Sokolovská 662/136b
> 186 00 Prague 8
> Czech Republic
> +420 2964 28581
> +420 737208624
> 
> -
> Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen.
> Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte
> sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren
> dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen
> ist nicht gestattet.
> 
> The information contained in this message is confidential or protected by
> law. If you are not the intended recipient, please contact the sender and
> delete this message. Any unauthorised copying of this message or
> unauthorised distribution of the information contained herein is prohibited.
> 
> Legally required information for business correspondence/
> Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz:
> http://deutsche-boerse.com/letterhead
> 
> --
> 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/
> 
Hi Mariusz,

the logical volumes have the same size for sure. The df command displays
only filesystem size info (not that of the underlying block device).
In your case that means that both filesystems don't use all of the
logical volumes' space, which may be perfectly valid, depending on the
filesystem type and how the filesystem was created.

-- 
Regards,
  Viktor Mihajlovski

--
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/