On 05/30/2017 02:50 PM, Marcy Cortes wrote:
> Did you do a "vgreduce VGname /dev/dasd*"
>
> If you missed that step, you can probably fix it with "vgreduce
> --removemissing VGname"
Hi Marcy,
Yes, I did that followed by pvremove on each device.
> You'll want to get rid of them from linux too
Hi,
We have a situation with two SLES11 servers. We had to migrate the
underlying PVs used for the swap logical volume (we used pvmove to move
from DASD to FCP LUNs) and then we removed the DASD PVs from the volume
group (followed by pvremove on them to wipe LVM metadata). After that I
called
On 05/11/2017 08:02 PM, Dominic Coulombe wrote:
> Is this what you're looking for?
>
> http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10877
Hi Dominic,
You've nailed it! Thanks for the link! I had no idea about these
Techdocs Library Flashes!
I'm glad to hear it's finally
Hi everyone,
Does anyone here knows if we will ever see Oracle certify its DB against
SLES 12 on s390x? It has been a while since they certified it against x86.
If I ask IBM about it they (appropriately) tell me to ask Oracle. If I
ask Oracle they tell me to open a support case. If I open a
On 08/17/2016 12:14 PM, Mark Post wrote:
> I'm hoping that when people are saying "SLES12" they are really
> meaning "SLES12 SP1 or later." SLES12 GA has been out of support for
> a while now.
Oh, definitely. For sure :) As soon as we jump in we'll grab the latest...
> With SLES12, zipl really
On 08/16/2016 02:45 PM, Marcy Cortes wrote:
> Was wondering what other people have decided to do for their file systems in
> SLES 12.
> Stable tried and try ext3 or new function (and more space) with btrfs.
I'm looking forward to btrfs on SLES 12; specifically its snapshot
capabilities and how
On 08/16/2016 06:20 PM, Rick Troth wrote:
> The problem with EXT3/4 is mostly that the EXT*FS family has fallen out
> of popularity. They're rock solid. They just work
Is ext4 available con SLES 12 (s390x)? We haven't tried SLES 12 yet as
we're waiting for Oracle to certify its database against
On 08/03/2016 05:30 PM, Marcy Cortes wrote:
> Yes, we saw it and someone else here did last week too.
> SUSE has a test fix for it.
>
> Has to do with running 32bit programs. ILMT was the one that we discovered
> it with.
Thanks Marcy! I googled it for a while but couldn't find it. I'll
search
Hi everyone,
We're having some kernel locking issues after installing the latest
kernel for SLES 11 SP4 (kernel-default-3.0.101-77.1). This is on two
separate Linux guests and it happens - right away- after starting some
network applications: Linux completely freezes. If we go back to the
On 01/24/2016 07:37 PM, Mark Post wrote:
> I haven't tried it myself, but perhaps the zfcp_san_disc command would be of
> use here.
Thanks Mark. That's a new one to me. I'll try the next time I have an
opportunity with changes on the fabric (other than new LUNs).
Regards,
Jorge
On 01/25/2016 07:47 PM, Raymond Higgs wrote:
> Zfcp_san_disc, and many other tools typically only display what Linux
> already knows about. If you start with the device offline, then it'll
> bring the device online and show you what is currently in the fabric. If
> you start with the device
On 01/23/2016 02:29 PM, Offer Baruch wrote:
> Did you try simply taking the fcp devices offline and then online again?
> That should be enough... (although that shouldn`t be necessary in the first
> place).
Hi,
No. I haven't for these initial deployments but now that you mention
it, I remember
Hi,
We have an issue with new deployed systems from our SLES 11 SP4 template
(They all have "zfcp.allow_lun_scan=1" on their zipl.conf file).
Whenever the z/VM admin deploys a new image, he would assign two FCP
devices. After that we take control of the system and:
1) verify FCP devices are
On 09/17/2015 09:15 AM, Jorge Fábregas wrote:
> Is there some specialty processor in the mainframe implementing either
> gzip, bzip2 or lzma that one could offload compression tasks to?
Thank you guys for pointing me to zEDC. That's indeed what I was
looking for. We have the zEC12
Hi,
I'm new to Linux on Z. I'm setting up a syslog server which is going to
receive a bunch of data and, of course, I'll be using logrotate to
rotate logs & *compress* them. I want to be a good neighbor when it
comes to processing time so
Is there some specialty processor in the mainframe
On 09/15/2015 05:43 PM, Neale Ferguson wrote:
> The underlying CP service Diagnose x’288’ takes a parameter specifying the
> time bomb interval in seconds. So it’s a function of the module.
>
> According to the source code of vmwatchdog.c there is an IOCTL that may be
> issued that will change
On 09/14/2015 06:31 PM, Jorge Fábregas wrote:
> If I can't change it via the module, is this timeout configurable at the
> z/VM level (so I can tell the z/VM admin)?
Bump :)
--
For LINUX-390 subscribe / signoff / archive
Hi,
I need to use the watchdog provided by z/VM (with the vmwatchdog kernel
module) but I've just found out its "timeout value" isn't configurable.
There's no module parameter for that. It's hardcoded at 1 minute (I
had plans to change it to 5 seconds or 10 seconds).
If I can't change it via
Hi,
I'm about to start a High-Availability project with SLES 11 SP4 where I
plan to use snIPl (to fence Linux guests via z/VM). I know there's the
SBD (storage-based fencing) as well (that SUSE seems to promote a lot)
and wondered if anyone here had any experience with one or the other
(which
Hi,
I'm new on the list, so hello to everyone!
Is there something similar to RHEL's tuned-adm in SLES 11? This is a
tool that includes some predefined profiles for typical use cases
(virtual guest, storage-server, desktop etc) and, when you choose a
profile, it goes out and tweaks all
20 matches
Mail list logo
