From: Terry <td3201@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: ext4 won't mount - fsck required - 2nd fsck in less than a week
Date: Sun, 9 Sep 2012 21:34:10 -0500 [thread overview]
Message-ID: <CAHSRzpC4bnZs1G8BHcuQL6Bf9cKiVb15Ha0sybRdkpwUZbdMKQ@mail.gmail.com> (raw)
Hello,
As the subject says, we have a 15 TB fsck drive that won't mount with
these errors:
Sep 9 20:02:20 narf kernel: EXT4-fs (dm-9): ext4_check_descriptors:
Inode bitmap for group 3200 not in group (block 4161027887)!
Sep 9 20:02:20 narf kernel: EXT4-fs (dm-9): group descriptors corrupted!
We did a proactive fsck on Tuesday of last week because it was
starting to give filesystem errors. It ran through and mounted fine.
The filesystem lives on an equallogic SAN spread across 36 drives.
Could this be something with the physical layer or is it not abnormal
to have to run multiple rounds of fsck to fully fix an issue?
Thanks!
next reply other threads:[~2012-09-10 2:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 2:34 Terry [this message]
2012-09-10 2:47 ` ext4 won't mount - fsck required - 2nd fsck in less than a week Theodore Ts'o
2012-09-10 2:53 ` Terry
2012-09-10 3:18 ` Terry
2012-09-10 13:48 ` Terry
2012-09-10 13:56 ` Terry
2012-09-11 16:22 ` Terry
2012-09-11 17:00 ` Theodore Ts'o
2012-09-11 17:07 ` Terry
2012-09-11 18:06 ` Theodore Ts'o
2012-09-11 18:16 ` Eric Sandeen
2012-09-11 17:59 ` Lukáš Czerner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHSRzpC4bnZs1G8BHcuQL6Bf9cKiVb15Ha0sybRdkpwUZbdMKQ@mail.gmail.com \
--to=td3201@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).