public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Holvenstot <cholvenstot@comcast.net>
To: Chris Holvenstot <saltydog@houston.rr.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Kernel / Fliesystem Error
Date: Thu, 09 Aug 2007 06:25:30 -0500	[thread overview]
Message-ID: <1186658730.7018.8.camel@localhost> (raw)
In-Reply-To: <1186623555.6613.17.camel@localhost>

> Chris Snook wrote:
>
>The problem here is that your clock is wrong either at mount (boot)
>time or unmount (shutdown) time. There's nothing wrong with ext3,
>except that it happens to be noticing this condition.


Chris - 

I appreciate the response but on the face of it I do not know if I
believe that this is the answer.  I am not the sharpest knife in the
drawer but the following two items still cast a doubt on the answer.

1.  This happens even when the system is rebooted via the shutdown -r
command - not much time for my fat fingers to get in there and dork up
the system clock.

2.  As I stated in the original note, this does NOT happen with kernel
2.6.22.1 - so far I have only seen it with the 2.6.23-rc1, rc2, and
rc2-git1 kernels.

Other than this I would say you were spot on in your analysis.  Maybe
there is something I don't understand here.  If so, pardon me for being
"Thick as a brick" 

Chris






  parent reply	other threads:[~2007-08-09 11:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09  1:39 Kernel / Fliesystem Error Chris Holvenstot
2007-08-09  9:47 ` Chris Snook
2007-08-09 11:25 ` Chris Holvenstot [this message]
2007-08-09 12:31   ` Benoit Boissinot
2007-08-09 20:02     ` Chris Holvenstot
  -- strict thread matches above, loose matches on Subject: below --
2007-08-09 13:27 cholvenstot

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=1186658730.7018.8.camel@localhost \
    --to=cholvenstot@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saltydog@houston.rr.com \
    /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