<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:12:12 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-14720] OSD should store filenames for system files in xattrs</title>
                <link>https://jira.whamcloud.com/browse/LU-14720</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;For recovery purposes, it would be great to store the filename for all internal system files in xattrs on each inode. This would make OI Scrub able to recover these files easily if the root directory was corrupted and some/all files end up in &lt;tt&gt;lost+found&lt;/tt&gt;.  While OI Scrub can repair some of the layout already (e.g. move objects from &lt;tt&gt;lost+found&lt;/tt&gt; back into an object directory &lt;tt&gt;O/SEQ/dN/OID&lt;/tt&gt;), it would be much better to just move the &quot;&lt;tt&gt;O/&lt;/tt&gt;&quot; or &quot;&lt;tt&gt;SEQ&lt;/tt&gt;&quot; or &quot;&lt;tt&gt;dN&lt;/tt&gt;&quot; directory as a whole back to the proper location instead of moving millions of objects separately.&lt;/p&gt;

&lt;p&gt;Similarly, recovering &lt;tt&gt;CONFIGS&lt;/tt&gt;, &lt;tt&gt;mountdata&lt;/tt&gt;, and &lt;tt&gt;last_rcvd&lt;/tt&gt; avoid the need for support personnel to get involved to recover this manually before the filesystem can even be mounted by Lustre.&lt;/p&gt;

&lt;p&gt;Since the &lt;tt&gt;mount.lustre&lt;/tt&gt; checks that the &lt;tt&gt;mountdata&lt;/tt&gt; and &lt;tt&gt;last_rcvd&lt;/tt&gt; files (in &lt;tt&gt;ldiskfs_is_lustre()&lt;/tt&gt;) before even &lt;b&gt;trying&lt;/b&gt; to mount the filesystem, this would need to be relaxed, and also allow mounting the filesystem if there are files in &lt;tt&gt;lost+found&lt;/tt&gt; that have &lt;tt&gt;trusted.lov&lt;/tt&gt; and &lt;tt&gt;trusted.lma&lt;/tt&gt; xattrs on them (and whatever else we do to identify internal system files).  Then, OI Scrub should try to identify critical files/directories in &lt;tt&gt;lost+found&lt;/tt&gt; first, before trying to mount the filesystem.  If the recovery of files from &lt;tt&gt;lost+found&lt;/tt&gt; is unsuccessful, and the &lt;tt&gt;mountdata&lt;/tt&gt; file cannot be recovered, the  mount should fail with a error as it does today.&lt;/p&gt;</description>
                <environment></environment>
        <key id="64447">LU-14720</key>
            <summary>OSD should store filenames for system files in xattrs</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</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="wc-triage">WC Triage</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                    </labels>
                <created>Sat, 29 May 2021 00:01:37 +0000</created>
                <updated>Wed, 10 May 2023 23:43:50 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="303060" author="adilger" created="Sat, 29 May 2021 00:19:02 +0000"  >&lt;p&gt;We might consider using &quot;&lt;tt&gt;trusted.link&lt;/tt&gt;&quot;, but that may be confused with regular user files. Possibly use the same format, but with a different xattr name. &lt;/p&gt;

&lt;p&gt;For files/directories in the filesystem root (eg. &quot;&lt;tt&gt;O/&lt;/tt&gt;&quot;, &quot;&lt;tt&gt;CATALOGS&lt;/tt&gt;&quot;, etc) can also have a parent IGIF FID of &lt;tt&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;0x00000002:0x0:0x0&amp;#93;&lt;/span&gt;&lt;/tt&gt; for the ext2 root inode. &lt;/p&gt;

&lt;p&gt;We have lots of space in these internal inodes, so storing a couple of xattrs is fine, and Scrub should be able to rebuild the whole structure easily. &lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </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|i01vnj:</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>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>