From owner-freebsd-stable@FreeBSD.ORG Fri Jan 18 23:51:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FFD816A417 for ; Fri, 18 Jan 2008 23:51:39 +0000 (UTC) (envelope-from jakob@email.cz) Received: from dev.citybikes.cz (r5o136.net.upc.cz [86.49.14.136]) by mx1.freebsd.org (Postfix) with ESMTP id 19D2C13C455 for ; Fri, 18 Jan 2008 23:51:38 +0000 (UTC) (envelope-from jakob@email.cz) Received: from dev (localhost [127.0.0.1]) by dev.citybikes.cz (8.14.2/8.14.2) with ESMTP id m0II1tJL033821 for ; Fri, 18 Jan 2008 19:01:56 +0100 (CET) (envelope-from jakob@email.cz) Date: Fri, 18 Jan 2008 19:01:55 +0100 From: Jakob To: freebsd-stable@freebsd.org Message-ID: <20080118190155.32294da3@dev> In-Reply-To: References: <20080118120140.2a8170a0@dev> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.1; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: panic when copying to ext2fs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2008 23:51:39 -0000 I think the dump I can see is output of an execution loop in ext2_linux_balloc.c (/usr/src/sys/gnu/fs/ext2fs) from 289 (repeat: label) to 414 (goto repeat:). But I haven't found yet why in previous branch it is ok. On Fri, 18 Jan 2008 14:44:07 +0100 Ivan Voras wrote: > Jakub Siroky wrote: > > I have two large ext2fs partitions (368 and 313GB) to hold data shared between several OSes. While there were no problems on 6-STABLE branch I was quite disappointed after upgrade to 7-STABLE. Whenever I copy/write to ext2fs partition the system freezes totally without crashdump. So I set debugging settings to kernel config (DEBUG,WITNESS,..) and in console I reproduced error situation ending with full screen of unstoppable running text with lot of memory addresses and a few recognisable words: 'new block bit set for ext already' - again with no crashdump. Then I have formatted 1GB partition with ext2fs and the problem on this small partition appears only sometimes. > > Interesting. I have ext2fs partitions in the same size range for the > same purpose under 8-CURRENT and I don't have the problems you > described, so it's unlikely the problem were introduced in 7. Did you > run e2fsck on the file systems? Can you verify there is no hardware or > driver data corruption (though I don't know how would you verify this > one - maybe by writing to the partition from one OS and reading from the > other, amd using md5 to check)? >