From: torn5 <torn5@shiftmail.org>
To: Ted Ts'o <tytso@mit.edu>, 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: Tue, 28 Dec 2010 11:41:53 +0100 [thread overview]
Message-ID: <4D19BEF1.9010708@shiftmail.org> (raw)
In-Reply-To: <20101228025343.GD10149@thunk.org>
On 12/28/2010 03:53 AM, Ted Ts'o wrote:
> On Tue, Dec 28, 2010 at 09:53:45AM +1100, Con Kolivas wrote:
>
>> Since I moved my internal HD into a USB dock externally and mount the ext4
>> filesystem on it, I regularly get the following errors after it has been
>> mounted for a while (see timecode). It doesn't seem to matter which recent
>> kernel I use.
>>
>> [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.
>
This is going to be a faq...
I suppose the datetime is encoded (what format is that?) in that long
number after "at".
May I suggest the datetime gets decoded in the printing?
Also may I suggest that the error happens immediately after mount and
not after 300 seconds from mount?
I just subscribed to this list exactly to report the same kind of error.
Last week I was doing reliability tests for open-iscsi and this error
drove me crazy. I spent days in tests where I thought I could reproduce
an error in open-iscsi by disconnecting and reconnecting the network; I
even reported this to the open-iscsi mailing list, but in fact it was an
old error of the filesystem and it was not getting cleared by my older
e2fsck 1.41.11 .
If that happened immediately after mount or if it spitted the datetime
in human readable format, I would have immediately guessed it was due to
an existing "filesystem problem" (even though I was running fsck.ext4 -f
prior to each mount) but instead I thought it was due to my 5 minutes of
"networks disconnection tests" I was doing after each mount. DOH!
Anyway thanks for your work: excellent filesystem.
PS: I have a question for you regarding ext4 behaviour with SCSI
commands resubmissions... ok I am opening another thread for that.
next prev parent reply other threads:[~2010-12-28 10:42 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
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 [this message]
[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=4D19BEF1.9010708@shiftmail.org \
--to=torn5@shiftmail.org \
--cc=adilger.kernel@dilger.ca \
--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).