<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:48:45 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-5127] Running mke2fs to get alternate superblocks on &gt;16TB LUN</title>
                <link>https://jira.whamcloud.com/browse/LU-5127</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;We have an OST that is not mountable because a superblock is unreadable from the backend storage. In order to begin repairs, we need to run mke2fs to get the alternate superblocks to then run debugfs. Unfortunately, the current version of e2fsprogs does not handle this by default. Can you advise the correct options to use with mke2fs with -n (very important!). If we run with -O64bit without any other of the original filesystem options, will that do it?&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@f1-oss1d5 share&amp;#93;&lt;/span&gt;# /tmp/e2fsprogs-new/sbin/mke2fs -n /dev/mapper/f1-ddn1d-l30&lt;br/&gt;
mke2fs 1.42.9.wc1 (24-Feb-2014)&lt;br/&gt;
mke2fs: Size of device (0x151e00000 blocks) /dev/mapper/f1-ddn1d-l30 too big to be expressed&lt;br/&gt;
       in 32 bits using a blocksize of 4096.&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@f1-oss1d5 man8&amp;#93;&lt;/span&gt;# dumpe2fs /dev/mapper/f1-ddn1d-l30 | grep superblock&lt;br/&gt;
dumpe2fs 1.42.7.wc2 (07-Nov-2013)&lt;br/&gt;
dumpe2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/mapper/f1-ddn1d-l30&lt;br/&gt;
Couldn&apos;t find valid filesystem superblock.&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;root@f1-oss1d5 man8&amp;#93;&lt;/span&gt;# &lt;/p&gt;</description>
                <environment>RHEL 6.4&lt;br/&gt;
e2fsprogs 1.42.9.wc1 </environment>
        <key id="24980">LU-5127</key>
            <summary>Running mke2fs to get alternate superblocks on &gt;16TB LUN</summary>
                <type id="9" iconUrl="https://jira.whamcloud.com/images/icons/issuetypes/undefined.png">Question/Request</type>
                                            <priority id="2" iconUrl="https://jira.whamcloud.com/images/icons/priorities/critical.svg">Critical</priority>
                        <status id="6" iconUrl="https://jira.whamcloud.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="yujian">Jian Yu</assignee>
                                    <reporter username="blakecaldwell">Blake Caldwell</reporter>
                        <labels>
                    </labels>
                <created>Sat, 31 May 2014 17:06:49 +0000</created>
                <updated>Tue, 3 Jun 2014 15:01:38 +0000</updated>
                            <resolved>Tue, 3 Jun 2014 15:00:48 +0000</resolved>
                                    <version>Lustre 2.4.1</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="85399" author="pjones" created="Sat, 31 May 2014 19:40:58 +0000"  >&lt;p&gt;Yu, Jian&lt;/p&gt;

&lt;p&gt;Could you please advise here?&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="85406" author="blakecaldwell" created="Sun, 1 Jun 2014 05:29:15 +0000"  >&lt;p&gt;Hello,&lt;/p&gt;

&lt;p&gt;We were able to resolve this issue. The -t ext4 option was critical to get mke2fs to assume the 64bit feature. Here are the full commands that we used.&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@f1-oss1d1 ~&amp;#93;&lt;/span&gt;# mke2fs -n -t ext4 -O has_journal,ext_attr,resize_inode,dir_index,filetype,extent,64bit,mmp,flex_bg,sparse_super,large_file,huge_file,uninit_bg,dir_nlink,quota /dev/mapper/f1-ddn1d-l30&lt;br/&gt;
mke2fs 1.42.7.wc2 (07-Nov-2013)&lt;br/&gt;
Filesystem label=&lt;br/&gt;
OS type: Linux&lt;br/&gt;
Block size=4096 (log=2)&lt;br/&gt;
Fragment size=4096 (log=2)&lt;br/&gt;
Stride=256 blocks, Stripe width=256 blocks&lt;br/&gt;
354287616 inodes, 5668601856 blocks&lt;br/&gt;
283430092 blocks (5.00%) reserved for the super user&lt;br/&gt;
First data block=0&lt;br/&gt;
Maximum filesystem blocks=7816085504&lt;br/&gt;
172992 block groups&lt;br/&gt;
32768 blocks per group, 32768 fragments per group&lt;br/&gt;
2048 inodes per group&lt;br/&gt;
Superblock backups stored on blocks:&lt;br/&gt;
      32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,&lt;br/&gt;
      4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,&lt;br/&gt;
      102400000, 214990848, 512000000, 550731776, 644972544, 1934917632,&lt;br/&gt;
      2560000000, 3855122432&lt;/p&gt;


&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@f1-oss1d1 ~&amp;#93;&lt;/span&gt;# debugfs -b 4096 -s 32768 -c -R &apos;icheck 3992983288&apos; /dev/mapper/f1-ddn1d-l30&lt;/p&gt;</comment>
                            <comment id="85555" author="yujian" created="Tue, 3 Jun 2014 11:02:16 +0000"  >&lt;p&gt;Hi Blake,&lt;/p&gt;

&lt;p&gt;For -O option, you can only specify the features which are not listed in the [defaults] section and [fs_types] subsectionin in the /etc/mke2fs.conf configuration file.&lt;/p&gt;

&lt;p&gt;Is there anything else I can help in this ticket?&lt;/p&gt;</comment>
                            <comment id="85570" author="blakecaldwell" created="Tue, 3 Jun 2014 13:32:17 +0000"  >&lt;p&gt;That answers it. Thanks!&lt;/p&gt;</comment>
                            <comment id="85588" author="yujian" created="Tue, 3 Jun 2014 14:44:37 +0000"  >&lt;p&gt;You&apos;re welcome, Blake. May I close this ticket?&lt;/p&gt;</comment>
                            <comment id="85592" author="blakecaldwell" created="Tue, 3 Jun 2014 14:52:11 +0000"  >&lt;p&gt;Yes. Please do.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzwnhz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>14152</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>