From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
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 09:19:17 +0100 [thread overview]
Message-ID: <20101228081917.GA1351@bitwizard.nl> (raw)
In-Reply-To: <20101228025343.GD10149@thunk.org>
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?
OK, the chances are that he has rebooted since november, and that an
older fsck fixed the errors, but not cleared the "fs errror log". Would
these errors have triggered a "remount-readonly" if the fs was mounted
like that?
I don't reboot that often:
obelix:~> uptime
09:16:19 up 175 days, 19:04, 19 users, load average: 110.10, 110.61, 111.22
(and yes, the load is quite high on that machine. I won't polute this
thread about that....)
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
next prev parent reply other threads:[~2010-12-28 8:19 UTC|newest]
Thread overview: 11+ 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 [this message]
2010-12-28 9:09 ` Con Kolivas
2010-12-28 10:30 ` Amir Goldstein
2011-01-01 17:20 ` Ric Wheeler
2010-12-28 14:15 ` Ted Ts'o
2010-12-28 10:41 ` torn5
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=20101228081917.GA1351@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--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