<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:21:07 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-15767] If the user regain access to the encrypted directory from another client, the contents of the files will be deleted</title>
                <link>https://jira.whamcloud.com/browse/LU-15767</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;On &lt;b&gt;Client 1&lt;/b&gt;:&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
# fscrypt setup
Defaulting to policy_version 1 because kernel doesn&apos;t support v2.
Customizing passphrase hashing difficulty &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; &lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt; system...
Created global config file at &lt;span class=&quot;code-quote&quot;&gt;&quot;/etc/fscrypt.conf&quot;&lt;/span&gt;.
Metadata directories created at &lt;span class=&quot;code-quote&quot;&gt;&quot;/.fscrypt&quot;&lt;/span&gt;.
[root@trevis-90vm4 ~]# fscrypt setup /mnt/lustre
Metadata directories created at &lt;span class=&quot;code-quote&quot;&gt;&quot;/mnt/lustre/.fscrypt&quot;&lt;/span&gt;.
Change in /etc/fscrypt.conf policy_version field from 1 to 2 &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;On &lt;b&gt;Client 2&lt;/b&gt;:&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
# fscrypt setup
Defaulting to policy_version 1 because kernel doesn&apos;t support v2.
Customizing passphrase hashing difficulty &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; &lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt; system...
Created global config file at &lt;span class=&quot;code-quote&quot;&gt;&quot;/etc/fscrypt.conf&quot;&lt;/span&gt;.
Metadata directories created at &lt;span class=&quot;code-quote&quot;&gt;&quot;/.fscrypt&quot;&lt;/span&gt;.
Change in /etc/fscrypt.conf policy_version field from 1 to 2 &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;On &lt;b&gt;Client 1&lt;/b&gt;:&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
# mkdir /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;
# ls -la &#160;/mnt/lustre/
total 16
drwxr-xr-x &#160;5 root root 4096 Apr 20 12:37 .
drwxr-xr-x. 3 root root 4096 Mar &#160;1 02:01 ..
drwxr-xr-x &#160;4 root root 4096 Apr 20 08:41 .fscrypt
drwxr-xr-x &#160;2 root root 4096 Apr 20 12:37 &lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt; &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;On &lt;b&gt;Client 2&lt;/b&gt;:&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
[root@trevis-90vm5 ~]# ls -la &#160;/mnt/lustre/
total 16
drwxr-xr-x &#160;5 root root 4096 Apr 20 12:37 .
drwxr-xr-x. 3 root root 4096 Mar &#160;1 02:01 ..
drwxr-xr-x &#160;4 root root 4096 Apr 20 08:41 .fscrypt
drwxr-xr-x &#160;2 root root 4096 Apr 20 12:37 &lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt; &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;On &lt;b&gt;Client 1&lt;/b&gt;:&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
# fscrypt encrypt /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;
The following protector sources are available:
1 - Your login passphrase (pam_passphrase)
2 - A custom passphrase (custom_passphrase)
3 - A raw 256-bit key (raw_key)
Enter the source number &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; the &lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt; protector [2 - custom_passphrase]: 2
Enter a name &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; the &lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt; protector: shield
Enter custom passphrase &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; protector &lt;span class=&quot;code-quote&quot;&gt;&quot;shield&quot;&lt;/span&gt;:
Confirm passphrase:
&lt;span class=&quot;code-quote&quot;&gt;&quot;/mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;&quot;&lt;/span&gt; is now encrypted, unlocked, and ready &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; use.

# echo &lt;span class=&quot;code-quote&quot;&gt;&quot;encrypt data&quot;&lt;/span&gt; &amp;gt; /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/encrypt_file1
# echo &lt;span class=&quot;code-quote&quot;&gt;&quot;encrypt data&quot;&lt;/span&gt; &amp;gt; /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/encrypt_file2

# ls -la /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;
total 8
drwx------ 2 root root 4096 Apr 20 12:42 .
drwxr-xr-x 5 root root 4096 Apr 20 12:37 ..
-rw-r--r-- 1 root root &#160; &#160;0 Apr 20 12:42 encrypt_file1
-rw-r--r-- 1 root root &#160; &#160;0 Apr 20 12:42 encrypt_file2

# cat /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/encrypt_file1
encrypt data
# cat /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/encrypt_file2
encrypt data &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;On &lt;b&gt;Client 2&lt;/b&gt;:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
# ls -la /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/
total 8
drwx------ 2 root root 4096 Apr 20 12:42 .
drwxr-xr-x 5 root root 4096 Apr 20 12:37 ..
-rw-r--r-- 1 root root &#160; &#160;0 Apr 20 12:42 1SSaHn+b7U0XyzL82SNzjWDOS6PGKx3pAjn7WD8I1vC
-rw-r--r-- 1 root root &#160; &#160;0 Apr 20 12:42 piJmwoKUzymPjQ+53PFWANKGtXX82h0+HFPC7gFLR1B
 &#160;

# cat /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/1SSaHn+b7U0XyzL82SNzjWDOS6PGKx3pAjn7WD8I1vC
cat: /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/1SSaHn+b7U0XyzL82SNzjWDOS6PGKx3pAjn7WD8I1vC: Required key not available
# cat /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/piJmwoKUzymPjQ+53PFWANKGtXX82h0+HFPC7gFLR1B
cat: /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/piJmwoKUzymPjQ+53PFWANKGtXX82h0+HFPC7gFLR1B: Required key not available


# echo &lt;span class=&quot;code-quote&quot;&gt;&quot;&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt; data&quot;&lt;/span&gt; &amp;gt; /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/1SSaHn+b7U0XyzL82SNzjWDOS6PGKx3pAjn7WD8I1vC
-bash: /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/1SSaHn+b7U0XyzL82SNzjWDOS6PGKx3pAjn7WD8I1vC: Required key not available
# echo &lt;span class=&quot;code-quote&quot;&gt;&quot;&lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt; data&quot;&lt;/span&gt; &amp;gt; /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/piJmwoKUzymPjQ+53PFWANKGtXX82h0+HFPC7gFLR1B
-bash: /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/piJmwoKUzymPjQ+53PFWANKGtXX82h0+HFPC7gFLR1B: Required key not available


&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;On &lt;b&gt;Client 2&lt;/b&gt;:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
# fscrypt unlock /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;
Enter custom passphrase &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; protector &lt;span class=&quot;code-quote&quot;&gt;&quot;shield&quot;&lt;/span&gt;:
&lt;span class=&quot;code-quote&quot;&gt;&quot;/mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;&quot;&lt;/span&gt; is now unlocked and ready &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; use.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;After that the file size is 0&lt;/p&gt;

&lt;p&gt;On &lt;b&gt;Client 1&lt;/b&gt;:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
# ls -la /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/
total 8
drwx------ 2 root root 4096 Apr 20 12:42 .
drwxr-xr-x 6 root root 4096 Apr 20 13:00 ..
-rw-r--r-- 1 root root &#160; &#160;0 Apr 20 12:42 encrypt_file1
-rw-r--r-- 1 root root &#160; &#160;0 Apr 20 12:42 encrypt_file2

# cat /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/encrypt_file1
# cat /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/encrypt_file2&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;On &lt;b&gt;Client 2&lt;/b&gt;:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
# ls -la /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/
total 8
drwx------ 2 root root 4096 Apr 20 12:42 .
drwxr-xr-x 6 root root 4096 Apr 20 13:00 ..
-rw-r--r-- 1 root root &#160; &#160;0 Apr 20 12:42 encrypt_file1
-rw-r--r-- 1 root root &#160; &#160;0 Apr 20 12:42 encrypt_file2

# cat /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/encrypt_file1 
# cat /mnt/lustre/&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt;/encrypt_file2&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;This is the first encrypted directory on this file system.&lt;/p&gt;

&lt;p&gt;With all the following encrypted directories, the bug could not be repeated.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="69824">LU-15767</key>
            <summary>If the user regain access to the encrypted directory from another client, the contents of the files will be deleted</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="5">Cannot Reproduce</resolution>
                                        <assignee username="sebastien">Sebastien Buisson</assignee>
                                    <reporter username="okulachenko">Oleg Kulachenko</reporter>
                        <labels>
                            <label>encryption</label>
                            <label>sec</label>
                            <label>security</label>
                    </labels>
                <created>Wed, 20 Apr 2022 13:28:11 +0000</created>
                <updated>Thu, 5 May 2022 19:57:52 +0000</updated>
                            <resolved>Thu, 5 May 2022 19:57:52 +0000</resolved>
                                    <version>Lustre 2.15.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="332478" author="adilger" created="Wed, 20 Apr 2022 19:42:49 +0000"  >&lt;p&gt;There are some operations that can be done without the encryption key:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;Without the key
---------------
Some filesystem operations may be performed on encrypted regular
files, directories, and symlinks even before their encryption key has
been added, or after their encryption key has been removed:
:
- Files may be deleted.  That is, nondirectory files may be deleted
  with unlink() as usual, and empty directories may be deleted with
  rmdir() as usual.  Therefore, ``rm`` and ``rm -r`` will work as
  expected.
:
Without the key, regular files cannot be opened or truncated.
Attempts to do so will fail with ENOKEY.  This implies that any
regular file operations that require a file descriptor, such as
read(), write(), mmap(), fallocate(), and ioctl(), are also forbidden.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;So it looks like &lt;b&gt;truncating&lt;/b&gt; the file shouldn&apos;t be allowed without a key, as that might e.g. corrupt the last block, or (potentially) remove important records from the end of a file or similar.&lt;/p&gt;</comment>
                            <comment id="332799" author="sebastien" created="Mon, 25 Apr 2022 08:56:44 +0000"  >&lt;p&gt;This is weird, as truncate with or without the encryption key is exercised in sanity-sec test_48a.&lt;/p&gt;</comment>
                            <comment id="332808" author="sebastien" created="Mon, 25 Apr 2022 09:48:32 +0000"  >&lt;p&gt;Could you please specify the following:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;&lt;tt&gt;fscrypt --version&lt;/tt&gt; to get version of fscrypt command line utility being used;&lt;/li&gt;
	&lt;li&gt;distribution and kernel version on server side;&lt;/li&gt;
	&lt;li&gt;distribution and kernel version on client side;&lt;/li&gt;
	&lt;li&gt;what is the exact Lustre version being used? As 2.15.0 is not released, which tag/commit have you taken from Git?&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="332814" author="sebastien" created="Mon, 25 Apr 2022 10:05:09 +0000"  >&lt;p&gt;This step, carried out on client1, is already a problem:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;# echo &quot;encrypt data&quot; &amp;gt; /mnt/lustre/private/encrypt_file1
# echo &quot;encrypt data&quot; &amp;gt; /mnt/lustre/private/encrypt_file2

# ls -la /mnt/lustre/private
total 8
drwx------ 2 root root 4096 Apr 20 12:42 .
drwxr-xr-x 5 root root 4096 Apr 20 12:37 ..
-rw-r--r-- 1 root root    0 Apr 20 12:42 encrypt_file1
-rw-r--r-- 1 root root    0 Apr 20 12:42 encrypt_file2
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Right after you created files &lt;tt&gt;encrypt_file1&lt;/tt&gt; and &lt;tt&gt;encrypt_file2&lt;/tt&gt;, they appear with a size of 0, locally on the node where you created them. This should certainly not happen. Can you reproduce the same behavior on a regular, non-encrypted directory, as you explain making sure this is the first directory on this file system?&lt;/p&gt;</comment>
                            <comment id="332821" author="sebastien" created="Mon, 25 Apr 2022 12:29:49 +0000"  >&lt;p&gt;I tried to reproduce with servers and clients installed with CentOS 8.3 and kernel 4.18.0-240.10.1.el8_3.x86_64, and current tip of Lustre master branch (commit &quot;c6cf295d8f &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-15719&quot; title=&quot;Update changelog to properly reflect status of supported kernels for 2.15 release&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-15719&quot;&gt;&lt;del&gt;LU-15719&lt;/del&gt;&lt;/a&gt; doc: Update changelog to properly reflect supported kernels&quot;).&lt;br/&gt;
I did not manage to hit the issue reported here. Even right after creation of files &lt;tt&gt;encrypt_file1&lt;/tt&gt; and &lt;tt&gt;encrypt_file2&lt;/tt&gt;, their size is reported correctly on client1 and client2.&lt;/p&gt;</comment>
                            <comment id="333077" author="JIRAUSER17313" created="Tue, 26 Apr 2022 21:24:06 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/secure/ViewProfile.jspa?name=sebastien&quot; class=&quot;user-hover&quot; rel=&quot;sebastien&quot;&gt;sebastien&lt;/a&gt;&#160;&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;&lt;tt&gt;fscrypt --version&lt;/tt&gt; to get version of fscrypt command line utility being used;&lt;/li&gt;
&lt;/ul&gt;


&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
fscrypt --version
fscrypt version v0.2.9&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;distribution and kernel version on server side;&lt;/li&gt;
&lt;/ul&gt;


&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
4.18.0-348.2.1.el8_lustre.x86_64
CentOS Linux release 8.5.2111 &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;distribution and kernel version on client side;&lt;/li&gt;
&lt;/ul&gt;


&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
4.18.0-348.2.1.el8_lustre.x86_64
CentOS Linux release 8.5.2111&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;what is the exact Lustre version being used? As 2.15.0 is not released, which tag/commit have you taken from Git?&lt;/li&gt;
&lt;/ul&gt;


&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
lustre-release 03e4b451b0dc95fc4af2f1f48ba88b8b57ad366c Build #4283  &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="333183" author="adilger" created="Wed, 27 Apr 2022 17:47:28 +0000"  >&lt;p&gt;Is it possible that this problem is the same as &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-15787&quot; title=&quot;clients built without encryption support can corrupt encrypted directories&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-15787&quot;&gt;&lt;del&gt;LU-15787&lt;/del&gt;&lt;/a&gt;, where a client w/o encryption support is able to access the file?  This would be the case if you tested on a RHEL7.9 client, or a client built without encryption support. &lt;/p&gt;

&lt;p&gt;Oleg, if you are able to reproduce this, could you please apply the patch &lt;a href=&quot;https://review.whamcloud.com/47156&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/47156&lt;/a&gt; &quot;&lt;tt&gt;LU--15787 sec: block enc unaware clients on enc files&lt;/tt&gt;&quot; on the server to see if that fixes it. &lt;/p&gt;</comment>
                            <comment id="333212" author="JIRAUSER17313" created="Wed, 27 Apr 2022 22:06:54 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/secure/ViewProfile.jspa?name=adilger&quot; class=&quot;user-hover&quot; rel=&quot;adilger&quot;&gt;adilger&lt;/a&gt; thank you very much.&lt;/p&gt;

&lt;p&gt;I&apos;ll try to reproduce it&lt;/p&gt;</comment>
                            <comment id="333958" author="pjones" created="Thu, 5 May 2022 19:57:52 +0000"  >&lt;p&gt;Could not be reproduced, perhaps addressed by &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-15787&quot; title=&quot;clients built without encryption support can corrupt encrypted directories&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-15787&quot;&gt;&lt;del&gt;LU-15787&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="70019">LU-15787</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i02nin:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>