From owner-freebsd-fs@FreeBSD.ORG Fri Nov 12 17:43:44 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D9DB106566B; Fri, 12 Nov 2010 17:43:44 +0000 (UTC) (envelope-from sarawgi.aditya@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id BA7448FC17; Fri, 12 Nov 2010 17:43:43 +0000 (UTC) Received: by iwn39 with SMTP id 39so3747096iwn.13 for ; Fri, 12 Nov 2010 09:43:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=cp0173sigjDNVvCPuetu4pnYqA2uRnHVLIN2JtltlCI=; b=REPCLxRLYMoj/tRqLJ2JckzEMIXwyB3o5MPyKsiIuVLzBI2818Dn/jQyABIR1zGB2y nrZpWSG8NQWciGTTAU0DnQWDEmuHAECHpL0Z5o4K5AW59MpERsaNKHJ18Gjz1BIjPyrM Sp2OAGCXISALPM3W2VONkcuCSmovKjSiYvISA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ddX2x7SLfOIlErFnrk3fj90t0GZvGH32RS4npSUH4HzvaJTeKhmmBfJz0TTUS+8Umq sLTdkmrqfvjYGpl+FuBztrXW2TWb/SB9LNK70XIIstHOT1ZrOuZt3cTDOkRKSCREJLMd 6t2uGSLR3DLFpUakcmWXOXvXCvA/IxGNlwtLE= MIME-Version: 1.0 Received: by 10.231.183.136 with SMTP id cg8mr2267704ibb.114.1289583822776; Fri, 12 Nov 2010 09:43:42 -0800 (PST) Received: by 10.231.253.81 with HTTP; Fri, 12 Nov 2010 09:43:42 -0800 (PST) In-Reply-To: <4CDB888E.6030005@FreeBSD.org> References: <4CDB888E.6030005@FreeBSD.org> Date: Fri, 12 Nov 2010 23:13:42 +0530 Message-ID: From: Aditya Sarawgi To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Minor problem re-mounting ext2fs system X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2010 17:43:44 -0000 Hi, On Thu, Nov 11, 2010 at 11:39 AM, Doug Barton 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 > > -- > > =A0 =A0 =A0 =A0Nothin' ever doesn't change, but nothin' changes much. > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0-- OK Go > > =A0 =A0 =A0 =A0Breadth of IT experience, and depth of knowledge in the DN= S. > =A0 =A0 =A0 =A0Yours for the right price. =A0:) =A0http://SupersetSolutio= ns.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" > --=20 Cheers, Aditya Sarawgi