linux-kernel - Re: Kernel / Fliesystem Error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46BAE29A.6010803@redhat.com>
Date:	Thu, 09 Aug 2007 05:47:06 -0400
From:	Chris Snook <csnook@...hat.com>
To:	Chris Holvenstot <saltydog@...ston.rr.com>
CC:	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: Kernel / Fliesystem Error

Chris Holvenstot wrote:
> 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

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/