Re: loop.o device busy after umount

Andries Brouwer (aebr@win.tue.nl)
Wed, 24 Jul 2002 21:41:30 +0200

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Thomas Molina: "2.5 Problem Reports Status"
Previous message: Andrew Morton: "Re: kernel BUG at page_alloc.c:92! & page allocation failure. order:0,"
In reply to: Kareem Dana: "Re: loop.o device busy after umount"
Next in thread: Andrew Rodland: "Re: loop.o device busy after umount"

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.
-
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/

Next message: Thomas Molina: "2.5 Problem Reports Status"
Previous message: Andrew Morton: "Re: kernel BUG at page_alloc.c:92! & page allocation failure. order:0,"
In reply to: Kareem Dana: "Re: loop.o device busy after umount"
Next in thread: Andrew Rodland: "Re: loop.o device busy after umount"