Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 29 Nov 2001 15:08:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 29 Nov 2001 15:08:48 -0500 Received: from marine.sonic.net ([208.201.224.37]:7711 "HELO marine.sonic.net") by vger.kernel.org with SMTP id ; Thu, 29 Nov 2001 15:08:33 -0500 X-envelope-info: Date: Thu, 29 Nov 2001 12:08:26 -0800 From: Mike Castle To: kernel list Subject: Re: 2.4.14 still not making fs dirty when it should Message-ID: <20011129120826.F7992@thune.mrc-home.com> Reply-To: Mike Castle Mail-Followup-To: Mike Castle , kernel list In-Reply-To: <20011128231504.A26510@elf.ucw.cz> <3C069291.82E205F1@zip.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C069291.82E205F1@zip.com.au> User-Agent: Mutt/1.3.23i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 29, 2001 at 11:54:57AM -0800, Andrew Morton wrote: > Pavel Machek wrote: > > > > Hi! > > > > I still can mount / read/write, press reset, and not get fsck on next > > reboot. That strongly suggests kernel bug to me. > > aargh. I thought that was fixed. How's this look? I'm curious: Why would you WANT this? I always thought that if you didn't make any fs changes, then it should NOT fsck. mrc -- Mike Castle dalgoda@ix.netcom.com www.netcom.com/~dalgoda/ We are all of us living in the shadow of Manhattan. -- Watchmen fatal ("You are in a maze of twisty compiler features, all different"); -- gcc - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/