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

[LUDOC-87] OSD-Mount Doc Changes https://jira.whamcloud.com/browse/LUDOC-87 Lustre Documentation <p>Changes to format and mount options</p> LUDOC-87

OSD-Mount Doc Changes

Improvement Critical Resolved Fixed Alex Zhuravlev Jodi Levi Wed, 12 Sep 2012 18:00:15 +0000 Wed, 16 Sep 2015 12:23:52 +0000 Wed, 16 Sep 2015 12:23:52 +0000 0 3 <p>Update the user manual to describe changes to the user tools:</p> <ul class="alternate" type="square"> <li>formatting, mounting, usage, configuration, etc.</li> <li>potentially some of the example output (if relevant to the examples)</li> <li>/proc tunables, module parameters, etc.</li> </ul> <p>Since we use a single manual for all of the Lustre releases, when changing any significant sections of text the content should include the version in which the change was made (i.e. 2.4) and leave the old comments in place (at least back to 2.1, older 1.x sections can be removed), for example:</p> <blockquote> <p>Up to Lustre 2.3 running writeconf was via <tt>tunefs.lustre --writeconf /dev/mdtdev</tt>. Starting with Lustre 2.4 running writeconf should be use ...</p></blockquote> <p>I've gone through the manual and got the following TODO:</p> <p>13.14.�Identifying To Which Lustre File an OST Object Belongs – check</p> <p>14.2.� Finding Nodes in the Lustre File System</p> <p>cat /proc/fs/lustre/lov/lustre-mdtlov/target_obd – lustre-MDTXXXX-mdtlov</p> <p>14.8.5.� Restoring OST Configuration Files – check</p> <p>14.12.� Separate a combined MGS/MDT – check</p> <p>17.1.1.1.�Using Lustre_rsync – check</p> <p>24.3.1.�Testing Local Disk Performance – load ofd module since 2.4</p> <p>24.3.4.2.�Visualizing Results - brw_stats in /proc/.../osd-*/brw_stats</p> <p>30.1.4.�OST Failure (Failover) - s/LOV/LOD/</p> <p>31.1.5.�Free Space Distribution – lustre-MDTXXXX-mdtlov</p> <p>31.2.6.�Watching the OST Block I/O Stream – in OSD now</p> <p>31.2.8.1.�Using OSS Read Cache - in OSD now</p> <p>36.14.3.�Examples – should we specify MDT index always?</p> <p>36.15.3.�Options – check md_stripe_cache_size still works</p> <p>36.18.3.�Options – check --mountfsoptions=opts</p> <ul> <li> <ul> <li>describe LOV->LOD, OSC->OSP change on MDS ?</li> <li>new parameters in LOD (under /proc/fs/lustre/osc/fsname-OST*-osc-MDT*/:<br/> sync_changes, sync_in_flight, sync_in_progress</li> <li>ZFS support</li> </ul> </li> </ul> <p>any comments?</p> <p>– 13.14.�Identifying To Which Lustre File an OST Object Belongs – check<br/> probably we need to mention "0" in /O/0/d$((34976 % 32))/34976" is a sequence number and with DNE it won't be 0, instead it should be taken properly from lfs getstripe output</p> <p>– 14.2.� Finding Nodes in the Lustre File System</p> <p>cat /proc/fs/lustre/lov/fsname-mdtlov/target_obd - s/fsname-mdtlov/fsname-MDT<index>-mdtlov/target_obd</p> <p>– 14.8.5.� Restoring OST Configuration Files</p> <p>should be OK</p> <p>– 14.12.� Separate a combined MGS/MDT – check</p> <p>should be OK</p> <p>– 17.1.1.1.�Using Lustre_rsync – check</p> <p>should be OK</p> <p>– 24.3.1</p> <p>starting from 2.4 we load ofd.ko instead of obdfilter.ko</p> <p>24.3.4.2.�Visualizing Results</p> <p>since 2.4 brw_stats should be checked in /proc/.../osd-*/brw_stats</p> <p>30.1.4.�OST Failure (Failover) - s/LOV/LOD/</p> <p>since 2.4 MDS uses LOD instead of LOV</p> <p>31.1.5.�Free Space Distribution</p> <p>cat /proc/fs/lustre/lov/fsname-mdtlov/qos_prio_free – it's actually /.../fsname-MDTXXXX-mdtlov/ since some previous version</p> <p>31.2.6.�Watching the OST Block I/O Stream – in OSD now</p> <p>oss# lctl get_param obdfilter.testfs-OST0000.brw_stats - osd-*.testfs-OST0000.brwstats since 2.4</p> <p>31.2.8.1.�Using OSS Read Cache</p> <p>lctl set_param osd-ldiskfs.<b>.read_cache_enable=0 – osd-</b>.*.read_cache_enable since 2.4, doesn't apply to osd-zfs</p> <p>36.18.3.�Options</p> <p>--mountfsoptions=opts should be OK</p> <p>with the latest changes to master branch, we can keep using obdfilter.* to access brw_stats. we should handle read_cache_enable similarly.</p> <p><a href="http://review.whamcloud.com/5873" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5873</a> – with the patch read_cache_enable, readcache_max_filesize and writethrough_cache_enable can be accessed via obdfilter.*, so we wouldn't need to change the manual.</p> <p>compatibility bits are landed</p> Related LU-1711 Development Project Rank 1|hzvksn: Rank (Obsolete) 7130