<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:28:09 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-16569] chattr makes file unavailable </title>
                <link>https://jira.whamcloud.com/browse/LU-16569</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Here is the problem, Lustre does not filter supported attributes and as a result file became unaccessible.&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;$touch /mnt/lustre/f2
$lsattr /mnt/lustre/f2
---------------------- /mnt/lustre/f2
$chattr +aAcCdDeFijmPsStTux /mnt/lustre/f2
$lsattr /mnt/lustre/f2
lsattr: No data available While reading flags on /mnt/lustre/f2
$cat /mnt/lustre/f2
cat: /mnt/lustre/f2: No data available
$statx /mnt/lustre/f2
  File: /mnt/lustre/f2
  Size: 0         	Blocks: 0          IO Block: 4194304 regular empty file
Device: 2c54f966h/743766374d	Inode: 144115205272502274  Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Context: unconfined_u:object_r:unlabeled_t:s0
Access: 2023-02-16 18:08:06.000000000 -0500
Modify: 2023-02-16 18:08:06.000000000 -0500
Change: 2023-02-16 18:08:06.000000000 -0500
 Birth: 2023-02-16 18:08:06.000000000 -0500
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="74725">LU-16569</key>
            <summary>chattr makes file unavailable </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="1" iconUrl="https://jira.whamcloud.com/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="sebastien">Sebastien Buisson</assignee>
                                    <reporter username="aboyko">Alexander Boyko</reporter>
                        <labels>
                    </labels>
                <created>Fri, 17 Feb 2023 11:15:40 +0000</created>
                <updated>Mon, 20 Feb 2023 13:41:54 +0000</updated>
                                            <version>Lustre 2.16.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="363357" author="adilger" created="Sat, 18 Feb 2023 01:47:46 +0000"  >&lt;p&gt;This definitely looks like it could screw up encrypted files:&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;# for F in a A c C d D e F i j m P s S t T u x; do
     touch /mnt/testfs/dir_attr/f-$F
     chattr +$F /mnt/testfs/dir_attr/f-$F
done

# ls -l /mnt/testfs/dir_attr
total 0
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-a
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-A
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-c
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-C
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-d
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-D
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-e
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-F
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-i
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-j
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-m
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-P
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-s
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-S
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-t
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-T
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-u
0 -rw-r--r--. 1 root 0 Feb 17 18:40 f-x

# lsattr /mnt/testfs/dir_attr
---------------------- /mnt/testfs/dir_attr/f-F
---------------------- /mnt/testfs/dir_attr/f-c
---------------------- /mnt/testfs/dir_attr/f-d
---------------------- /mnt/testfs/dir_attr/f-D
---------------------- /mnt/testfs/dir_attr/f-m
-------A-------------- /mnt/testfs/dir_attr/f-A
lsattr: Required key not available While reading flags on /mnt/testfs/dir_attr/f-C
---------------------- /mnt/testfs/dir_attr/f-s
--S------------------- /mnt/testfs/dir_attr/f-S
---------------------- /mnt/testfs/dir_attr/f-T
---------------------- /mnt/testfs/dir_attr/f-x
---------------------- /mnt/testfs/dir_attr/f-u
-------------------P-- /mnt/testfs/dir_attr/f-P
-----a---------------- /mnt/testfs/dir_attr/f-a
----i----------------- /mnt/testfs/dir_attr/f-i
---------------------- /mnt/testfs/dir_attr/f-t
---------------------- /mnt/testfs/dir_attr/f-e
---------------------- /mnt/testfs/dir_attr/f-j
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;While I&apos;m not sure the &lt;b&gt;clients&lt;/b&gt; should filter the flags (since they may not know which ones the servers support), definitely the MDS should filter the unknown/unsupported flags (or whitelist only known flags).  I &lt;em&gt;think&lt;/em&gt; there is a flag whitelist in newer ext4 code, not sure what version that appeared in, but we might also bypass those checks in osd-ldiskfs.&lt;/p&gt;</comment>
                            <comment id="363457" author="sebastien" created="Mon, 20 Feb 2023 13:41:54 +0000"  >&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;lsattr: Required key not available While reading flags on /mnt/testfs/dir_attr/f-C
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I am not even sure why it complains about a &apos;key&apos; on the file &lt;tt&gt;f-C&lt;/tt&gt;, as it just has a COW-related flag:&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;C      A file with the &apos;C&apos; attribute set will not be subject to
              copy-on-write updates.  This flag is only supported on
              file systems which perform copy-on-write.  (Note: For
              btrfs, the &apos;C&apos; flag should be set on new or empty files.
              If it is set on a file which already has data blocks, it
              is undefined when the blocks assigned to the file will be
              fully stable.  If the &apos;C&apos; flag is set on a directory, it
              will have no effect on the directory, but new files
              created in that directory will have the No_COW attribute
              set. If the &apos;C&apos; flag is set, then the &apos;c&apos; flag cannot be
              set.)
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                    </comments>
                    <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|i03ee7:</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>