Hi
Also beware that KVM host and KVM guest cannot use the same FS nor belong to the same cluster
Please see FAQ https://www.ibm.com/docs/en/spectrum-scale?topic=STXKQY/gpfsclustersfaq.html#gpfsclustersfaqAugust2016-gen4__virtualizationlimitsq
Not saying it does not work, stating what the
On 10/06/2021 15:00, Ryan Novosielski wrote:>
The problem with not version locking the kernel, however, is that you
really need to know that the kernel you are going to is going to
support the GPFS version that you are going to be running. Typically
that only becomes a problem when you cross a
I think I found the document you are talking about. In general I believe most
of it still applies. I can make the following comments on it about Spectrum
Scale:
1 - There was an effort to simplify Spectrum Scale tuning, and tuning of
worker1Threads should be replaced by tuning workerThreads
We manage kernel updates pretty carefully ... not least because there is a good
chance MOFED will also break at the same time.
We do have a similar systemd unit that tries to install from our local repos,
then tries to build locally.
Simon
On 10/06/2021, 15:01,
The problem with not version locking the kernel, however, is that you really
need to know that the kernel you are going to is going to support the GPFS
version that you are going to be running. Typically that only becomes a problem
when you cross a minor release boundary on RHEL-derivatives,
Thanks, Jonathan, I've been thinking about how to manage this as well and
like it more than version-locking the kernel.
On Wed, Jun 09, 2021 at 09:28:07PM +0100, Jonathan Buzzard wrote:
>
> So you need to apply a kernel update and that means a new gpfs.gplbin :-( So
> after going around the
Hi Wally,
I don't see a dedicated document for DB2 from Scale document sets, however,
usually the workloads of database are doing direct I/O, so those
documentation sections in Scale for direct I/O should be good to review.
Here I have a list about tunings for direct I/O for your reference.
