![]() | |||||||||||||
Messages in this thread |
> 2. When a filesystem is remounted read-only, it is *not* marked > clean if it has in-use, 0-nlink inodes. If a following "umount" > or "remount" finds no such inodes, *then* the filesystem can be > marked clean. No. When a file system is mounted R/O, the expectation is that _no_ write access occurs on it (like with a hardware R/O device). After you have remounted it R/O, a subsequent umount may not write to the device. Thus you can't mark it clean afterwards. (I don't know if anything depends on this behavior, but I think this is a common assumption which should not be broken.) Plus, this is not nice UI-wise: nobody expects the system to fsck after a shutdown which looks completely OK. (People who don't know from experience how robust ext2fs really is might go into panic :-) olaf - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu | ||||||||||||
| Last update: 2005-03-22 12:43 [W:0.130 / U:0.390 seconds] ©2003-2008 Jasper Spaans | |||||||||||||