From owner-freebsd-current@FreeBSD.ORG Sun Sep 26 01:15:32 2004 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 066FA16A4CE for ; Sun, 26 Sep 2004 01:15:32 +0000 (GMT) Received: from mail.airnet.com.au (mail.airnet.com.au [202.174.32.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id A55D643D53 for ; Sun, 26 Sep 2004 01:15:31 +0000 (GMT) (envelope-from Lucas.James@LDJcs.Com.Au) Received: from mail.ldjcs.com.au (dsl2-62.gw1.adl1.airnet.com.au [202.174.37.62]) by mail.airnet.com.au (Postfix) with ESMTP id E84C78D5D1 for ; Sun, 26 Sep 2004 10:38:04 +0930 (CST) Received: from draco.ldjcs.com.au (draco.ldjcs.com.au [203.17.30.8]) by mail.ldjcs.com.au (8.13.1/8.13.1) with ESMTP id i8Q1FSn1079556 for ; Sun, 26 Sep 2004 10:45:28 +0930 (CST) (envelope-from Lucas.James@LDJcs.Com.Au) From: Lucas James To: freebsd-current@freebsd.org Date: Sun, 26 Sep 2004 10:36:44 +0930 User-Agent: KMail/1.7 References: <41555396.4030009@fer.hr> <20040926021347.721a025f.benlutz@datacomm.ch> <20040926005943.GA61350@parodius.com> In-Reply-To: <20040926005943.GA61350@parodius.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2644352.oJSfmMxJ0x"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200409261036.49484.Lucas.James@LDJcs.Com.Au> X-Mailman-Approved-At: Sun, 26 Sep 2004 15:32:32 +0000 Subject: Re: USB memory stick hotswap problems 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, 26 Sep 2004 01:15:32 -0000 --nextPart2644352.oJSfmMxJ0x Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sun, 26 Sep 2004 10:29 am, Jeremy Chadwick wrote: > Can't usbd (or better yet, usbd.conf) be modified or changed in some way > to automatically handle the unmounting of any existing filesystems that > match the device which is mounted? that won't work because usbd only gets the notification of something being= =20 unplugged *after* the fact, and it's too late to do unmounting then. And it can't be modified, because the kernel has no idea when the user is=20 going to yank out the cable. > Seems like we're eventually going to need this to make hot-swappable USB > devices more friendly. I understand why you must unmount a device > before SCSI CAM gets disconnected from it, but it just seems that this > should be a job for usbd. the only way you can ensure data integrity on user-removable devices is to= =20 mount them with -o sync. We should be telling the kernel at some point that this is a removable devi= ce,=20 and not have the kernel complain if we umount it when the device has alread= y=20 disappeared (assuming that we have mounted it with -o sync). Lucas James =2D-=20 The only possible interpretation of any research whatever in the `social sciences' is: some do, some don't. -- Ernest Rutherford --nextPart2644352.oJSfmMxJ0x Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBVhYpS5LuBv475s8RAlcEAKCnhphekybbPc7kaLFhpatuHaaIXgCgpYTa npTVKjqr4wjwz5o7bQaDJJU= =p3FG -----END PGP SIGNATURE----- --nextPart2644352.oJSfmMxJ0x--