Date: Thu, 07 May 2015 13:34:45 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Wojciech Puchar <wojtek@puchar.net>, "Julian H. Stacey" <jhs@berklix.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Ryan Stone <rysto32@gmail.com>, NGie Cooper <yaneurabeya@gmail.com> Subject: Re: What's required to make removal of a mounted USB stick safe? Message-ID: <554B4DD5.9090006@selasky.org> In-Reply-To: <alpine.BSF.2.20.1505071320590.870@laptop.wojtek.intra> References: <201505062159.t46Lx0iZ028607@fire.js.berklix.net> <alpine.BSF.2.20.1505071320590.870@laptop.wojtek.intra>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/07/15 13:21, Wojciech Puchar wrote: >> - Deep kernel work (dont hold your breath, see 30 above, & don't look >> at me :-) >> - Cobble up some C to run from user space, not as root, >> so that your UFS is not mounted, but accessed by user level >> programs (much like mwrite & mread for accessing DOS media of old) >> - man 8 amd : set a short timeout to auto unmount, >> it wont total solve your problem, but should lessen the frequency of >> panics. >> - Mount the USB media on a spare laptop running as an NFS+ AMD server, >> then access the FS via NFS from your real client big PC. When >> you pull the stick by accident forgetting its mounted, just the >> laptop crashes afte a bit, the AMD access on the other PC just >> hangs but doesnt crash. >> - Encourage A SOC (google summer of code) student to look at it, >> probably wont come to a solution though, see 30 above. >> - Toss money at the problem :-) If your company can afford some cash, >> either: >> - help fund FreeBSD Foundation & ask them to solve it, >> - Or pay some consultant somewhere to look at it, Here's a globaly >> geographicaly indexed list http://berklix.com/consultants/ >> maybe there's one near your company ? > - mount using fuse Hi, I'm very happy you understand this is not a USB problem ;-) --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?554B4DD5.9090006>