From owner-freebsd-current@FreeBSD.ORG Sun Jun 1 10:49:16 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 DF17D37B401; Sun, 1 Jun 2003 10:49:16 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5247243FB1; Sun, 1 Jun 2003 10:49:16 -0700 (PDT) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h51HiKZ28933; Sun, 1 Jun 2003 10:44:20 -0700 Received: from btc.adaptec.com (hollin.btc.adaptec.com [10.100.253.56]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id KAA24601; Sun, 1 Jun 2003 10:49:15 -0700 (PDT) Message-ID: <3EDA3BFA.1020602@btc.adaptec.com> Date: Sun, 01 Jun 2003 11:46:34 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Leidinger References: <200306011300.h51D0DMH042667@fledge.watson.org> <20030601165406.20550ba0.Alexander@Leidinger.net> In-Reply-To: <20030601165406.20550ba0.Alexander@Leidinger.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: rwatson@freebsd.org cc: re@freebsd.org cc: current@freebsd.org Subject: Re: 5.1-RELEASE TODO 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: Sun, 01 Jun 2003 17:49:17 -0000 Alexander Leidinger wrote: > On Sun, 1 Jun 2003 09:00:13 -0400 (EDT) > Robert Watson wrote: > > >> Areas requiring immediate testing > > > I already reported to -current that I wasn't able to umount a msdosfs > slice a while ago (umount failed with "busy" and the slice was still > mounted), last week I had the possibility to test it with a May 25 > kernel again and I still wasn't able to umount the msdosfs slice. I > tried not with the same harddisk as last time and the slices wheren't > created by the same Windows system, so I exclude the possibility of a > damaged slice. > > I try to get time to connect the harddisk again to my system (with a May > 30 kernel) before I return the disk, but I think the issue should get > added to the list of issues to look at before 5.1 (at least to be able > to add it to the errata). > > Bye, > Alexander. > I've mounted many MSDOS filesystems recently without problems. Do have any other information about this? Did you verify that there were no open vnodes on the filesystem? Scott