From owner-freebsd-hackers Sat Dec 7 23:26:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5342537B401 for ; Sat, 7 Dec 2002 23:26:41 -0800 (PST) Received: from priv-edtnes62.telusplanet.net (outbound01.telus.net [199.185.220.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F4B743EA9 for ; Sat, 7 Dec 2002 23:26:40 -0800 (PST) (envelope-from sh@bel.bc.ca) Received: from dbs ([216.232.29.145]) by priv-edtnes62.telusplanet.net (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with SMTP id <20021208072640.YBOA1598.priv-edtnes62.telusplanet.net@dbs> for ; Sun, 8 Dec 2002 00:26:40 -0700 Message-ID: <000c01c29e8b$2ecfd390$911de8d8@slugabed.org> From: "Sean Hamilton" To: Subject: umount -f safety Date: Sat, 7 Dec 2002 23:26:53 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greetings, In short, how safe is umount -f? I've been given the task of creating a CD jukebox with Samba. I've got a few dozen ISO images, and a directory with a number of subdirectories named after all the clients. Then, in samba, I have a share with a path of /store/images/%m, so each client receives a unique view of that share. To change CDs, I am executing, for example: # unmount old cd umount -f /store/mount/someclient vnconfig -u vn4 # and mount new one vnconfig vn4 /store/images/blah.iso mount -t cd9660 /dev/vn4 /store/mount/someclient This works great, but I seem to recall reading that umount -f might cause panics, and since this server is also a network gateway, I'd prefer that not occur. I need to umount -f because the samba server keeps its working directory in there, presumably it chroots. The alternative would be to kill off the samba server serving that one client, then quickly remount and hope the client doesn't reconnect, but of course that's a big hack. The server is running 4.7-RELEASE. I've only recently implemented this, so it has not seen heavy load, nor has it panicked. thanks, sh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message