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-11060 Lustre <p>the mkfs.lustre cli is not supported under 2.11 release of lustre:</p> <p>Below is the list of components installed on the server:</p> <p> dkms status</p> <p>lustre-all, 2.11.0, 3.10.0-693.21.1.el7_lustre.x86_64, x86_64: installed</p> <p>spl, 0.7.6, 3.10.0-693.21.1.el7_lustre.x86_64, x86_64: installed</p> <p>zfs, 0.7.6, 3.10.0-693.21.1.el7_lustre.x86_64, x86_64: installed</p> <p> </p> <p>we are able to create the zfs pools:</p> <p> zpool create -f -O canmount=off -o cachefile=none mgspool mirror sdb sdc</p> <p>zpool status</p> <p>  pool: mgspool</p> <p> state: ONLINE</p> <p>  scan: none requested</p> <p>config:</p> <p> </p> <p>NAME        STATE     READ WRITE CKSUM</p> <p>mgspool     ONLINE       0     0     0</p> <p>  mirror-0  ONLINE       0     0     0</p> <p>    sdb     ONLINE       0     0     0</p> <p>    sdc     ONLINE       0     0     0</p> <p> however the mfs.lustre cli fails:</p> <p> </p> <p>mkfs.lustre --mgs --fsname=$NAME --reformat --servicenode=$MGS_NID --servicenode=$MDT_NID --mgsnode=$MGS_NID --mgsnode=$MDT_NID --backfstype=zfs mgspool/mgt</p> <p>mkfs.lustre: command not found!!</p> <p> </p> <p>Has this been deprecated or is there something missing ?</p> <p> </p> <p>thanks,</p> <p>Abe</p> <p> </p> <p> </p> <p> </p> <p> </p> LU-11060

mkfs.lustre cli command not supported in 2.11

Bug Major Resolved Done WC Triage Abe Mon, 28 May 2018 09:40:02 +0000 Wed, 8 Aug 2018 17:41:18 +0000 Wed, 8 Aug 2018 17:41:18 +0000 Lustre 2.11.0 0 2 <p>The mkfs.lustre tool is still in use and needs to be installed from the RPL. Almost certainly something is missing. This is a standard command that is still in use. </p> <p>You can try "which mkfs.lustre" to check if it is in your path, or "rpm -ql &lt;package&gt;"</p> <p>You are right Andreas,</p> <p> </p> <p>the lustre rpm was not installed although dams shows as installed:</p> <p> </p> <p>yum install lustre-2.11.0-1.el7.x86_64.rpm    </p> <p>mkfs.lustre</p> <p> modprobe lustre</p> <p> modprobe zfs</p> <p> modprobe lnet</p> <p>  lctl network up</p> <p> </p> <p>and it is working now:</p> <p>mkfs.lustre --mgs --fsname=$NAME --reformat --servicenode=$MGS_NID --servicenode=$MDT_NID --mgsnode=$MGS_NID --mgsnode=$MDT_NID --backfstype=zfs mgspool/mgt</p> <p> </p> <p>mgspool/mgt on /mnt/lustre/mgt type lustre (ro,seclabel,svname=MGS,nosvc,mgs,osd=osd-zfs)</p> <p> </p> <p>Also do you know of documentation on how to setup data on metadata feature in 2.11 release ?</p> <p> </p> <p>Thanks &amp; Best Regards,</p> <p>Abe</p> <p> </p> <p> </p> <p> </p> <p>See <a href="https://jira.hpdd.intel.com/secure/attachment/28729/DOM_user_guide.pdf" class="external-link" target="_blank" rel="nofollow noopener">https://jira.hpdd.intel.com/secure/attachment/28729/DOM_user_guide.pdf</a></p> <p>thanks Andreas for providing info this, one more question are there any default settings already for the strip size etc or does the user has to set these params before using metadata servers ?</p> <p> </p> <p>Best regards,</p> <p>Abe</p> <p>There are several levels of default values for file layouts. In order of <b>increasing</b> priority</p> <ul> <li>at the lowest level are the default values that are compiled into the code if no other values are available, namely <tt>stripe_count=1</tt> and <tt>stripe_size=1MB</tt> (which only really matters for multi-stripe files)</li> <li>there are default values that can be specified at format time with <tt>-<del>param=lov.stripesize=1M</tt> and <tt></del>-param=lov.stripecount=1</tt> (or whatever) which apply to all files unless some other layout is specified</li> <li>there may be a default layout stored on the filesystem root directory using <tt>lfs setstripe ... &lt;mountpoint&gt;</tt> (typically by the sysadmin) to allow plain (RAID-0) or composite (PFL) layouts to be specified for all new files created in the filesystem that don't have any other layout</li> <li>there may be a default layout stored on the parent directory (normally by the user) using <tt>lfs setstripe ... &lt;parent_directory&gt;</tt> that is used for all new files created in that directory, and also copied to new subdirectories created therein</li> <li>the user may specify a layout specifically for that file using <tt>lfs setstripe ... &lt;filename&gt;</tt> that is used preferentially, though it will inherit parameters from the parent/root directory or filesystem-wide defaults if some parameter is not specified (e.g. stripe size, pool, etc)</li> </ul> <p>Closing this ticket as questions have been answered.</p> Development Rank 1|hzzxvr: Rank (Obsolete) 9223372036854775807 Severity