From owner-freebsd-current@FreeBSD.ORG  Sun Dec 14 09:05:10 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C7CA416A4CF
	for <current@freebsd.org>; Sun, 14 Dec 2003 09:05:10 -0800 (PST)
Received: from smtp.web.de (smtp04.web.de [217.72.192.208])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 85D4843D1F
	for <current@freebsd.org>; Sun, 14 Dec 2003 09:05:09 -0800 (PST)
	(envelope-from yanestra@web.de)
Received: from dsl-082-082-137-190.arcor-ip.net ([82.82.137.190] helo=web.de)
	by smtp.web.de with asmtp (TLSv1:RC4-MD5:128)
	(WEB.DE 4.99 #566)
	id 1AVZg3-0005B6-00
	for current@freebsd.org; Sun, 14 Dec 2003 18:05:08 +0100
Message-ID: <3FDC984A.70805@web.de>
Date: Sun, 14 Dec 2003 18:05:14 +0100
From: "Klaus-J. Wolf" <yanestra@web.de>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031210
X-Accept-Language: en-us, en, de
MIME-Version: 1.0
To: current@freebsd.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Sender: yanestra@web.de
Subject: [RC1] ext2fs broken?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Dec 2003 17:05:10 -0000

Hi,

I have observed some strange behaviour of mounted ext2fs (*ick*) 
filesystems. The strange behaviour ranges from when unpacking a tar in a 
mounted ext2fs filesystem getting "cannot open: Operation not permitted" 
or "...File exists" and ls(1) saying the whole device its empty. 
Sometimes directories disappear, the block count is massively different 
from what Linux says about it.

Example of what can happen when trying to umount the device:

fsync: giving up on dirty: 0xc6339618: tag ext2fs, type VDIR, usecount 
1, writec
ount 0, refcount 3, lock type ext2fs: EXCL (count 1) by thread 0xc46783c0
        ino 57, on dev da0s2 (4, 40)

I have no experience in filesystem debugging, if there is more info 
needed, please tell me how to collect it.

Regards,
k.j.