From owner-freebsd-current@FreeBSD.ORG Wed Oct 29 00:27:44 2003 Return-Path: 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 4640A16A4CF for ; Wed, 29 Oct 2003 00:27:44 -0800 (PST) Received: from roadrunner.rominet.net (ATuileries-109-1-3-201.w81-48.abo.wanadoo.fr [81.48.116.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id B088643FD7 for ; Wed, 29 Oct 2003 00:27:42 -0800 (PST) (envelope-from at@rominet.net) Received: by roadrunner.rominet.net (Postfix, from userid 1000) id 3118582D5; Wed, 29 Oct 2003 09:27:41 +0100 (CET) Date: Wed, 29 Oct 2003 09:27:41 +0100 From: Alain Thivillon To: current@freebsd.org Message-ID: <20031029082741.GD92762@roadrunner.rominet.net> References: <20031027233558.12920.qmail@verizonmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20031027233558.12920.qmail@verizonmail.com> User-Agent: Mutt/1.3.24i X-Organization: Rominet Networks Inc. X-Operating-System: FreeBSD 4.9-PRERELEASE Subject: Re: cp -Rp /a_dir/w_sub_dirs to gbde vnode on SmartMedia Card locks system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2003 08:27:44 -0000 Donald Creel écrivait (wrote) : > This has been reproducible for the last few weeks. System will crash if > I am strictly from ttyv(n) or using KDE3.x and drag and drop. I have no crashes but i see locks of gbde file systems (no more activity, system idle 100%, file systems unmountable) when copying large files on gbde fs over md. When i restart system, reattach and fsck the gbde fs, all latest modifications are lost (lot of files in lost+found). As this is my first try on gbde, i have not tested against a real disk partition, so maybe this is a md(4) problem. I was running -CURRENT from around 01 October, i have upgraded to yesterday -CURRENT and still the same problem.