https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-9730 Lustre <p>If interrupted or upon failure, obdfilter-survey can leave OST objects allocated, unconnected and consuming space.</p> <p>A first and simple fix will be to add an exit trap to the script in order to ensure that the previously created objects during the current run will be deleted.</p> <p>Alternatively, a post-failure cleanup way/tool is also required to allow later/async deletion of these same kind of orphan objects.</p> LU-9730

cleanup OST objects that have been leaked during interrupted/failed runs of obdfilter-survey

Bug Minor Open Unresolved Bruno Faccini Bruno Faccini Sun, 2 Jul 2017 22:41:36 +0000 Wed, 15 Feb 2023 21:25:02 +0000 0 6 <p>Faccini Bruno (bruno.faccini@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/28113" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/28113</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-9730" title="cleanup OST objects that have been leaked during interrupted/failed runs of obdfilter-survey" class="issue-link" data-issue-key="LU-9730">LU-9730</a> tests: obdfilter-survey cleanup upon exit/signal<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 0b44735657983451407f9bbd90891b6c054bde6d</p> <p>About the async post-failure cleanup process, as the orphan objects end up as unattached inodes with i_nlink == 1, for ldiskfs back-end case, an e2fsck run would be very helpful to identify all all concerned inodes, among some others if Lustre FS and OST are currently in-use/mounted, and this at least using the -n option. <br/> But then there is the need to access their LMA xattr content, in order to verify if they are of the FID_SEQ_ECHO sequence and thus use their object-id to request their destruction.<br/> Or may be some of the OI code could be used/modified in order to permit inode/object-id mapping, or why not to implement a method to parse OI in order to retrieve all known/registered FID_SEQ_ECHO/object-id from it and thus be able to destroy all of them.</p> <p>For ZFS back-end, looks like ZAP features usage will be required.</p> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=nangelinas" class="user-hover" rel="nangelinas">nangelinas</a>, I know you were working on this recently.  Did you end up finishing something?</p> Duplicate Related Development Rank 1|hzzfz3: Rank (Obsolete) 9223372036854775807 Severity