MDS runs kernel 3.10.0-957.el7_lustre, from downloads.whamcloud ->
lustre-2.10.6-ib, on CentOS 7.5
On 13.11.19 18:20, Colin Faber wrote:
Which kernel are you running?
https://access.redhat.com/solutions/3393611
On Wed, Nov 13, 2019 at 4:28 AM Thomas Roth wrote:
Hi all,
we keep hitting LU
Indeed, that's the one I was looking for.
Interesting: why would Google give me different Jira-hits when searching for the same term, from two different by close-by internet-entry points in
Germany, from two Firefoxes of the same version, running on Debian or Ubuntu, no JavaScript, no cookies in
Which kernel are you running?
https://access.redhat.com/solutions/3393611
On Wed, Nov 13, 2019 at 4:28 AM Thomas Roth wrote:
> Hi all,
>
> we keep hitting LU-10697, which makes the users' experience quite painful.
> There was a related issue in Lustre 2.12/2.13 which is also unresolved -
> can'
Thanks Andreas!
Comparing “zpool get all” on both systems I found ashift is 0 on both systems –
but a number of features are different on the “bad” mdt. Except for “extensible
dataset” they are all enabled on the “bad” one. Could one of them be the
problem? Is it possible to change those featur
On Wed, Nov 13, 2019 at 4:28 AM Thomas Roth wrote:
> Hi all,
>
> we keep hitting LU-10697, which makes the users' experience quite painful.
> There was a related issue in Lustre 2.12/2.13 which is also unresolved -
> can't find the LU- at the moment.
>
>
Thomas,
Perhaps you are looking for LU-12
Hi all,
we keep hitting LU-10697, which makes the users' experience quite painful.
There was a related issue in Lustre 2.12/2.13 which is also unresolved - can't
find the LU- at the moment.
In any case, it always looks like
Nov 13 10:23:58 lxmds19.gsi.de kernel: Pid: 6449, comm: mdt00_095 3.1
