From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Terry <td3201@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: ext4 won't mount - fsck required - 2nd fsck in less than a week
Date: Tue, 11 Sep 2012 13:16:39 -0500 [thread overview]
Message-ID: <504F8007.7070208@redhat.com> (raw)
In-Reply-To: <20120911180646.GC763@thunk.org>
On 9/11/12 1:06 PM, Theodore Ts'o wrote:
> On Tue, Sep 11, 2012 at 12:07:14PM -0500, Terry wrote:
>>
>> RHEL 6.3 with kernel 2.6.32-279.5.2.el6.x86_64
>
> I'll let Eric or Lukas comment, but as far as I know the ext4 in the
> RHEL 6 kernels has been quite stable (there are a lot of bug fixes
> that have been backported to the RHEL 6 kernel, and while it doesn't
> have some of the newer ext4 features, it doesn't have any of the more
> exciting bugs that might come with the newer features :-).
>
> So I really would strongly suspect the SAN or the SAN-attached storage
> as being flaky, causing the file system corruptions which is leading
> to the kernel and e2fsck complaining.
Right, ext4 is default in RHEL6 and well tended. We'll let support look
at the case, and see what's going on. But I'd certainly troubleshoot
the san as well, esp. to be sure HA is set up properly and not mounting
it twice on 2 nodes etc.
-Eric
> Regards,
>
> - Ted
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-09-11 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 2:34 ext4 won't mount - fsck required - 2nd fsck in less than a week Terry
2012-09-10 2:47 ` 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 [this message]
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=504F8007.7070208@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=td3201@gmail.com \
--cc=tytso@mit.edu \
/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).