Date: Fri, 12 Nov 2010 23:13:42 +0530 From: Aditya Sarawgi <sarawgi.aditya@gmail.com> To: Doug Barton <dougb@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: Minor problem re-mounting ext2fs system Message-ID: <AANLkTik0aiXJXmjWjZz_4k1ZvjtVd0ZqJq5Bx9O_JDE1@mail.gmail.com> In-Reply-To: <4CDB888E.6030005@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
Hi, On Thu, Nov 11, 2010 at 11:39 AM, Doug Barton <dougb@freebsd.org> wrote: > Even after a clean shutdown I get this error at nearly every reboot: > > kernel: last write time is in the future. > kernel: (by less than a day, probably due to the hardware clock being > incorrectly set). > kernel: FIXED. > The ext2fs superblock (the structure that keeps summary and important information for the filesystem) has one of the field has timestamp. Now clearly it doesn't make any sense for the filesystem getting mounted to have a future timestamp. It regards this has inconsistency and hence you need to fsck it. You need to figure out why is it taking a future timestamp. You can analyse the superblock by dumpe2fs from e2fsprogs. > It does get fixed, but it requires the fsck program from e2fsprogs to do it. > > > Doug > > -- > > Nothin' ever doesn't change, but nothin' changes much. > -- OK Go > > Breadth of IT experience, and depth of knowledge in the DNS. > Yours for the right price. :) http://SupersetSolutions.com/ > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > -- Cheers, Aditya Sarawgihome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTik0aiXJXmjWjZz_4k1ZvjtVd0ZqJq5Bx9O_JDE1>