From hsu@clinet.fi  Sat Mar 23 15:00:50 1996
Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA17649
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 23 Mar 1996 15:00:44 -0800 (PST)
Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.7.3/8.6.4) with ESMTP id BAA26088 for <FreeBSD-gnats-submit@freebsd.org>; Sun, 24 Mar 1996 01:00:19 +0200 (EET)
Received: (root@localhost) by katiska.clinet.fi (8.7.4/8.6.4) id BAA17185; Sun, 24 Mar 1996 01:00:09 +0200 (EET)
Message-Id: <199603232300.BAA17185@katiska.clinet.fi>
Date: Sun, 24 Mar 1996 01:00:09 +0200 (EET)
From: Heikki Suonsivu <hsu@clinet.fi>
Reply-To: hsu@clinet.fi
To: FreeBSD-gnats-submit@freebsd.org
Subject: File system corruption (2 cases)
X-Send-Pr-Version: 3.2

>Number:         1098
>Category:       kern
>Synopsis:       File system corruption (2 cases)
>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 Mar 23 15:10:01 PST 1996
>Closed-Date:    Mon Apr 13 01:55:11 PDT 1998
>Last-Modified:  Mon Apr 13 01:55:31 PDT 1998
>Originator:     Heikki Suonsivu
>Release:        FreeBSD 2.2-CURRENT i386
>Organization:
Clinet, Espoo, Finland
>Environment:

	First case: P90 news server, two Adaptek 2940s, 2*4G news spool,
	1 * 4G root/usr, 1 * 1G news history.  News disks were mounted
	async when this happened.

	Second case: 486-100, IDE disks, 1*400M root/usr, 1.2G local.
	No async mounts.

	Kernels are from mid-february sups.

>Description:

	Filesystems get seriosly corrupted.  Files and directories
	which are in active use at the time of the crash are corrupted.

	fsck -y does not fix directories, it becomes a loop until
	broken directory is manually clri'd, fsck removes cleared
	inodes but after salvaging the damaged directory it also salvages
	cleared inodes, thus never getting rid of cleared files.  clring
	the damaged directory fixes this.

	In the first case, large number of news directories were corrupted,
	in addition to small damage on all disks.

	In the second case, things like /dev, /usr/libexec and several
	other directories actively used were lost.  libc.so.2.2 was
	corrupted (at least).  The common thing was that all the things
	corrupted were the ones with most active use, and things corrupted
	were not necessarily things being modified (libexec and libc hardly
	change often).  

	In the second case the computer first seemed to become confused,
	and finally locked up.  After reboot it did not come up as /dev
	was corrupted.

>How-To-Repeat:

	I don't know.  One happened to an unattended machine (news server),
	the second case could have been a shock by hitting the table
	the computer was on, but the symptoms are exactly the same
	for the unattended machine.

	It seems that everything in the buffer cache was
	corrupted and then written back to the disk.  Ie. it smashes
	everything important.

>Fix:
	
	I wish I knew.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: scrappy 
State-Changed-When: Mon Oct 21 23:23:09 PDT 1996 
State-Changed-Why:  

Dust off the cobwebs - Confirm Status 
State-Changed-From-To: feedback->open 
State-Changed-By: scrappy 
State-Changed-When: Tue Oct 22 02:12:29 PDT 1996 
State-Changed-Why:  

Problem Still Exists 

--- 

From: Heikki Suonsivu <hsu@clinet.fi> 

I think this still exists.  This is problem with fsck; it cannot fix 
certain problems which are created by either 

- async mounts 

- current for last couple of weeks 

and can be worked around by clri'ng the offending inode. 


From: Heikki Suonsivu <hsu@clinet.fi>
To: freebsd-gnats-submit@freebsd.org
Cc: hsu@clinet.fi
Subject: kern/1098 File system corruption (2 cases)
Date: Sat, 28 Mar 1998 04:33:44 +0200 (EET)

 fsck has been patched since this, so I am not quite sure if this any more
 exists.  I haven't seen it for long time, so I think this can be closed. 
 
 Studded@dal.net writes:
  > Greetings, :)
  > 
  > 	I am writing to you in regards to your FreeBSD Problem
  > Report. The FreeBSD project is currently conducting a beta test on
  > version 2.2.6 and feedback as to whether you are still experiencing
  > your problem would be very valuable. 
  > 
  > 	If you are still experiencing the problem you reported, it
  > would help the project track the problem if you could upgrade to the
  > latest snapshot of 2.2.6-Beta (located at releng22.freebsd.org) and
  > test your problem again. 
  > 
  > 	If you have any feedback regarding this Problem Report,
  > whether you are still experiencing the problem or whether the PR can
  > be closed, please mail your response to
  > freebsd-gnats-submit@freebsd.org. Please do not respond directly to
  > me. I am merely a humble volunteer and have no official connection to
  > the FreeBSD project. Therefore I cannot make any changes to the status
  > of your Problem Report. It is also very important that you include 
  > the category and number of your Problem Report (kern/1098)
  > in the subject line of your response.
  > 
  > 	Another option if you need a refresher on the details of your
  > problem or would like to submit a followup is to use the web page
  > interface and look up your PR by number.
  > http://www.freebsd.org/cgi/query-pr-summary.cgi
  > 
  > 	Thank you for helping to make this the greatest release of
  > FreeBSD ever.
  > 
  > Doug
  > 
  > 
  > -- 
  > ***         Chief Operations Officer, DALnet IRC network       ***
  > *** Proud operator, designer and maintainer of the world's largest
  > *** Internet Relay Chat server.  5,328 clients and still growing.
  > *** Try spider.dal.net on ports 6662-4    (Powered by FreeBSD)
  > 
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Mon Apr 13 01:55:11 PDT 1998 
State-Changed-Why:  
originator told us so 
>Unformatted:
