On Jan 9, 2019, at 07:52, Daniel Kobras wrote:
>
> Hi Aurélien!
>
> Am 09.01.19 um 14:30 schrieb Degremont, Aurelien:
>> The secondary group thing was ok to me. I got this idea even if there is
>> some weird results during my tests. Looks like you can overwrite MDT checks
>> if user and group
Is Lustre 2.12 considered to be suitable for production or is that a
development version?
Andrew Tauferner
1-952-562-4944 (office)
1-507-696-4609 (mobile)
-Original Message-
From: Degremont, Aurelien [mailto:degre...@amazon.com]
Sent: Wednesday, January 9, 2019 11:49 AM
To: Tauferner,
Interesting that I can successfully build a 4.14 kernel and run the Lustre
client using the modules that came from that kernel. The Lustre code in the
kernel tree appears to be really old (2.7?).
Andrew Tauferner
1-952-562-4944 (office)
1-507-696-4609 (mobile)
-Original Message-
2.10.6 does not support Linux 4.14.
There is several patches that needs to be cherry picked to have it working.
2.12 is fine though.
Aurélien
Le 09/01/2019 18:43, « lustre-discuss au nom de Tauferner, Andrew T »
a écrit :
I configured like so:
I configured like so:
attaufer@head-2:~/lustre-release> ./configure --disable-server
--with-linux=/nfshome/attaufer/kernel/usr/src/kernels/4.14.54-mos-tc3-20181113
The make failed as follows:
attaufer@head-2:~/lustre-release> make rpms
make dist-gzip am__post_remove_distdir='@:'
make[1]:
Hi Aurélien!
Am 09.01.19 um 14:30 schrieb Degremont, Aurelien:
> The secondary group thing was ok to me. I got this idea even if there is some
> weird results during my tests. Looks like you can overwrite MDT checks if
> user and group is properly defined on client node. Cache effects?
In a
Hi Daniel!
The secondary group thing was ok to me. I got this idea even if there is some
weird results during my tests. Looks like you can overwrite MDT checks if user
and group is properly defined on client node. Cache effects?
ACL is really the thing I was interested in. Who is validating
Hi ANS,
About the soft limits and not receiving any warning or notification when the
soft quota is reached, this would be the expected behavior. The soft quota is
used together with the grace period to give some “extra” time to the user to
remove inodes/blocks, as per the Lustre Operations
Hi Aurélien!
Am 09.01.19 um 11:48 schrieb Degremont, Aurelien:
> When disabling identity_upcall on a MDT, you get this message in system
> logs:
>
> lustre-MDT: disable "identity_upcall" with ACL enabled maybe cause
> unexpected "EACCESS"
>
> I’m trying to understand what could be a
Hello all,
When disabling identity_upcall on a MDT, you get this message in system logs:
lustre-MDT: disable "identity_upcall" with ACL enabled maybe cause
unexpected "EACCESS"
I’m trying to understand what could be a scenario that shows this problem?
What is the implication, or rather,
Dear All,
Can anyone look into it.
Thanks,
ANS
On Mon, Jan 7, 2019 at 6:38 PM ANS wrote:
> Dear All,
>
> I am trying to set quota on lustre but unfortunately i have issued the
> below commands:-
>
> tunefs.lustre --param ost.quota_type=ug /dev/mapper/mds1
> checking for existing Lustre data:
11 matches
Mail list logo
