public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Holvenstot <cholvenstot@comcast.net>
To: Benoit Boissinot <bboissin@gmail.com>
Cc: Chris Holvenstot <saltydog@houston.rr.com>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Kernel / Fliesystem Error
Date: Thu, 09 Aug 2007 15:02:56 -0500	[thread overview]
Message-ID: <1186689776.6976.12.camel@localhost> (raw)
In-Reply-To: <40f323d00708090531p34f1fffcub5186d358f9beafb@mail.gmail.com>

Benoit - 

I am a little unsure of the protocol involved here but I will respond to
this, the last message I received on the topic.

As I feared, I was giving an incomplete picture with my original report
and did not even realize it.  

On the systems I was getting  the error on I used the mkinitramfs
command to build the initrd.img file.  This was basically the 2.6.23
systems.  I did this because the documentation seemed to indicate that
this would clear up the "devfs unknown file system" messages I was
getting at boot.

Which it did.

However, when I rebuilt the 2.6.22.1 kernel's initrd.img file with
mkinitramfs instead of mkinitrd the 2.6.22.1 kernel started getting the
"superblock time stamp" errors too.

So the problem is NOT with the kernel code - it appears to be either
with mkinitramfs or my process.  With the way my luck has been running
of late it is likely that the fault is with my process.

So I once again thank you for your response, and apologize for what now
appears to be a false alarm.  Since the initramfs tool set was provided
with the Ubuntu release I am using as a base I will try to locate
someone there to assist with this issue.

Chris



On Thu, 2007-08-09 at 14:31 +0200, Benoit Boissinot wrote:
> On 8/9/07, Chris Holvenstot <cholvenstot@comcast.net> wrote:
> > > 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.
> >
> > 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.
> >
> 
> But very likely time keeping was broken between .22 and .23-rc.
> Probably not ext3.
> 
> regards,
> 
> Benoit


  reply	other threads:[~2007-08-09 20:01 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
2007-08-09 12:31   ` Benoit Boissinot
2007-08-09 20:02     ` Chris Holvenstot [this message]
  -- 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=1186689776.6976.12.camel@localhost \
    --to=cholvenstot@comcast.net \
    --cc=bboissin@gmail.com \
    --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