<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:46:46 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-4893] allow unlink for dangling entry</title>
                <link>https://jira.whamcloud.com/browse/LU-4893</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;It should be possible for a regular user to delete a file or directory if the remote MDT is available but the object does not exist using normal tools like rm and rmdir. &lt;/p&gt;

&lt;p&gt;Normally, &quot;lfs rm_entry&quot; is only allowed by the root user, and this will not delete remote entries even of they exist. &lt;/p&gt;</description>
                <environment></environment>
        <key id="24190">LU-4893</key>
            <summary>allow unlink for dangling entry</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="6" iconUrl="https://jira.whamcloud.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="rhenwood">Richard Henwood</reporter>
                        <labels>
                            <label>dne</label>
                            <label>dne2</label>
                    </labels>
                <created>Sat, 12 Apr 2014 16:05:08 +0000</created>
                <updated>Tue, 12 Dec 2017 19:17:11 +0000</updated>
                            <resolved>Tue, 12 Dec 2017 19:17:11 +0000</resolved>
                                    <version>Lustre 2.6.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                            <comments>
                            <comment id="100715" author="adilger" created="Thu, 4 Dec 2014 18:43:01 +0000"  >&lt;p&gt;This isn&apos;t really specific to DNE2 (striped directories), it also applies to DNE1 (remote directories).&lt;/p&gt;</comment>
                            <comment id="126416" author="adilger" created="Fri, 4 Sep 2015 17:58:15 +0000"  >&lt;p&gt;I recall the upstream kernel folks were unhappy with our ioctl (&lt;tt&gt;LL_IOC_REMOVE_ENTRY&lt;/tt&gt;) to allow root to delete dangling entries like this.  The problem with allowing non-root users to delete dangling entries is that it isn&apos;t possible to have proper permission checks for this, since the inode&apos;s UID/GID/ACL are on the remote (unavailable) MDT, and only the local permission of the directory can be used.  For something like a striped /tmp directory with +S permissions this would allow any user to potentially disconnect a whole tree of files owned by another user.&lt;/p&gt;</comment>
                            <comment id="126682" author="adilger" created="Tue, 8 Sep 2015 17:37:20 +0000"  >&lt;p&gt;Oleg suggests to allow regular users to delete dangling subdirectories in directories that they own IFF the target MDT is online and available and reports that the directory is missing. &lt;/p&gt;</comment>
                            <comment id="212533" author="simmonsja" created="Wed, 1 Nov 2017 16:53:11 +0000"  >&lt;p&gt;In fact upstream hated it so much that LL_IOC_REMOVE_ENTRY has been deleted. Doesn&apos;t LFSCK replace this?&lt;/p&gt;</comment>
                            <comment id="212967" author="adilger" created="Tue, 7 Nov 2017 09:39:43 +0000"  >&lt;p&gt;This is needed in case some remote MDT is permanently removed, and the user/admin wants to delete the directory.  While LFSCK could potentially fix this, that might take hours/days to scan and repair the whole filesystem depending on the size. Also, LFSCK will typically not repair components of the filesystem if some server is unavailable, on the assumption that the server will be restored.  Otherwise, an ill-timed LFSCK run could clobber a large fraction of the filesystem if some OST or MDT is temporarily offline.&lt;/p&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|hzwjzb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>13529</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>