Whamcloud Community JIRA

Whamcloud Community JIRA https://jira.whamcloud.com This file is an XML representation of an issue en-us

9.4.14

940014

05-12-2023

[LU-591] 1.8->2.0 Lustre filesystem upgrade tool https://jira.whamcloud.com/browse/LU-591 Lustre LU-591

1.8->2.0 Lustre filesystem upgrade tool

New Feature Minor Resolved Fixed nasf Vitaly Fertman Fri, 12 Aug 2011 15:40:02 +0000 Tue, 9 Apr 2013 08:28:30 +0000 Tue, 9 Apr 2013 08:28:30 +0000 Lustre 2.1.0 Lustre 2.4.0 0 8 remote: <a href="http://review.whamcloud.com/1230" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/1230</a> remote: <a href="http://review.whamcloud.com/1231" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/1231</a> remote: <a href="http://review.whamcloud.com/1232" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/1232</a> the code is not 100% ready, it is still under testing. I'm generally not in favour of the last patch (<a href="http://review.whamcloud.com/1232" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/1232</a>, automatically enabling the INCOMPAT_DIR_DATA feature at first mount) since this can cause interoperability issues, and may cause problems for downgrade to 1.8 if there are problems in that code. In upstream ext4 none of the new features are enabled automatically by the kernel, but rather depend on explicit user action (tune2fs). In this case, it makes sense that the enabling of this feature should be done either by tune2fs or some other explicit action that runs the filesystem upgrade tool. As for the "compatible with 1 version", we are working to maintain protocol compatibility with 1.8.x clients and upgrade from 1.8.x -> 2.1, because almost nobody is running 2.0.0. I checked and it appears that there is "data_in_dirent" support going back to 1.8.2 (<a href="https://bugzilla.lustre.org/show_bug.cgi?id=21188" class="external-link" target="_blank" rel="nofollow noopener">https://bugzilla.lustre.org/show_bug.cgi?id=21188</a> was also fixed in 1.8.2 after the initial patch landing), so this should be OK but I'd like feedback from Johann and Oleg as well. HLD code is rebased against b2_1 and moved to: <a href="http://review.whamcloud.com/#change,1561" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,1561</a> <a href="http://review.whamcloud.com/#change,1562" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,1562</a> <a href="http://review.whamcloud.com/#change,1563" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,1563</a> 1230 seem to be introduced a bug: <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> rc = mdo_xattr_get(env, mdd_obj, ldata->ml_buf, XATTR_NAME_LINK, capa); if (rc == -ERANGE) { /* Buf was too small, figure out what we need. */ mdd_buf_put(ldata->ml_buf); rc = mdo_xattr_get(env, mdd_obj, ldata->ml_buf, XATTR_NAME_LINK, capa); </pre> </div></div> in the latter <tt>mdo_xattr_get()</tt>, <tt>&LU_BUF_NULL</tt> should be used instead of <tt>ldata->ml_buf</tt>. Currently it will return same -ERANGE, not actual size of the EA. In light of the changes to lfsck in phase 1.5(<a href="https://jira.hpdd.intel.com/browse/LU-1866" class="external-link" target="_blank" rel="nofollow noopener">https://jira.hpdd.intel.com/browse/LU-1866</a>), is this tool still needed? If so, what does it do that the new lfsck does not? Thanks. Patrick, this code and the LFSCK 1.5 code are largely overlapping. The main differences are: <ul class="alternate" type="square"> <li>this code changed all of the inode FIDs, which would cause problems with NFS exports and some backup tools</li> <li>LFSCK 1.5 keeps the 1.8 IGIF FIDs and treats them as normal 2.x FIDs, even after backup/restore</li> <li>this code must be run without mounted clients, due to above</li> <li>LFSCK 1.5 can be run while the filesystem is mounted and in use</li> </ul> Related LU-1866 Development Rank 1|hzvn13: Rank (Obsolete) 7537