Since shared_vn always has to be zero, zero it at the start of repair.
Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx>
---
v2: reset shared_vn in phase 1 and tell the user about it, per sandeen
v3: more suggestions by sandeen to make the new code more consistent
---
repair/phase1.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/repair/phase1.c b/repair/phase1.c
index 126d0b3..9799883 100644
--- a/repair/phase1.c
+++ b/repair/phase1.c
@@ -138,6 +138,13 @@ _("Cannot disable lazy-counters on V5 fs\n"));
}
}
+ /* shared_vn should be zero */
+ if (sb->sb_shared_vn) {
+ do_warn(_("resetting shared_vn to zero\n"));
+ sb->sb_shared_vn = 0;
+ primary_sb_modified = 1;
+ }
+
if (primary_sb_modified) {
if (!no_modify) {
do_warn(_("writing modified primary superblock\n"));
--
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
