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 de
>>> 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
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 g
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 i
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
>>> 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
M
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
>>> 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
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 i
>>> 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.
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
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
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
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-675d2c52dbd
>>> 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
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 call
>>> 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.
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 ] Fou
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 mou
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
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
>>> 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
Greeting Mark, please tell us why use_lvmetad has been disabled!
From: Mark Post
To: LINUX-390@VM.MARIST.EDU
Date: 04/19/2016 04:25 PM
Subject:Re: Simple DASD question
Sent by:Linux on 390 Port
>>> On 4/19/2016 at 04:12 PM, Michael J Nash wrote:
>
>>> 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 subscri
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'
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
To: LINUX-390@VM.MARIST.EDU
Date: 04/19/2016 03:53 PM
Subject: Re: Simple DASD questi
>>> 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
ng 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
>>
>>
> From: Mark Pace
> To: LINUX-390@VM.MARIST.EDU
> Date: 04/19/2016 02:58 PM
> Subject:Re: Simple DASD question
> Sent by:Linux on 390 Port
>
>
>
> You could try.
>
> sles003:~> /sbin/lsdasd
> Bus-ID Status Name Device T
volumes
You can use the man command on each of these commands to learn how to use
them.
From: Mark Pace
To: LINUX-390@VM.MARIST.EDU
Date: 04/19/2016 02:58 PM
Subject:Re: Simple DASD question
Sent by:Linux on 390 Port
You could try.
sles003:~> /sbin/lsdasd
Bus
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
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
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 ac
>>> 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' con
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 Hu
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 dis
36 matches
Mail list logo
