On 12/28/2010 03:32 PM, Ted Ts'o wrote:
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.
I suggest to decode it in GMT then.
Like this it's not possible to guess it's a "time" value, and hence that
it's an *old* error. I thought it was a pointer to something, and so I
thought the error was happening now, or more likely (since it was
triggered after 300 seconds) that it was some inconsistency in the
filesystem being detected now, in some kind of lazy check.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
