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-2068 Lustre <p>I run into build issues with the "lvfs" directory and the "osd-ldiskfs" directory if I configure the tree using the "--without-ldiskfs" option.</p> Lustre Tree: 2.3.51-7-g1d7fa63<br/> OS: CHAOS 5 (RHEL 6.2) LU-2068

configure option "--without-ldiskfs" does not build.

Bug Major Resolved Fixed Minh Diep Prakash Surya Mon, 1 Oct 2012 16:46:04 +0000 Fri, 19 Apr 2013 14:48:06 +0000 Mon, 8 Oct 2012 01:23:29 +0000 Lustre 2.4.0 Lustre 2.4.0 0 7 <p>To start, it looks like my patches from <a href="https://jira.whamcloud.com/browse/LU-2158" title="remove lvfs and fsfilt code" class="issue-link" data-issue-key="LU-2158"><del>ORI-257</del></a> were dropped. I'm going to try and resurrect those on master.</p> <p>Pushed an initial patch to remedy this here: <a href="http://review.whamcloud.com/4148" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4148</a></p> <p>thanks for the patch. I've slightly modified it so that:</p> <p>1) utilities (mkfs/mount) do not try to call ldiskfs helpers<br/> 2) enable ldiskfs by default (sorry, there are number of people and systems depending on this behavior)<br/> 3) the code depending on lvfs/ldiskfs shouldn't build unless ldiskfs support is configured: obdfilter, llog_lvfs, backup in mgc</p> <p>Would you mind if I add in the top autoMakefile.am fix for the META for ldisk?</p> <p>not at all. thanks!</p> <p>Last patch is pretty broken. Is mds and cmm used only for ldisk non-osd mode? I included them back in for server build or should they be only ldiskfs?</p> <p>no, neither mds nor cmm are used with any backend.</p> <p>i'm uploading a new version just to see how the build system like it..</p> <p>Trying it as well.</p> <p>James, there is a small defect still in the code (preventing few conf-sanity tests), I'll upload fixed version shortly.</p> <p>Client build seems to be having a issue as well.</p> <p>fixing..</p> <p>Found the last build bug on client. Will be pushing a patch soon.</p> <p>I'll have to update the patch after that. thanks in advance.</p> <p>Just submitted. All yours now.</p> <p>Almost. Only the ZFS build now fails. What is missing is:</p> <p>diff --git a/lustre/obdfilter/autoMakefile.am b/lustre/obdfilter/autoMakefile.am<br/> index 171bc30..3896641 100644<br/> &#8212; a/lustre/obdfilter/autoMakefile.am<br/> +++ b/lustre/obdfilter/autoMakefile.am<br/> @@ -35,7 +35,9 @@<br/> #</p> <p> if MODULES<br/> +if LDISKFS_ENABLED<br/> modulefs_DATA = obdfilter$(KMODEXT)<br/> endif<br/> +endif</p> <p> MOSTLYCLEANFILES := @MOSTLYCLEANFILES@ </p> <p>Could you explain why ZFS needs that? As of 2.3.51 we are building lustre --without-ldiskfs and --with-zfs and did not see a build problem.</p> <p>In any event, the obdfilter code will be deleted in about a week, as I understand it, so I don't much care either way.</p> <p>The last patch for this ticket was trying to build obdfilter for zfs which is not needed.</p> <p>Chris, this is not just obdfilter - it's llog-lvfs code which I'd like to avoid from the builds with no ldiskfs support.<br/> In orion it's easier because llog-lvfs itself was removed, we can't do this now on master. and this is one of examples<br/> why we can't just land orion on master (as we'd like to do as well).</p> <p>You need to get me an explanation of why we can't do this now, and exactly when it will be landed.</p> <p>Chris, if you'd prefer to land the minimal patch now, I'm fine with patchset #2 (+ ldiskfs enabled by default).</p> <p>Patchset 2 + ldiskfs enabled would be great, yes.</p> <p>I just uploaded that. </p> <p>Alex, James, please see: <a href="http://review.whamcloud.com/4159" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4159</a>.</p> <p>sure, thanks.</p> <p>Both patches 4159 and 4148 landed to master.</p> Development Rank 1|hzv4uf: Rank (Obsolete) 4318 Severity