Re: Simple DASD question

[Tom Huegel]

Mm probably not..
It's golf day no more time for work today.. Maybe I'll just grab a mod 27
on Monday.



On Fri, Apr 22, 2016 at 11:57 AM, Mark Post  wrote:

> >>> On 4/22/2016 at 11:20 AM, Tom Huegel  wrote:
> > Although when I try to reboot
> >
> >  [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46... 6s / no
> > limit) [ BUSY ] A start job is running for dev-disk-by\x2d
> > uuid-d8b46... 6s / no limit) [ BUSY ]
>
> Again, this looks like the bug in SLES12 that is fixed by later
> maintenance.  Was that applied before adding the DASD volume to the file
> system?
>
>
> 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: Simple DASD question

[Mark Post]

>>> On 4/22/2016 at 11:20 AM, Tom Huegel  wrote: 
> Although when I try to reboot
> 
>  [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46... 6s / no
> limit) [ BUSY ] A start job is running for dev-disk-by\x2d
> uuid-d8b46... 6s / no limit) [ BUSY ] 

Again, this looks like the bug in SLES12 that is fixed by later maintenance.  
Was that applied before adding the DASD volume to the file system?


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: Simple DASD question

[Harley Linker]

Did you run command 'fdasd -a /dev/dasdb' to create the partition?  /dev/dasdb1 
doesn't exist unless you run the command.

Harley Linker Jr.



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Tom Huegel
Sent: Friday, April 22, 2016 9:08 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Simple DASD question

So far I have failed with my feeble attempts to add the second disk dasdb
(0251) to the btrfs filesystem.
This is what I have fresh after my re-re-re-re-install.
It seems "btrfs device add /dev/dasdb1 /" would be a good thing to do but I get 
message about dasdb1 not existing...


sles12:~ # lsdasd
Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
==
0.0.0250   active  dasda 94:0ECKD  4096   7042MB1802880
0.0.0251   active  dasdb 94:4ECKD  4096   7042MB1802880
sles12:~ # btrfs filesystem show
Label: none  uuid: d8b46146-19c1-48d8-b024-80547e728787
Total devices 1 FS bytes used 2.74GiB
devid1 size 5.71GiB used 3.53GiB path /dev/dasda3
Btrfs v3.16+20140829
sles12:~ # df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/dasda3 5.8G  3.0G  2.5G  55% /
devtmpfs439M  8.0K  439M   1% /dev
tmpfs   446M 0  446M   0% /dev/shm
tmpfs   446M  7.0M  439M   2% /run
tmpfs   446M 0  446M   0% /sys/fs/cgroup
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/tmp
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/spool
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/opt
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/log
/dev/dasda1 194M   24M  161M  13% /boot/zipl
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/pgsql
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/named
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/mailman
/dev/dasda3 5.8G  3.0G  2.5G  55% /usr/local
/dev/dasda3 5.8G  3.0G  2.5G  55% /tmp
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/crash
/dev/dasda3 5.8G  3.0G  2.5G  55% /srv
/dev/dasda3 5.8G  3.0G  2.5G  55% /opt
/dev/dasda3 5.8G  3.0G  2.5G  55% /home
/dev/dasda3 5.8G  3.0G  2.5G  55% /boot/grub2/s390x-emu
sles12:~ #


On Thu, Apr 21, 2016 at 2:37 PM, Mark Post <mp...@suse.com> wrote:

> >>> On 4/21/2016 at 05:33 PM, Grzegorz Powiedziuk
> >>> <gpowiedz...@gmail.com>
> wrote:
> > then pvcreate, vgextend, lvextend and filesystem resize.
>
> No, we're trying to get him set up with LVM, just btrfs.
>
>
> 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/
© 2016 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. 
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.

Re: Simple DASD question

[Tom Huegel]

Although when I try to reboot

 [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46... 6s / no
limit) [ BUSY ] A start job is running for dev-disk-by\x2d
uuid-d8b46... 6s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46... 7s / no limit) [ BUSY ] A start job is
 running for dev-disk-by\x2duuid-d8b46... 7s / no limit) [ BUSY ] A start
job is running for dev-disk-by\x2duuid-d8b46... 8s / no li
mit) [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46... 8s /
no limit) [ BUSY ] A start job is running for dev-disk-by
\x2duuid-d8b46... 9s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46... 9s / no limit) [ BUSY ] A start jo
b is running for dev-disk-by\x2duuid-d8b46...10s / no limit) [ BUSY ] A
start job is running for dev-disk-by\x2duuid-d8b46...10s / n
o limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46...11s / no limit) [** [0m] A start job is
running for dev
-disk-by\x2duuid-d8b46...11s / no limit) [ * [0m] A start job is
running for dev-disk-by\x2duuid-d8b46...12s / no limit) [**
 [0m] A start job is running for dev-disk-by\x2duuid-d8b46...12s / no
limit) [ BUSY ] A start job is running for dev-disk-by\x2duuid
-d8b46...13s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46...13s / no limit) [ BUSY ] A start job is run
ning for dev-disk-by\x2duuid-d8b46...14s / no limit) [ BUSY ] A start job
is running for dev-disk-by\x2duuid-d8b46...14s / no limit)
 [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46...15s / no
limit) [ BUSY ] A start job is running for dev-disk-by\x2d
uuid-d8b46...15s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46...16s / no limit) [ BUSY ] A start job is
 running for dev-disk-by\x2duuid-d8b46...16s / no limit) [ BUSY ] A start
job is running for dev-disk-by\x2duuid-d8b46...17s / no li
mit) [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46...17s /
no limit) [ BUSY ] A start job is running for dev-disk-by
\x2duuid-d8b46...18s / no limit) [** [0m] A start job is running for
dev-disk-by\x2duuid-d8b46...18s / no limit) [ * [0m] A
start job is running for dev-disk-by\x2duuid-d8b46...19s / no limit) [
** [0m] A start job is running for dev-disk-by\x2duuid-d8b
46...19s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46...20s / no limit) [ BUSY ] A start job is running
 for dev-disk-by\x2duuid-d8b46...20s / no limit) [ BUSY ] A start job is
running for dev-disk-by\x2duuid-d8b46...21s / no limit) [ B
USY ] A start job is running for dev-disk-by\x2duuid-d8b46...21s / no
limit) [ BUSY ] A start job is running for dev-disk-by\x2duuid
-d8b46...22s / no limit) [ BUSY ] A start job is running for
dev-disk-by\x2duuid-d8b46...22s / no limit) [ BUSY ] A start job is run
ning for dev-disk-by\x2duuid-d8b46...23s / no limit) [ BUSY ] A start job
is running for dev-disk-by\x2duuid-d8b46...23s / no limit)
 [ BUSY ] A start job is running for dev-disk-by\x2duuid-d8b46...24s / no
limit)

















RUNNING   SCZVMLX2

On Fri, Apr 22, 2016 at 7:59 AM, Tom Huegel  wrote:

> Thank-you...
> Maybe someday I will learn how it all works... I just don't do that much
> with LINUX..
>
>
> sles12:~ # fdasd -a /dev/dasdb
> reading volume label ..: VOL1
> reading vtoc ..: ok
> auto-creating one partition for the whole disk...
> writing volume label...
> writing VTOC...
> rereading partition table...
> sles12:~ # btrfs device add /dev/dasdb1 /
> sles12:~ # btrfs filesystem show
> Label: none  uuid: d8b46146-19c1-48d8-b024-80547e728787
> Total devices 2 FS bytes used 2.74GiB
> devid1 size 5.71GiB used 3.53GiB path /dev/dasda3
> devid2 size 6.88GiB used 0.00B path /dev/dasdb1
> Btrfs v3.16+20140829
> sles12:~ # df -h
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/dasda3  13G  3.0G  9.4G  24% /
> devtmpfs439M  8.0K  439M   1% /dev
> tmpfs   446M 0  446M   0% /dev/shm
> tmpfs   446M  7.0M  439M   2% /run
> tmpfs   446M 0  446M   0% /sys/fs/cgroup
> /dev/dasda3  13G  3.0G  9.4G  24% /var/tmp
> /dev/dasda3  13G  3.0G  9.4G  24% /var/spool
> /dev/dasda3  13G  3.0G  9.4G  24% /var/opt
> /dev/dasda3  13G  3.0G  9.4G  24% /var/log
> /dev/dasda1 194M   24M  161M  13% /boot/zipl
> /dev/dasda3  13G  3.0G  9.4G  24% /var/lib/pgsql
> /dev/dasda3  13G  3.0G  9.4G  24% /var/lib/named
> /dev/dasda3  13G  3.0G  9.4G  24% /var/lib/mailman
> /dev/dasda3  13G  3.0G  9.4G  24% /usr/local
> /dev/dasda3  13G  3.0G  9.4G  24% /tmp
> /dev/dasda3  13G  3.0G  9.4G  24% /var/crash
> /dev/dasda3  13G  3.0G  9.4G  24% /srv
> /dev/dasda3  13G  3.0G  9.4G  24% /opt
> /dev/dasda3  13G  3.0G  9.4G  24% /home
> /dev/dasda3  13G  3.0G  9.4G  24% /boot/grub2/s390x-emu
> sles12:~ #
>
> On Fri, Apr 22, 2016 at 7:19 AM, Mark Post  wrote:
>
>> >>> On 4/22/2016 at 10:07 AM, 

Re: Simple DASD question

[Tom Huegel]

Thank-you...
Maybe someday I will learn how it all works... I just don't do that much
with LINUX..


sles12:~ # fdasd -a /dev/dasdb
reading volume label ..: VOL1
reading vtoc ..: ok
auto-creating one partition for the whole disk...
writing volume label...
writing VTOC...
rereading partition table...
sles12:~ # btrfs device add /dev/dasdb1 /
sles12:~ # btrfs filesystem show
Label: none  uuid: d8b46146-19c1-48d8-b024-80547e728787
Total devices 2 FS bytes used 2.74GiB
devid1 size 5.71GiB used 3.53GiB path /dev/dasda3
devid2 size 6.88GiB used 0.00B path /dev/dasdb1
Btrfs v3.16+20140829
sles12:~ # df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/dasda3  13G  3.0G  9.4G  24% /
devtmpfs439M  8.0K  439M   1% /dev
tmpfs   446M 0  446M   0% /dev/shm
tmpfs   446M  7.0M  439M   2% /run
tmpfs   446M 0  446M   0% /sys/fs/cgroup
/dev/dasda3  13G  3.0G  9.4G  24% /var/tmp
/dev/dasda3  13G  3.0G  9.4G  24% /var/spool
/dev/dasda3  13G  3.0G  9.4G  24% /var/opt
/dev/dasda3  13G  3.0G  9.4G  24% /var/log
/dev/dasda1 194M   24M  161M  13% /boot/zipl
/dev/dasda3  13G  3.0G  9.4G  24% /var/lib/pgsql
/dev/dasda3  13G  3.0G  9.4G  24% /var/lib/named
/dev/dasda3  13G  3.0G  9.4G  24% /var/lib/mailman
/dev/dasda3  13G  3.0G  9.4G  24% /usr/local
/dev/dasda3  13G  3.0G  9.4G  24% /tmp
/dev/dasda3  13G  3.0G  9.4G  24% /var/crash
/dev/dasda3  13G  3.0G  9.4G  24% /srv
/dev/dasda3  13G  3.0G  9.4G  24% /opt
/dev/dasda3  13G  3.0G  9.4G  24% /home
/dev/dasda3  13G  3.0G  9.4G  24% /boot/grub2/s390x-emu
sles12:~ #

On Fri, Apr 22, 2016 at 7:19 AM, Mark Post  wrote:

> >>> On 4/22/2016 at 10:07 AM, Tom Huegel  wrote:
> > This is what I have fresh after my re-re-re-re-install.
> > It seems "btrfs device add /dev/dasdb1 /" would be a good thing to do
> but I
> > get message about dasdb1 not existing...
>
> Have you used YaST or run fdasd to create it?
> fdasd -a /dev/dasdb
>
>
> 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: Simple DASD question

[Mark Post]

>>> On 4/22/2016 at 10:07 AM, Tom Huegel  wrote: 
> This is what I have fresh after my re-re-re-re-install.
> It seems "btrfs device add /dev/dasdb1 /" would be a good thing to do but I
> get message about dasdb1 not existing...

Have you used YaST or run fdasd to create it?
fdasd -a /dev/dasdb


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: Simple DASD question

[Tom Huegel]

So far I have failed with my feeble attempts to add the second disk dasdb
(0251) to the btrfs filesystem.
This is what I have fresh after my re-re-re-re-install.
It seems "btrfs device add /dev/dasdb1 /" would be a good thing to do but I
get message about dasdb1 not existing...


sles12:~ # lsdasd
Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
==
0.0.0250   active  dasda 94:0ECKD  4096   7042MB1802880
0.0.0251   active  dasdb 94:4ECKD  4096   7042MB1802880
sles12:~ # btrfs filesystem show
Label: none  uuid: d8b46146-19c1-48d8-b024-80547e728787
Total devices 1 FS bytes used 2.74GiB
devid1 size 5.71GiB used 3.53GiB path /dev/dasda3
Btrfs v3.16+20140829
sles12:~ # df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/dasda3 5.8G  3.0G  2.5G  55% /
devtmpfs439M  8.0K  439M   1% /dev
tmpfs   446M 0  446M   0% /dev/shm
tmpfs   446M  7.0M  439M   2% /run
tmpfs   446M 0  446M   0% /sys/fs/cgroup
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/tmp
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/spool
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/opt
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/log
/dev/dasda1 194M   24M  161M  13% /boot/zipl
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/pgsql
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/named
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/lib/mailman
/dev/dasda3 5.8G  3.0G  2.5G  55% /usr/local
/dev/dasda3 5.8G  3.0G  2.5G  55% /tmp
/dev/dasda3 5.8G  3.0G  2.5G  55% /var/crash
/dev/dasda3 5.8G  3.0G  2.5G  55% /srv
/dev/dasda3 5.8G  3.0G  2.5G  55% /opt
/dev/dasda3 5.8G  3.0G  2.5G  55% /home
/dev/dasda3 5.8G  3.0G  2.5G  55% /boot/grub2/s390x-emu
sles12:~ #


On Thu, Apr 21, 2016 at 2:37 PM, Mark Post  wrote:

> >>> On 4/21/2016 at 05:33 PM, Grzegorz Powiedziuk 
> wrote:
> > then pvcreate, vgextend, lvextend and filesystem resize.
>
> No, we're trying to get him set up with LVM, just btrfs.
>
>
> 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: Simple DASD question

[Mark Post]

>>> On 4/21/2016 at 05:33 PM, Grzegorz Powiedziuk  
>>> wrote: 
> then pvcreate, vgextend, lvextend and filesystem resize.

No, we're trying to get him set up with LVM, just btrfs.


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: Simple DASD question

[Grzegorz Powiedziuk]

I cant remember how it is during install but I would make a bet that
default partitioning will not use more than one drive. Did you try to go
into advanced partitioning and see what the installator sugests? You should
be able manualy create one big lvm with seperate partition for boot (or you
can include boot in lvm but not all distros/versions support this). Unless
you want to do btrfs (I usually stick to ext3/4) then as we agreed lvm
doesn't make sense and btrfs volume pools should be used instead. But I
haven't done this before so can't tell.

But nontheless you still should be able to change it now if you do it step
by step from Mark's instructions.
So first make sure that second dasd is activated and available after ipl
(yast)
then pvcreate, vgextend, lvextend and filesystem resize.
Gregory

On Thursday, April 21, 2016, Tom Huegel  wrote:

> I don't know.. I've done a couple of re-installs and I still don't
> see dasdb (251) being used.
> This is SLES12 SP1. I activate and format my two drives and then take all
> of the defaults.
>
> 蘿
>
> On Thu, Apr 21, 2016 at 11:50 AM, Tom Huegel  > wrote:
>
> > Since this is a new install I'll just go back to step one and start with
> > reinstalling..
> > I'll let you know how it works out.
> >
> > On Thu, Apr 21, 2016 at 11:08 AM, Robert J Brenneman  >
> > wrote:
> >
> >> On Thu, Apr 21, 2016 at 2:00 PM, Grzegorz Powiedziuk <
> >> gpowiedz...@gmail.com >
> >> wrote:
> >>
> >> > I see. I never used btrfs before so it makes sense.
> >> > So  isn't using LVM with btrfs on top of it complicating things
> >> more?
> >> >
> >>
> >> Basically yes.
> >>
> >> The default SLES 12 install does not use LVM though, it only uses the
> >> btrfs
> >> functions to achieve similar results.
> >>
> >> Doing both LVM and btrfs is not impossible, but you need to be
> thoughtful
> >> about how you combine those two.
> >>
> >> --
> >> Jay Brenneman
> >>
> >> --
> >> 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/
>

--
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: Simple DASD question

[Mark Post]

>>> On 4/21/2016 at 05:03 PM, Tom Huegel  wrote: 
> I don't know.. I've done a couple of re-installs and I still don't
> see dasdb (251) being used.
> This is SLES12 SP1. I activate and format my two drives and then take all
> of the defaults.

That's because of the way the installer does things.  Once you have the install 
completed, use "yast dasd" to activate (and if needed format) the new volume. 
Then you'll need to use the btrfs command to add the new volume to the file 
system:
btrfs device add /dev/dasdb1 /

But, please, please, make sure you have all available maintenance installed 
before you do any of this, or make sure you have SLES12 *SP1* installed and 
updated with maintenance first.  Otherwise you're just going to wind up in the 
emergency shell again.


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: Simple DASD question

[Tom Huegel]

I don't know.. I've done a couple of re-installs and I still don't
see dasdb (251) being used.
This is SLES12 SP1. I activate and format my two drives and then take all
of the defaults.

蘿

On Thu, Apr 21, 2016 at 11:50 AM, Tom Huegel  wrote:

> Since this is a new install I'll just go back to step one and start with
> reinstalling..
> I'll let you know how it works out.
>
> On Thu, Apr 21, 2016 at 11:08 AM, Robert J Brenneman 
> wrote:
>
>> On Thu, Apr 21, 2016 at 2:00 PM, Grzegorz Powiedziuk <
>> gpowiedz...@gmail.com>
>> wrote:
>>
>> > I see. I never used btrfs before so it makes sense.
>> > So  isn't using LVM with btrfs on top of it complicating things
>> more?
>> >
>>
>> Basically yes.
>>
>> The default SLES 12 install does not use LVM though, it only uses the
>> btrfs
>> functions to achieve similar results.
>>
>> Doing both LVM and btrfs is not impossible, but you need to be thoughtful
>> about how you combine those two.
>>
>> --
>> Jay Brenneman
>>
>> --
>> 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: Simple DASD question

[Tom Huegel]

Since this is a new install I'll just go back to step one and start with
reinstalling..
I'll let you know how it works out.

On Thu, Apr 21, 2016 at 11:08 AM, Robert J Brenneman 
wrote:

> On Thu, Apr 21, 2016 at 2:00 PM, Grzegorz Powiedziuk <
> gpowiedz...@gmail.com>
> wrote:
>
> > I see. I never used btrfs before so it makes sense.
> > So  isn't using LVM with btrfs on top of it complicating things more?
> >
>
> Basically yes.
>
> The default SLES 12 install does not use LVM though, it only uses the btrfs
> functions to achieve similar results.
>
> Doing both LVM and btrfs is not impossible, but you need to be thoughtful
> about how you combine those two.
>
> --
> Jay Brenneman
>
> --
> 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: Simple DASD question

[Robert J Brenneman]

On Thu, Apr 21, 2016 at 2:00 PM, Grzegorz Powiedziuk 
wrote:

> I see. I never used btrfs before so it makes sense.
> So  isn't using LVM with btrfs on top of it complicating things more?
>

Basically yes.

The default SLES 12 install does not use LVM though, it only uses the btrfs
functions to achieve similar results.

Doing both LVM and btrfs is not impossible, but you need to be thoughtful
about how you combine those two.

--
Jay Brenneman

--
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: Simple DASD question

[Grzegorz Powiedziuk]

2016-04-21 13:39 GMT-04:00 Tom Huegel :

> Oh well I must have done something wrong, it won't boot (IPL) now.
> Booting default
> (grub2)
>
>
>
> [  OK  ] Found device
> /dev/disk/by-uuid/f75ec84d-5640-4a2c-bced-e026dd7ec2b9.
>
> 
> Warning: /dev/disk/by-uuid/2103a597-f950-4b63-931e-675d2c52dbd9 does not
> exist
>
>
>
It seems like the device is still missing. Did you run yast or
dasd_configure before doing all that and did it update initrd to have the
device available at boot time?
In dracut try a couple of basic commands like lsdasd  or cat
/proc/dasd/devices  to see if the second disk is actually there (probably
not)

--
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: Simple DASD question

[Mark Post]

 >>> On 4/21/2016 at 01:39 PM, Tom Huegel  wrote: 
> Starting Dracut Emergency
> Shell...
> 
> Warning: /dev/disk/by-uuid/2103a597-f950-4b63-931e-675d2c52dbd9 does not
> exist

This looks like the problem I warned you about previously.  When you're in the 
emergency shell, can you see both DASD volumes in /dev?
ls /dev/dasd*

If it is not there, then
echo 1 > /sys/bus/ccw/devices/0.0.0251/online

In some cases, the DASD volume would come online just after entering the 
emergency shell, and you could then see it:
ls /dev/disk/by-uuid/

If /dev/disk/by-uuid/2103a597-f950-4b63-931e-675d2c52dbd9 is there, you should 
be able to continue by doing a "systemctl default" command.

Once the system is up run mkinitrd and grub2-install.


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: Simple DASD question

[Grzegorz Powiedziuk]

2016-04-21 13:27 GMT-04:00 Robert J Brenneman :

>
> That's part of what the new btrfs in SLES 12 does for you. It does
> management of multiple physical block devices as a single logical entity,
> as well as talking that single logical entity and using it to back multiple
> mount points ( now called subvolumes ? ) to do things like snapshot just
> the /home section so you can do a rollback if you need to.
>
> It's part of the new SLES support to restore off service if required.
>
>
I see. I never used btrfs before so it makes sense.
So  isn't using LVM with btrfs on top of it complicating things more?

Gregory

--
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: Simple DASD question

[Mark Post]

>>> On 4/21/2016 at 12:04 PM, Tom Huegel  wrote: 
> Now I need just a little more help.
> Would this be correct to use all of the new volume? " lvextend -l +100%PVS
> /dev/system "

Almost, but not quite.  You would need to specify the logical volume name as 
/dev/system/root, not just /dev/system.

Perhaps an easier way would be
lvextend -l +1761 /dev/system/root

since that is the number of free physical extents you have as shown in the 
vgdisplay command.

After that, you have a couple more things to do, one of which is to actually 
resize the file system
btrfs filesystem resize max /

Having said all that, perhaps the better route is to re-install the system:
1. using SLES12 SP1 instead of just SLES12
2. not using LVM for volume management since btrfs can handle it by itself 
(SUSE recommends against using btrfs on top of LVM). I would have to check but 
btrfs on LVM might not be a supported configuration.

If you decide not to do that, make sure you have all available maintenance 
installed to avoid the problem I mentioned earlier with new DASD volumes not 
being activated properly at boot time.

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: Simple DASD question

[Tom Huegel]

Oh well I must have done something wrong, it won't boot (IPL) now.
Booting default
(grub2)

[  OK  ] Started Show Plymouth Boot
Screen.

[  OK  ] Reached target
Paths.

[  OK  ] Reached target Basic
System.

[  OK  ] Found device
/dev/disk/by-uuid/f75ec84d-5640-4a2c-bced-e026dd7ec2b9.

[  OK  ] Found device
/dev/mapper/system-swap.

Buffer I/O error on device dm-2, logical block
3172336

Buffer I/O error on device dm-2, logical block
3172336

[  OK  ] Started Show Plymouth Boot
Screen.

[  OK  ] Reached target
Paths.

[  OK  ] Reached target Basic
System.

[  OK  ] Found device
/dev/disk/by-uuid/f75ec84d-5640-4a2c-bced-e026dd7ec2b9.

[  OK  ] Found device
/dev/mapper/system-swap.

 Starting Dracut Emergency
Shell...

Warning: /dev/disk/by-uuid/2103a597-f950-4b63-931e-675d2c52dbd9 does not
exist


Generating
"/run/initramfs/rdsosreport.txt"

Buffer I/O error on device dm-2, logical block
3172336

Buffer I/O error on device dm-2, logical block
3172336

Buffer I/O error on device dm-2, logical block
3172336

Buffer I/O error on device dm-2, logical block
3172336





Entering emergency mode. Exit the shell to
continue.

Type "journalctl" to view system
logs.

You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or
/boot
after mounting them and attach it to a bug
report.





dracut:/#
1




HOLDING   SCZVMLX2

On Thu, Apr 21, 2016 at 10:27 AM, Robert J Brenneman 
wrote:

> On Thu, Apr 21, 2016 at 12:27 PM, Grzegorz Powiedziuk <
> gpowiedz...@gmail.com
> > wrote:
>
> > /dev/mapper/system-root  5.3G  3.0G  2.0G  60% /opt
> > /dev/mapper/system-root  5.3G  3.0G  2.0G  60% /home
> > /dev/mapper/system-root  5.3G  3.0G  2.0G  60% /boot/grub2/s390x-emu
> >
> >
> > According to this,  the same logical volume is mounted multiple times.
> > Honestly it doesn't make sense to me.
> >
>
> That's part of what the new btrfs in SLES 12 does for you. It does
> management of multiple physical block devices as a single logical entity,
> as well as talking that single logical entity and using it to back multiple
> mount points ( now called subvolumes ? ) to do things like snapshot just
> the /home section so you can do a rollback if you need to.
>
> It's part of the new SLES support to restore off service if required.
>
> --
> Jay Brenneman
>
> --
> 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: Simple DASD question

[Robert J Brenneman]

On Thu, Apr 21, 2016 at 12:27 PM, Grzegorz Powiedziuk  wrote:

> /dev/mapper/system-root  5.3G  3.0G  2.0G  60% /opt
> /dev/mapper/system-root  5.3G  3.0G  2.0G  60% /home
> /dev/mapper/system-root  5.3G  3.0G  2.0G  60% /boot/grub2/s390x-emu
>
>
> According to this,  the same logical volume is mounted multiple times.
> Honestly it doesn't make sense to me.
>

That's part of what the new btrfs in SLES 12 does for you. It does
management of multiple physical block devices as a single logical entity,
as well as talking that single logical entity and using it to back multiple
mount points ( now called subvolumes ? ) to do things like snapshot just
the /home section so you can do a rollback if you need to.

It's part of the new SLES support to restore off service if required.

--
Jay Brenneman

--
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: Simple DASD question

[Grzegorz Powiedziuk]

I am not sure about "PVS"  but "FREE" will work
You want to extend the LV so it should be rather something like this:

lvextend -l +100%FREE /dev/system/root(or /dev/mapper/system-root)

(/dev/system is a Volume group which from I can see has been already
extended - it has 7GB free )

Of course it that is what you want to do? Extend the size of root logical
volume?
Next you will have to resize the filesystem. If it is ext3 or ext4 you can
just do resize2fs /dev/system/root   and it will use all free space.


But, what I don't like, is the output of your "df" command. Nobody said
anything about it before so I guess it is ok, but I've never seen something
like this:

/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/tmp
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/spool
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/opt
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/log
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/lib/pgsql
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/lib/mailman
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/crash
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /usr/local
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/lib/named
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /tmp
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /srv
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /opt
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /home
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /boot/grub2/s390x-emu


According to this,  the same logical volume is mounted multiple times.
Honestly it doesn't make sense to me.
There should be just one mount point if you have only one logical volume
"root" without separate volumes for other mount points.
/dev/mapper/system-root  xxx xxx xxx 60% /

And that's it.


Gregory

2016-04-21 12:04 GMT-04:00 Tom Huegel :

> Now I need just a little more help.
> Would this be correct to use all of the new volume? " lvextend -l +100%PVS
> /dev/system "
> Thanks
>
> sles12:~ # vgdisplay
>   --- Volume group ---
>   VG Name   system
>   System ID
>   Formatlvm2
>   Metadata Areas2
>   Metadata Sequence No  4
>   VG Access read/write
>   VG Status resizable
>   MAX LV0
>   Cur LV2
>   Open LV   2
>   Max PV0
>   Cur PV2
>   Act PV2
>   VG Size   13.55 GiB
>   PE Size   4.00 MiB
>   Total PE  3470
>   Alloc PE / Size   1709 / 6.68 GiB
>   Free  PE / Size   1761 / 6.88 GiB
>   VG UUID   8wdm3K-4TNN-yqqn-v4bG-vBFE-INMc-AIZCxT
>
>
> On Wed, Apr 20, 2016 at 8:06 AM, Mark Post  wrote:
>
> > >>> On 4/19/2016 at 04:42 PM, Michael J Nash 
> wrote:
> > > Greeting Mark, please tell us why  use_lvmetad  has been disabled!
> >
> > It wasn't considered ready for enterprise use.
> >
> >
> > 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/
>

--
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: Simple DASD question

[Tom Huegel]

Now I need just a little more help.
Would this be correct to use all of the new volume? " lvextend -l +100%PVS
/dev/system "
Thanks

sles12:~ # vgdisplay
  --- Volume group ---
  VG Name   system
  System ID
  Formatlvm2
  Metadata Areas2
  Metadata Sequence No  4
  VG Access read/write
  VG Status resizable
  MAX LV0
  Cur LV2
  Open LV   2
  Max PV0
  Cur PV2
  Act PV2
  VG Size   13.55 GiB
  PE Size   4.00 MiB
  Total PE  3470
  Alloc PE / Size   1709 / 6.68 GiB
  Free  PE / Size   1761 / 6.88 GiB
  VG UUID   8wdm3K-4TNN-yqqn-v4bG-vBFE-INMc-AIZCxT


On Wed, Apr 20, 2016 at 8:06 AM, Mark Post  wrote:

> >>> On 4/19/2016 at 04:42 PM, Michael J Nash  wrote:
> > Greeting Mark, please tell us why  use_lvmetad  has been disabled!
>
> It wasn't considered ready for enterprise use.
>
>
> 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: Simple DASD question

[Mark Post]

>>> On 4/19/2016 at 04:42 PM, Michael J Nash  wrote: 
> Greeting Mark, please tell us why  use_lvmetad  has been disabled!

It wasn't considered ready for enterprise use.


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: Simple DASD question

[Michael J Nash]

Greeting Mark, please tell us why  use_lvmetad  has been disabled!



From:   Mark Post <mp...@suse.com>
To: LINUX-390@VM.MARIST.EDU
Date:   04/19/2016 04:25 PM
Subject:    Re: Simple DASD question
Sent by:Linux on 390 Port <LINUX-390@VM.MARIST.EDU>



>>> On 4/19/2016 at 04:12 PM, Michael J Nash <miken...@us.ibm.com> wrote:
> vi /etc/lvm/lvm.conf
> Set use_lvmetad=1

I would not do that on a SLES12 system. There's a reason we left it
disabled until SLES12 SP1.


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: Simple DASD question

[Mark Post]

>>> On 4/19/2016 at 04:12 PM, Michael J Nash  wrote: 
> vi /etc/lvm/lvm.conf
> Set use_lvmetad=1

I would not do that on a SLES12 system. There's a reason we left it disabled 
until SLES12 SP1.


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: Simple DASD question

[Dan Horák]

On Tue, 19 Apr 2016 11:51:17 -0700
Tom Huegel  wrote:

> I am sure the answer must be simple.
> How can I tell if a disk (3390-9) is actually being used?
>
> Background:
> I just installed SUSE 12 specifying 2 3390-9 on the installation
> panel. I tried to add a package and I get 'no space on DASD'
> condition. I am guessing the installation only used the first disk,
> but how can I be sure?
> Assuming I can determine the second disk is unused I should be able to
> extend the LVM to it and my problem would be solved. Right?

lsdasd (as already suggested) and lsblk will give you good overview what
uses what


Dan

--
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: Simple DASD question

[Michael J Nash]

Greetings, Not sure why you received your initial message of not having
enough space.
You appear to have enough.  You should address this problem first.
How did you try to install the package?  What was the exact error message?


Display the partition table: fdasd -p /dev/dasd?
 I think if you edit lvm.conf you will get rid of the warning messages.
 You can also turn on verbose. I I think the levels are 0-7.  A "1" is
good.
vi /etc/lvm/lvm.conf
Set use_lvmetad=1



From:   Mark Post <mp...@suse.com>
To: LINUX-390@VM.MARIST.EDU
Date:   04/19/2016 03:53 PM
Subject:    Re: Simple DASD question
Sent by:Linux on 390 Port <LINUX-390@VM.MARIST.EDU>



>>> On 4/19/2016 at 03:33 PM, Tom Huegel <tehue...@gmail.com> wrote:
> sles12:~ # pvscan -v
> connect() failed on local socket: No such file or directory
> Internal cluster locking initialisation failed.
> WARNING: Falling back to local file-based locking.
> Volume Groups with the clustered attribute will be inaccessible.
> Wiping cache of LVM-capable devices
> Wiping internal VG cache
> Walking through all physical volumes
> PV /dev/dasda2   VG system   lvm2 [6.68 GiB / 4.00 MiB free]
> Total: 1 [6.68 GiB] / in use: 1 [6.68 GiB] / in no VG: 0 [0   ]

This shows that only /dev/dasda2 is in use by LVM.


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: Simple DASD question

[Mark Post]

>>> On 4/19/2016 at 03:33 PM, Tom Huegel  wrote: 
> sles12:~ # pvscan -v
> connect() failed on local socket: No such file or directory
> Internal cluster locking initialisation failed.
> WARNING: Falling back to local file-based locking.
> Volume Groups with the clustered attribute will be inaccessible.
> Wiping cache of LVM-capable devices
> Wiping internal VG cache
> Walking through all physical volumes
> PV /dev/dasda2   VG system   lvm2 [6.68 GiB / 4.00 MiB free]
> Total: 1 [6.68 GiB] / in use: 1 [6.68 GiB] / in no VG: 0 [0   ]

This shows that only /dev/dasda2 is in use by LVM.


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: Simple DASD question

[Nix, Robert P.]

SoŠ The significant parts are in the lsdasd (251 is seen, and attached to
Linux as /dev/dasdb), the df (dasdb isn¹t listed at all), and pvscan (only
/dev/dasda2 is listed.

So now, you¹ll want to do a dasdfmt for /dev/dasdb, and then a pvcreate
/dev/dasdb1, then vgextend system /dev/dasdb1. Check the man page for
dasdfmt. You¹ll want just the one partition. After all this, the space
will be in volume group system, and you can allocate it to a new logical
volume, or extend one that already exists. If you use lvextend, remember
to run resize2fs afterward. If you use lvcreate, then be sure to run mkfs
afterward, and then add it somewhere in your fstab so that it will get
mounted on reboot.
-- 
Robert P. Nix | Sr IT Systems Engineer | Data Center Infrastructure
Services

Mayo Clinic | 200 First Street SW | Rochester, MN 55905
507-284-0844 | nix.rob...@mayo.edu
"quando omni flunkus moritati"




On 4/19/16, 2:33 PM, "Linux on 390 Port on behalf of Tom Huegel"
<LINUX-390@VM.MARIST.EDU on behalf of tehue...@gmail.com> wrote:

>sles12:~ # lsdasd
>Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
>==
>
>0.0.0250   active  dasda 94:0ECKD  4096   7042MB1802880
>0.0.0251   active  dasdb 94:4ECKD  4096   7042MB1802880
>sles12:~ # df -h
>Filesystem   Size  Used Avail Use% Mounted on
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /
>devtmpfs 439M 0  439M   0% /dev
>tmpfs446M  324K  446M   1% /dev/shm
>tmpfs446M   46M  400M  11% /run
>tmpfs446M 0  446M   0% /sys/fs/cgroup
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/tmp
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/spool
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/opt
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/log
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/lib/pgsql
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/lib/mailman
>/dev/dasda1  194M   25M  160M  14% /boot/zipl
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/crash
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /usr/local
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/lib/named
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /tmp
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /srv
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /opt
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /home
>/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /boot/grub2/s390x-emu
>sles12:~ # vgscan
>sles12:~ # pvscan
>sles12:~ # lvscan
>sles12:~ # man vgscan
>sles12:~ # vgscan -v
>connect() failed on local socket: No such file or directory
>Internal cluster locking initialisation failed.
>WARNING: Falling back to local file-based locking.
>Volume Groups with the clustered attribute will be inaccessible.
>Wiping cache of LVM-capable devices
>Wiping internal VG cache
>Reading all physical volumes.  This may take a while...
>Finding all volume groups
>Finding volume group "system"
>Found volume group "system" using metadata type lvm2
>sles12:~ # pvscan -v
>connect() failed on local socket: No such file or directory
>Internal cluster locking initialisation failed.
>WARNING: Falling back to local file-based locking.
>Volume Groups with the clustered attribute will be inaccessible.
>Wiping cache of LVM-capable devices
>Wiping internal VG cache
>Walking through all physical volumes
>PV /dev/dasda2   VG system   lvm2 [6.68 GiB / 4.00 MiB free]
>Total: 1 [6.68 GiB] / in use: 1 [6.68 GiB] / in no VG: 0 [0   ]
>sles12:~ # lvscan -v
>connect() failed on local socket: No such file or directory
>Internal cluster locking initialisation failed.
>WARNING: Falling back to local file-based locking.
>Volume Groups with the clustered attribute will be inaccessible.
>Finding all logical volumes
>ACTIVE'/dev/system/root' [5.22 GiB] inherit
>ACTIVE'/dev/system/swap' [1.45 GiB] inherit
>sles12:~ #
>
>On Tue, Apr 19, 2016 at 12:15 PM, Michael J Nash <miken...@us.ibm.com>
>wrote:
>
>> Greetings, please provide some more information.
>> The output from the following commands will help.
>>
>> lsdasd will show you what devices are online.
>> df -h will show you your utilization
>> vgscan - will show you the lvm groups
>> pvscan - will show you the physical volumes
>> lvscan - will show you the lvm volumes
>>
>> You can use the man command on each of these commands to learn how to
>>use
>> them.
>>
>>
>>

Re: Simple DASD question

[Tom Huegel]

sles12:~ # lsdasd
Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
==
0.0.0250   active  dasda 94:0ECKD  4096   7042MB1802880
0.0.0251   active  dasdb 94:4ECKD  4096   7042MB1802880
sles12:~ # df -h
Filesystem   Size  Used Avail Use% Mounted on
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /
devtmpfs 439M 0  439M   0% /dev
tmpfs446M  324K  446M   1% /dev/shm
tmpfs446M   46M  400M  11% /run
tmpfs446M 0  446M   0% /sys/fs/cgroup
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/tmp
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/spool
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/opt
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/log
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/lib/pgsql
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/lib/mailman
/dev/dasda1  194M   25M  160M  14% /boot/zipl
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/crash
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /usr/local
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /var/lib/named
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /tmp
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /srv
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /opt
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /home
/dev/mapper/system-root  5.3G  3.0G  2.0G  60% /boot/grub2/s390x-emu
sles12:~ # vgscan
sles12:~ # pvscan
sles12:~ # lvscan
sles12:~ # man vgscan
sles12:~ # vgscan -v
connect() failed on local socket: No such file or directory
Internal cluster locking initialisation failed.
WARNING: Falling back to local file-based locking.
Volume Groups with the clustered attribute will be inaccessible.
Wiping cache of LVM-capable devices
Wiping internal VG cache
Reading all physical volumes.  This may take a while...
Finding all volume groups
Finding volume group "system"
Found volume group "system" using metadata type lvm2
sles12:~ # pvscan -v
connect() failed on local socket: No such file or directory
Internal cluster locking initialisation failed.
WARNING: Falling back to local file-based locking.
Volume Groups with the clustered attribute will be inaccessible.
Wiping cache of LVM-capable devices
Wiping internal VG cache
Walking through all physical volumes
PV /dev/dasda2   VG system   lvm2 [6.68 GiB / 4.00 MiB free]
Total: 1 [6.68 GiB] / in use: 1 [6.68 GiB] / in no VG: 0 [0   ]
sles12:~ # lvscan -v
connect() failed on local socket: No such file or directory
Internal cluster locking initialisation failed.
WARNING: Falling back to local file-based locking.
Volume Groups with the clustered attribute will be inaccessible.
Finding all logical volumes
ACTIVE'/dev/system/root' [5.22 GiB] inherit
ACTIVE'/dev/system/swap' [1.45 GiB] inherit
sles12:~ #

On Tue, Apr 19, 2016 at 12:15 PM, Michael J Nash <miken...@us.ibm.com>
wrote:

> Greetings, please provide some more information.
> The output from the following commands will help.
>
> lsdasd will show you what devices are online.
> df -h will show you your utilization
> vgscan - will show you the lvm groups
> pvscan - will show you the physical volumes
> lvscan - will show you the lvm volumes
>
> You can use the man command on each of these commands to learn how to use
> them.
>
>
>
>
> From:   Mark Pace <pacemainl...@gmail.com>
> To: LINUX-390@VM.MARIST.EDU
> Date:   04/19/2016 02:58 PM
> Subject:Re: Simple DASD question
> Sent by:Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
>
>
>
> You could try.
>
> sles003:~> /sbin/lsdasd
> Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
>
> ==
>
> 0.0.0201   active  dasda 94:0ECKD  ???7042MB???
>
>
> On Tue, Apr 19, 2016 at 2:51 PM, Tom Huegel <tehue...@gmail.com> wrote:
>
> > I am sure the answer must be simple.
> > How can I tell if a disk (3390-9) is actually being used?
> >
> > Background:
> > I just installed SUSE 12 specifying 2 3390-9 on the installation panel.
> > I tried to add a package and I get 'no space on DASD' condition.
> > I am guessing the installation only used the first disk, but how can I be
> > sure?
> > Assuming I can determine the second disk is unused I should be able to
> > extend the LVM to it and my problem would be solved. Right?
> >
> > Thanks
> > Tom
> >
> > --
> > For LINUX-390 subscribe / signoff / archiv

Re: Simple DASD question

[Michael J Nash]

Greetings, please provide some more information.
The output from the following commands will help.

lsdasd will show you what devices are online.
df -h will show you your utilization
vgscan - will show you the lvm groups
pvscan - will show you the physical volumes
lvscan - will show you the lvm volumes

You can use the man command on each of these commands to learn how to use
them.




From:   Mark Pace <pacemainl...@gmail.com>
To: LINUX-390@VM.MARIST.EDU
Date:   04/19/2016 02:58 PM
Subject:    Re: Simple DASD question
Sent by:Linux on 390 Port <LINUX-390@VM.MARIST.EDU>



You could try.

sles003:~> /sbin/lsdasd
Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
==

0.0.0201   active  dasda 94:0ECKD  ???7042MB???


On Tue, Apr 19, 2016 at 2:51 PM, Tom Huegel <tehue...@gmail.com> wrote:

> I am sure the answer must be simple.
> How can I tell if a disk (3390-9) is actually being used?
>
> Background:
> I just installed SUSE 12 specifying 2 3390-9 on the installation panel.
> I tried to add a package and I get 'no space on DASD' condition.
> I am guessing the installation only used the first disk, but how can I be
> sure?
> Assuming I can determine the second disk is unused I should be able to
> extend the LVM to it and my problem would be solved. Right?
>
> Thanks
> Tom
>
> --
> 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/
>



--
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
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: Simple DASD question

[Duerbusch, Tom]

df would show something like this (for a dual disk system):
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/dasda17098008   352   3292988  52% /
devtmpfs510668   100510568   1% /dev
tmpfs   51066816510652   1% /dev/shm
/dev/dasdb17098008925552   5811888  14% /home

In this case, dasda1 has the root directory "/".
dasdb1 has the home subdirectory "/home".

Tom Duerbusch
THD Consulting


On Tue, Apr 19, 2016 at 1:51 PM, Tom Huegel  wrote:

> I am sure the answer must be simple.
> How can I tell if a disk (3390-9) is actually being used?
>
> Background:
> I just installed SUSE 12 specifying 2 3390-9 on the installation panel.
> I tried to add a package and I get 'no space on DASD' condition.
> I am guessing the installation only used the first disk, but how can I be
> sure?
> Assuming I can determine the second disk is unused I should be able to
> extend the LVM to it and my problem would be solved. Right?
>
> Thanks
> Tom
>
> --
> 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: Simple DASD question

[Tom Huegel]

Got it.. Thanks

On Tue, Apr 19, 2016 at 12:05 PM, Mark Post  wrote:

> >>> On 4/19/2016 at 02:51 PM, Tom Huegel  wrote:
> > I am sure the answer must be simple.
> > How can I tell if a disk (3390-9) is actually being used?
> >
> > Background:
> > I just installed SUSE 12 specifying 2 3390-9 on the installation panel.
> > I tried to add a package and I get 'no space on DASD' condition.
> > I am guessing the installation only used the first disk, but how can I be
> > sure?
>
> Several ways:
> lsdasd -> If it doesn't show up at all it's not being used
> df -> Same
>
> > Assuming I can determine the second disk is unused I should be able to
> > extend the LVM to it and my problem would be solved. Right?
>
> Since you're using LVM, then another way to check if the volume is being
> used by LVM is
> the "pvs" or "pvdisplay" commands.  If the volume doesn't show up there,
> it is not being used by LVM.
>
> Now, if you're going to add another disk to the configuration, make sure
> you
> - Use either YaST or dasd_configure to bring the disk online and have it
> be persistent across a reboot.
> - Re-run mkinitrd and zipl afterward because early on in SLES12 there was
> a bug that would cause new disks to not be activated properly on reboot.
>
>
> 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: Simple DASD question

[Tom Huegel]

But I have no idea if 0251 is actually used.. How can I see if it has
7042MB of free space or something less?


sles12:~ # /sbin/lsdasd
Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
==
0.0.0250   active  dasda 94:0ECKD  4096   7042MB1802880
0.0.0251   active  dasdb 94:4ECKD  4096   7042MB1802880
sles12:~ #

On Tue, Apr 19, 2016 at 11:57 AM, Mark Pace  wrote:

> You could try.
>
> sles003:~> /sbin/lsdasd
> Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
>
> ==
> 0.0.0201   active  dasda 94:0ECKD  ???7042MB???
>
>
> On Tue, Apr 19, 2016 at 2:51 PM, Tom Huegel  wrote:
>
> > I am sure the answer must be simple.
> > How can I tell if a disk (3390-9) is actually being used?
> >
> > Background:
> > I just installed SUSE 12 specifying 2 3390-9 on the installation panel.
> > I tried to add a package and I get 'no space on DASD' condition.
> > I am guessing the installation only used the first disk, but how can I be
> > sure?
> > Assuming I can determine the second disk is unused I should be able to
> > extend the LVM to it and my problem would be solved. Right?
> >
> > Thanks
> > Tom
> >
> > --
> > 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/
> >
>
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> 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: Simple DASD question

[Mark Post]

>>> On 4/19/2016 at 02:51 PM, Tom Huegel  wrote: 
> I am sure the answer must be simple.
> How can I tell if a disk (3390-9) is actually being used?
> 
> Background:
> I just installed SUSE 12 specifying 2 3390-9 on the installation panel.
> I tried to add a package and I get 'no space on DASD' condition.
> I am guessing the installation only used the first disk, but how can I be
> sure?

Several ways:
lsdasd -> If it doesn't show up at all it's not being used
df -> Same

> Assuming I can determine the second disk is unused I should be able to
> extend the LVM to it and my problem would be solved. Right?

Since you're using LVM, then another way to check if the volume is being used 
by LVM is
the "pvs" or "pvdisplay" commands.  If the volume doesn't show up there, it is 
not being used by LVM.

Now, if you're going to add another disk to the configuration, make sure you
- Use either YaST or dasd_configure to bring the disk online and have it be 
persistent across a reboot.
- Re-run mkinitrd and zipl afterward because early on in SLES12 there was a bug 
that would cause new disks to not be activated properly on reboot.


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: Simple DASD question

[Mark Pace]

You could try.

sles003:~> /sbin/lsdasd
Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
==
0.0.0201   active  dasda 94:0ECKD  ???7042MB???


On Tue, Apr 19, 2016 at 2:51 PM, Tom Huegel  wrote:

> I am sure the answer must be simple.
> How can I tell if a disk (3390-9) is actually being used?
>
> Background:
> I just installed SUSE 12 specifying 2 3390-9 on the installation panel.
> I tried to add a package and I get 'no space on DASD' condition.
> I am guessing the installation only used the first disk, but how can I be
> sure?
> Assuming I can determine the second disk is unused I should be able to
> extend the LVM to it and my problem would be solved. Right?
>
> Thanks
> Tom
>
> --
> 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/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

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

Simple DASD question

[Tom Huegel]

I am sure the answer must be simple.
How can I tell if a disk (3390-9) is actually being used?

Background:
I just installed SUSE 12 specifying 2 3390-9 on the installation panel.
I tried to add a package and I get 'no space on DASD' condition.
I am guessing the installation only used the first disk, but how can I be
sure?
Assuming I can determine the second disk is unused I should be able to
extend the LVM to it and my problem would be solved. Right?

Thanks
Tom

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