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-3445 Lustre <p>With older version of Lustre I was used to have IB as default network, but also to have a ethernet connection as fallback, so each NID specified for failover.node or mgs.node contained both networks, e.g.:</p> <p>failover.node=10.3.0.228@o2ib,192.168.50.128@tcp</p> <p>When I try this with 2.4.0 it appears the parser does not understand this syntax anymore. I get an error in syslog:</p> <p>LDISKFS-fs (dm-7): Unrecognized mount option "192.168.50.128@tcp" or missing value</p> LU-3445

Specifying multiple networks in NIDs does no longer work

Bug Major Resolved Fixed Jian Yu Oliver Mangold Fri, 7 Jun 2013 13:40:24 +0000 Thu, 9 Jan 2014 13:39:15 +0000 Tue, 20 Aug 2013 05:59:59 +0000 Lustre 2.4.0 Lustre 2.4.1 Lustre 2.5.0 0 11 <p>Yu, Jian</p> <p>Could you please look into this issue?</p> <p>Thanks</p> <p>Peter</p> <p>A simple test showed that:</p> <div class="panel" style="border-width: 1px;"><div class="panelContent"> <p><b>&#35; tunefs.lustre --dryrun /dev/vda5</b><br/> checking for existing Lustre data: found<br/> Reading CONFIGS/mountdata</p> <p> Read previous values:<br/> Target: lustre-OST0000<br/> Index: 0<br/> Lustre FS: lustre<br/> Mount type: ldiskfs<br/> Flags: 0x62<br/> (OST first_time update )<br/> Persistent mount opts: errors=remount-ro<br/> Parameters: sys.timeout=20 mgsnode=10.3.0.228@o2ib,192.168.50.128@tcp</p> <p> Permanent disk data:<br/> Target: lustre:OST0000<br/> Index: 0<br/> Lustre FS: lustre<br/> Mount type: ldiskfs<br/> Flags: 0x62<br/> (OST first_time update )<br/> Persistent mount opts: errors=remount-ro<br/> Parameters: sys.timeout=20 mgsnode=10.3.0.228@o2ib,192.168.50.128@tcp</p> <p>exiting before disk write.</p> <p><b>&#35; mount -v -t lustre /dev/vda5 /mnt/ost1</b><br/> arg<span class="error">&#91;0&#93;</span> = /sbin/mount.lustre<br/> arg<span class="error">&#91;1&#93;</span> = -v<br/> arg<span class="error">&#91;2&#93;</span> = -o<br/> arg<span class="error">&#91;3&#93;</span> = rw<br/> arg<span class="error">&#91;4&#93;</span> = /dev/vda5<br/> arg<span class="error">&#91;5&#93;</span> = /mnt/ost1<br/> source = /dev/vda5 (/dev/vda5), target = /mnt/ost1<br/> options = rw<br/> checking for existing Lustre data: found<br/> Reading CONFIGS/mountdata<br/> Writing CONFIGS/mountdata<br/> mounting device /dev/vda5 at /mnt/ost1, flags=0x1000000 <font color="red">options=osd=osd-ldiskfs,errors=remount-ro,mgsnode=10.3.0.228@o2ib,192.168.50.128@tcp,virgin,update,param=sys.timeout=20,param=mgsnode=10.3.0.228@o2ib,192.168.50.128@tcp,svname=lustre-OST0000,device=/dev/vda5</font><br/> mount.lustre: mount /dev/vda5 at /mnt/ost1 failed: Invalid argument retries left: 0<br/> mount.lustre: mount /dev/vda5 at /mnt/ost1 failed: Invalid argument<br/> This may have multiple causes.<br/> Are the mount options correct?<br/> Check the syslog for more info.</p> </div></div> <p>I'm creating a patch to fix add_param() to add "key" before each "sub-val" separated by comma in "val".</p> <p>Patch for Lustre master branch: <a href="http://review.whamcloud.com/6686" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/6686</a></p> <p>Hi Oleg,</p> <p>Could you please cherry-pick the patch to Lustre b2_4 branch? Thanks.</p> <p>this patch cannot be cherrypicked to b2_4 due to a conflict</p> <p>back port to b2_4: <a href="http://review.whamcloud.com/7344" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7344</a></p> <p>Landed for 2.4.1 and 2.5</p> <p>It seems to me this bug is still there for 2 reasons:</p> <p>-the patch only take care of mkfs/tunefs and so there is still an upgrade issue if mountdata contains something like <tt>failover.node=10.3.0.228@o2ib,192.168.50.128@tcp</tt><br/> The way to workaround this looks to be a writeconf, which has side effect. Is there some UPGRADE notes somewhere relative to this?</p> <p>-the patch seems to modify this kind of string</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>--failnode=10.3.0.228@o2ib,192.168.50.128@tcp </pre> </div></div> <p>into</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>--failnode=10.3.0.228@o2ib --failnode=10.3.0.228@o2ib </pre> </div></div> <p>Which is not the same. The first example refers to 1 failnode, with 2 NIDS to reach it. The second one refers to 2 different failnodes with 1 NID each.</p> <p>Thanks Aurelien for pointing this out. I'll look into these issues and figure out whether I should fix the original issue in lmd_parse(). I'll create a new Jira ticket to track the work.</p> <p>Thanks Jian. For my own tracking I've just created the ticket: <a href="https://jira.whamcloud.com/browse/LU-4460" title="Using multiple NIDs for the same failnode or mgsnode is STILL broken for Lustre 2.4" class="issue-link" data-issue-key="LU-4460"><del>LU-4460</del></a>.</p> Duplicate LU-3830 Development Rank 1|hzvsx3: Rank (Obsolete) 8593 Severity