Date: Sun, 01 Jun 2003 11:46:34 -0600 From: Scott Long <scott_long@btc.adaptec.com> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: current@freebsd.org Subject: Re: 5.1-RELEASE TODO Message-ID: <3EDA3BFA.1020602@btc.adaptec.com> In-Reply-To: <20030601165406.20550ba0.Alexander@Leidinger.net> References: <200306011300.h51D0DMH042667@fledge.watson.org> <20030601165406.20550ba0.Alexander@Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Leidinger wrote: > On Sun, 1 Jun 2003 09:00:13 -0400 (EDT) > Robert Watson <rwatson@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EDA3BFA.1020602>