Hi Alastair,
You can mount the client with -o network=tcp, this did the job in our
case.
Cheers,
Marek
W dniu czw, 06.02.2020 o godzinie 16∶28 +, użytkownik BASDEN,
ALASTAIR G. napisał:
> Hi,
> We are mounting a 2.12.2 server on a 2.12.3 client.
>
> Both have @o2ib and @tcp networks.
>
>
Hi Sebastien,
Thanks for looking into this.
You are right that nodemap deactivation didn't affect the outcome. I
must have made a mistake and cannot reproduce.
The uid/gid are on the mds. I can do a sudo to the user and run the test
program successfully.
I forgot to mention that I use SSK in
Hi,
I am not able to reproduce your issue. I compiled your C program, in all cases
I am not getting Permission Denied.
You say that it works when you deactivate the nodemap. But given that you have
a fileset on your nodemap entry « sif », when you deactivate it you might end
up doing IOs in a
Hi,
We are mounting a 2.12.2 server on a 2.12.3 client.
Both have @o2ib and @tcp networks.
However, there is no link between them on the @o2ib.
We are therefore mounting on @tcp, have network=tcp0 in the fstab, and
have switched discovery off.
This works, metadata can be read and created, and
We're running 2.13.0 server on Ubuntu Bionic 18.04 with 4.15 kernel in
our test setup. Has been working without any real problems for a couple
of weeks. But it is a small test setup so...
For clients we have 2.10.7 from DDN on our production Ubuntu Xenial
systems (with HWE kernel so 4.15)
On
Hi Matthias,
last time we tried this (Debian Wheezy + Lustre 2.5) we had to use the Redhat
kernel _in_ Debian.
However, nowadays there is the patchless-ldiskfs-server, and of course the server based on ZFS, both of which would require only to compile the proper
modules.
My guess is that you
Hi,
Thanks for a very quick reply :-) Here are the map:
# lctl get_param nodemap.sif.*
nodemap.sif.admin_nodemap=1
nodemap.sif.audit_mode=1
nodemap.sif.deny_unknown=0
nodemap.sif.exports=
[
{ nid: 172.25.10.51@tcp, uuid: 56bb9b04-9bb5-d7b5-3f50-d62804690db1 },
]
nodemap.sif.fileset=/sif
Hi,
It might be due to a property on the nodemap you defined.
Could you please dump your nodemap definition?
Thanks,
Sebastien.
> Le 6 févr. 2020 à 14:14, Hans Henrik Happe a écrit :
>
> Hi,
>
> Has anyone had success with gocryptfs 1.7.x on top of a Lustre nodemap?
>
> I've tested with
Hi,
Has anyone had success with gocryptfs 1.7.x on top of a Lustre nodemap?
I've tested with Lustre 2.12.3.
I found that gocryptfs 1.6 worked. However, with 1.7.x I got a lot of
"Permission denied". I tried all permutations of trusted and admin on
the nodemap.
By stracing a bit, I've created a
- IIRC on disk file size may differ if you use raidz with not optimal block sizes- do you run zdb on exported pool? Zdb may show "problems" on imported pools because they are online and change every second.- feel free to discuss it in zfsonlinux mailing list24.01.2020, 23:12, "Nick Skingle" :
Hi
10 matches
Mail list logo
