A couple of changes to how xfs behaves w.r.t. readonly mounts. 1) remove readonly checks from xfs_release and xfs_inactive paths 2) write unmount record even for RO mounts (which may have done recovery) 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 do that straightaway when we replay the log. 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. -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