Messages in this thread |  | | | Date | Thu, 24 Sep 1998 15:33:41 +0100 | | From | "Stephen C. Tweedie" <> | | Subject | Re: 2.1.122 and unmouting problems |
| |
Hi,
On Thu, 17 Sep 1998 07:52:10 -0600 (MDT), dbrodsky@cs.ualberta.ca said:
> I notices that in the pre-2.1.122 and 2.1.122 itself when umount is > called to remount root as ro for a shutdown:
> mount -n -v -o remount,ro /
> it fails saying that the device is busy.
That's because the device is busy.
The problem occurs when you have a file handle still open on a deleted file somewhere. Previous kernels incorrectly failed to spot this problem: obviously, deleting such a file needs write access to the device, and since the file will be deleted when it is finally closed, the close needs write access.
The old kernels would fail silently in this case, but the current kernels will refuse to remount the filesystem readonly, ensuring that the deleted file will be correctly cleaned up by fsck on the subsequent reboot.
--Stephen
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
|  |