Today, freezing an xfs filesystem will add a dummy log entry after it quiesces the filesystem, to trigger unlinked inode recovery on the next mount. This kind of sucks for readonly snapshots on readonly devices; one must then specify "-o ro,norecovery" or mount will fail, because the log appears dirty. This is very nonobvious. I propose improving the situation by moving unlinked inode recovery out of log replay; check for and process unlinked inodes on every mount, regardless of log dirtiness. This way we can create snapshots with clean logs. There may be some devils in the details here but it passes a quick sanity check, so let's see what reviewers think, and see what I've overlooked... 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
