From nobody@FreeBSD.ORG Sat Apr  3 07:23:11 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id AF5E4152D9; Sat,  3 Apr 1999 07:22:35 -0800 (PST)
Message-Id: <19990403152235.AF5E4152D9@hub.freebsd.org>
Date: Sat,  3 Apr 1999 07:22:35 -0800 (PST)
From: vmori@cronosnet.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: FSCK reports filesystem ALWAYS "dirty"
X-Send-Pr-Version: www-1.0

>Number:         10929
>Category:       i386
>Synopsis:       FSCK reports filesystem ALWAYS "dirty"
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Apr  3 07:30:01 PST 1999
>Closed-Date:    Sun Apr 4 12:47:58 PDT 1999
>Last-Modified:  Sun Apr  4 12:50:05 PDT 1999
>Originator:     Vittorio Mori
>Release:        3.1
>Organization:
Pyxis Computers
>Environment:
>Description:
If you just launch an "fsck", the filesystem is reported as "dirty". You are prompted to launch fsck again, and you're just into an infinite loop :)


>How-To-Repeat:
It happens on every machine I've tried (more than 5).
>Fix:


>Release-Note:
>Audit-Trail:

From: "Kenneth D. Merry" <ken@plutotech.com>
To: vmori@cronosnet.com
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/10929: FSCK reports filesystem ALWAYS "dirty"
Date: Sat, 3 Apr 1999 11:23:39 -0700 (MST)

 vmori@cronosnet.com wrote...
 > 
 > >Number:         10929
 > >Category:       i386
 > >Synopsis:       FSCK reports filesystem ALWAYS "dirty"
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       high
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Sat Apr  3 07:30:01 PST 1999
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Vittorio Mori
 > >Release:        3.1
 > >Organization:
 > Pyxis Computers
 > >Environment:
 > >Description:
 > If you just launch an "fsck", the filesystem is reported as "dirty". You are prompted to launch fsck again, and you're just into an infinite loop :)
 > 
 > 
 > >How-To-Repeat:
 > It happens on every machine I've tried (more than 5).
 
 Did you try this on a mounted or unmounted filesystem?
 
 Ken
 -- 
 Kenneth Merry
 ken@plutotech.com
 
State-Changed-From-To: open->closed 
State-Changed-By: ken 
State-Changed-When: Sun Apr 4 12:47:58 PDT 1999 
State-Changed-Why:  
After corresponding with the PR submitter, it appears that he was trying to 
fsck a mounted filesystem.  Of course, filesystems that are mounted read-write 
will always be dirty, until you unmount them.  In any case, I think this 
can be chalked up to a misunderstanding of the way things work. 
>Unformatted:
