From: Ric Wheeler <rwheeler@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: "Ted Ts'o" <tytso@mit.edu>, Rogier Wolff <R.E.Wolff@bitwizard.nl>,
Con Kolivas <kernel@kolivas.org>,
linux-kernel@vger.kernel.org, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Regular ext4 error warning with HD in USB dock
Date: Sat, 01 Jan 2011 12:20:04 -0500 [thread overview]
Message-ID: <4D1F6244.7050203@redhat.com> (raw)
In-Reply-To: <AANLkTim_5Yx1RQFHYbmh40xx7c5sU9XsXZEzegC4G=1x@mail.gmail.com>
On 12/28/2010 05:30 AM, Amir Goldstein wrote:
> On Tue, Dec 28, 2010 at 10:19 AM, Rogier Wolff<R.E.Wolff@bitwizard.nl> wrote:
>> On Mon, Dec 27, 2010 at 09:53:43PM -0500, Ted Ts'o wrote:
>>> On Tue, Dec 28, 2010 at 09:53:45AM +1100, Con Kolivas wrote:
>>>> [1048401.773270] EXT4-fs (sde8): mounted filesystem with writeback data mode.
>>>> Opts: (null)
>>>> [1048702.736011] EXT4-fs (sde8): error count: 3
>>>> [1048702.736016] EXT4-fs (sde8): initial error at 1289053677:
>>>> ext4_journal_start_sb:251
>>>> [1048702.736018] EXT4-fs (sde8): last error at 1289080948: ext4_put_super:719
>>> That's actually not an error. It's a report which is generated every
>>> 24 hours, indicating that there has been 3 errors since the last time
>>> the error count has been cleared, with the first error taking place at
>>> Sat Nov 6 10:27:57 2010 (US/Eastern) in the function
>>> ext4_journal_start_sb(), at line 251, and the most recent error taking
>>> place at Sat Nov 6 18:02:28 2010 (US/Eastern), in the function
>>> ext4_put_super() at line 719. This is a new feature which was added
>>> in 2.6.36.
>> Nice. But the issue you're not mentioning is: What errors could have
>> happened on the 6th of november? Should Con worry about those errors?
>>
> Ted,
>
> I would like to use this opportunity to remind you about my
> record_journal_errstr()
> implementation, see:
> https://github.com/amir73il/ext4-snapshots/blob/next3-stable/fs/next3/super.c#L157
>
> It records the initial errors messages (which I found to be the most
> interesting),
> in a message buffer on the unused space after the journal super block
> (3K on a 4K block fs).
>
> fsck prints out those messages and clears the buffer.
> In under a year of Next3 fs in beta and production, it has helped me many times
> to analyse bugs post-mortem and find the problem.
>
> If there is demand, I can post the patch for Ext4.
>
> Amir.
I do think that this sounds like a useful addition - should be very useful in
doing post mortem analysis...
Thanks!
Ric
next prev parent reply other threads:[~2011-01-01 17:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 22:53 Regular ext4 error warning with HD in USB dock Con Kolivas
2010-12-28 2:53 ` Ted Ts'o
2010-12-28 8:19 ` Rogier Wolff
2010-12-28 9:09 ` Con Kolivas
2010-12-28 10:30 ` Amir Goldstein
2011-01-01 17:20 ` Ric Wheeler [this message]
2011-01-02 19:23 ` Amir Goldstein
2011-01-07 5:26 ` Ted Ts'o
2011-01-07 19:41 ` Amir Goldstein
2011-01-07 21:07 ` Amir Goldstein
2011-01-07 22:12 ` Amir Goldstein
2011-01-08 20:28 ` Amir Goldstein
2011-01-08 8:05 ` Rogier Wolff
2011-01-08 20:06 ` Amir Goldstein
2011-01-08 22:00 ` Ted Ts'o
2011-01-09 8:12 ` Rogier Wolff
2011-01-09 14:58 ` Ted Ts'o
2011-01-10 7:45 ` Andreas Dilger
2011-01-10 8:49 ` Rogier Wolff
2011-01-07 5:28 ` Ted Ts'o
2011-01-07 19:43 ` Amir Goldstein
2011-01-07 20:39 ` Amir Goldstein
2010-12-28 14:15 ` Ted Ts'o
2010-12-28 10:41 ` torn5
[not found] ` <4D19BEF1.9010708-9AbUPqfR1/2XDw4h08c5KA@public.gmane.org>
2010-12-28 14:32 ` Ted Ts'o
2010-12-28 15:02 ` Ben Pfaff
2010-12-28 15:20 ` torn5
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=4D1F6244.7050203@redhat.com \
--to=rwheeler@redhat.com \
--cc=R.E.Wolff@bitwizard.nl \
--cc=adilger.kernel@dilger.ca \
--cc=amir73il@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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).