A couple of changes to how xfs behaves w.r.t. readonly mounts. 1) write unmount record even for RO mounts (which may have done recovery) 2) remove readonly checks from xfs_release and xfs_inactive paths Both of these stem from the fact that a readonly mount (as opposed to a ro,norecovery mount) is /not/ guaranteed to do no writes to the block device; in fact we write straightaway when we replay the log on an ro mount. Other "OMG don't write!" leftovers linger, and cause issues as described in the following 2 patches. Dave suggested grand plans for coalescing more of this into common paths ala remount handling, i.e. a RO mount gets mounted RW and then just goes through the same transition to RO at the end, but I haven't put all that together yet, and these patches address a couple bugs in a more targeted fashion until that can happen. Dave also objected earlier to my 2nd patch which allows orphan recovery to proceed on an ro mount. There may be filesystems out there with fairly long orphan inode lists which have never been recovered due to this bug, and I guess the concern was that $SOMEHOW, processing them now would cause $PROBLEMS. I'm at a loss for how to address these concerns; I tried to come up with a way to craft such a filesystem for a regression test, but failed. Once the flaw has been fixed in the kernel, I don't know how to recreate the situation at will for testing. Christoph was concerned about the xfstest which demonstrates this flaw still failing, so resending these patches to see if we can make some progress. Thanks, -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
