Re: [BUG] remount ro on loopback mount leaves unmountable filesystem behind
- Date: Tue, 13 May 2008 08:42:03 -0400
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Subject: Re: [BUG] remount ro on loopback mount leaves unmountable filesystem behind
On Tue, May 13, 2008 at 10:07:10PM +1000, David Chinner wrote: > Anyway, I'll hard code loop device numbers into the script so > I can just forget about this problem. Thanks, Christoph. hardcoding them is a little dangerous because a system might aswell have them in use already, e.g. for CD images. Just use losetup -f to find the first free one and keep it in a shell variable. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [BUG] remount ro on loopback mount leaves unmountable filesystem behind
- From: H. Peter Anvin
- Re: [BUG] remount ro on loopback mount leaves unmountable filesystem behind
- References:
- [BUG] remount ro on loopback mount leaves unmountable filesystem behind
- From: David Chinner
- Re: [BUG] remount ro on loopback mount leaves unmountable filesystem behind
- From: Christoph Hellwig
- Re: [BUG] remount ro on loopback mount leaves unmountable filesystem behind
- From: David Chinner
- [BUG] remount ro on loopback mount leaves unmountable filesystem behind
- Prev by Date: Re: [PATCH 0/3] bootmem2 III
- Next by Date: Re: [PATCH 1/1] [MTD/MAPS] Blackfin Async Flash Maps: Handle the case where flash memory and ethernet mac/phy are mapped onto the same async bank
- Previous by thread: Re: [BUG] remount ro on loopback mount leaves unmountable filesystem behind
- Next by thread: Re: [BUG] remount ro on loopback mount leaves unmountable filesystem behind
- Index(es):