Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 24 Jul 2002 15:59:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 24 Jul 2002 15:59:10 -0400 Received: from chaos.analogic.com ([204.178.40.224]:9601 "EHLO chaos.analogic.com") by vger.kernel.org with ESMTP id ; Wed, 24 Jul 2002 15:59:09 -0400 Date: Wed, 24 Jul 2002 16:03:29 -0400 (EDT) From: "Richard B. Johnson" Reply-To: root@chaos.analogic.com To: Andries Brouwer cc: Kareem Dana , Andrew Rodland , linux-kernel@vger.kernel.org Subject: Re: loop.o device busy after umount In-Reply-To: <20020724194130.GB13180@win.tue.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1209 Lines: 35 On Wed, 24 Jul 2002, Andries Brouwer wrote: > On Wed, Jul 24, 2002 at 03:33:19PM -0400, Kareem Dana wrote: > > > losetup worked like a charm. Thanks. Any reason umount would not do that automatically though? > > Read mount(8), the places where losetup is mentioned. It works in my system and `umount` is version 2.10o umount: umount-2.10o It works because (strace output), umount does the LOOP_CLR_FD ioctl(). munmap(0x400aa000, 4096) = 0 oldumount("/mnt") = 0 open("/dev/loop0", O_RDONLY) = 3 ioctl(3, LOOP_CLR_FD, 0) = 0 close(3) = 0 If you don't have such an `umount`, loop will remain active, preventing the module from being unloaded. Cheers, Dick Johnson Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips). The US military has given us many words, FUBAR, SNAFU, now ENRON. Yes, top management were graduates of West Point and Annapolis. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/