From: "Ted Ts'o" <tytso@mit.edu>
To: torn5 <torn5@shiftmail.org>
Cc: 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:32:55 -0500 [thread overview]
Message-ID: <20101228143255.GI10149@thunk.org> (raw)
In-Reply-To: <4D19BEF1.9010708@shiftmail.org>
On Tue, Dec 28, 2010 at 11:41:53AM +0100, torn5 wrote:
>
> This is going to be a faq...
> I suppose the datetime is encoded (what format is that?) in that
> long number after "at".
Number of seconds since January 1st, 1970 midnight GMT. (Standard
Unix-time format). It's hard for the kernel to decode it since it
doesn't know what time-zone you are in, or what your local legislature
has done vis-a-vis arbitrary and cabritious adjustments to the
start/stop date of daylight savings time, etc.
It's easy enough to decode it using perl:
perl -e '$t = localtime(1289053677); print "$t\n"'
> 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?
Hmmm.... maybe. The idea behind the 300 second delay was for the root
file system, to let e2fsck have a chance to fix the file system before
reporting the errors at mount time.
- Ted
next prev parent reply other threads:[~2010-12-28 14:38 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
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 [this message]
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=20101228143255.GI10149@thunk.org \
--to=tytso@mit.edu \
--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=torn5@shiftmail.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