<para>For example, for a 2 stripe file, stripe size = 1M, the bad OST is at index 0, and you have holes in the file at: [(2*N + 0)*1M, (2*N + 0)*1M + 1M - 1], N = { 0, 1, 2, ...}</para>
<para>If the file system cannot be mounted, currently there is no way that parses metadata directly from an MDS. If the bad OST does not start, options to mount the file system are to provide a loop device OST in its place or replace it with a newly-formatted OST. In that case, the missing objects are created and are read as zero-filled.</para>
</section>
- <section xml:id="dbdoclet.50438198_69657">
+ <section xml:id="dbdoclet.repair_ost_lastid">
<title>Fixing a Bad LAST_ID on an OST</title>
<para>Each OST contains a LAST_ID file, which holds the last object (pre-)created by the MDS <footnote>
<para>The contents of the LAST_ID file must be accurate regarding the actual objects that exist on the OST.</para>
use</literal> error and reject to start the operation. This is caused by a portmap service
(often NFS locking) that starts before the Lustre file system and binds to the default port
988. You must have port 988 open from firewall or IP tables for incoming connections on the
- client, OSS, and MDS nodes. LNET will create three outgoing connections on available,
+ client, OSS, and MDS nodes. LNet will create three outgoing connections on available,
reserved ports to each client-server pair, starting with 1023, 1022 and 1021.</para>
<para>Unfortunately, you cannot set sunprc to avoid port 988. If you receive this error, do the following:</para>
<itemizedlist>
</listitem>
<listitem>
<para>Use a port other than 988 for the Lustre file system. This is configured in
- <literal>/etc/modprobe.d/lustre.conf</literal> as an option to the LNET module. For
+ <literal>/etc/modprobe.d/lustre.conf</literal> as an option to the LNet module. For
example:</para>
<screen>options lnet accept_port=988</screen>
</listitem>
git://git.whamcloud.com / doc / manual.git / blobdiff