public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Holvenstot <saltydog@houston.rr.com>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: Kernel / Fliesystem Error
Date: Wed, 08 Aug 2007 20:39:15 -0500	[thread overview]
Message-ID: <1186623555.6613.17.camel@localhost> (raw)

I think that I may have spotted a minor bug in the 2.6.23 kernel and its
relationship with the EXT3 file system.  I apologize in advance if I am
mistaken, reporting a problem that is already known (I did not spot it
in Bugzilla) or if I am reporting it to the wrong forum.  I made the
decision a just a few weeks ago to participate by running my system on
the newest kernels and this is the first issue I have attempted to
report.

And I know that you have stumble a few times before you get the hang of
it.

I note that on the 2.6.23-rc1, rc2 and rc2-git1 systems that when I boot
I receive the following message each and every time:

/dev/sda1:  Superblock last write time is in the future.  FIXED

This message is repeated once for each hard drive I have (three
traditional PATA and two of the newer SATA drives)

After the message is issued the system seems to run great.

This DOES NOT happen when I am coming up with a 2.6.22.1 kernel.


A thumbnail of my configuration is:

  AMD-64 Dual Core 4600+ on a MSI motherboard
  2 gig of memory
  3 PATA hard disks in an integrated nVidia CK804 controller 
  2 SAS hard disks on an integrated nVidia CK804 controller
  1 IDE DVD/CD driver
  2 USB attached DVD/ CD burner
  nVidia GeForce 7600 PCI video card

Thank you






             reply	other threads:[~2007-08-09  2:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09  1:39 Chris Holvenstot [this message]
2007-08-09  9:47 ` Kernel / Fliesystem Error Chris Snook
2007-08-09 11:25 ` Chris Holvenstot
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=1186623555.6613.17.camel@localhost \
    --to=saltydog@houston.rr.com \
    --cc=linux-kernel@vger.kernel.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