[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080513102340.GA15112@infradead.org>
Date: Tue, 13 May 2008 06:23:40 -0400
From: Christoph Hellwig <hch@...radead.org>
To: David Chinner <dgc@....com>
Cc: lkml <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
util-linux-ng@...r.kernel.org
Subject: Re: [BUG] remount ro on loopback mount leaves unmountable
filesystem behind
On Tue, May 13, 2008 at 06:50:47PM +1000, David Chinner wrote:
> Same thing, but remounting the loop filesystem readonly
> before unmounting:
>
> $ mount -t xfs /dev/sdb6 /mnt/scratch
> $ mkdir /mnt/scratch/mnt
> $ touch /mnt/scratch/img
> $ mkfs.xfs -f -d file,name=/mnt/scratch/img,size=1g
> $ mount -t xfs -o loop /mnt/scratch/img /mnt/scratch/mnt
> $ mount -t xfs -o remount,ro /mnt/scratch/img /mnt/scratch/mnt
> $ umount /mnt/scratch/mnt
> $ umount /mnt/scratch
> umount: /mnt/scratch: device is busy
> umount: /mnt/scratch: device is busy
This is a problem in mount, no the kernel. Before the remount the
/etc mtab looks something like this:
/qemu/test.img /mnt xfs rw,loop=/dev/loop0 0 0
and after it looks something like this:
/qemu/test.img /mnt xfs ro 0 0
As a workaround do a losetup -d /dev/loop0 after unmounting the
filesystem.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists