Did you actually run xfs_repair without -n and with -L? All the examples of the xfs_repair output you gave earlier indicated that -n had been used so no changes were being made.
The xfs_repair is normally very fast - just a few minutes. Despite the ominous sounding warning about the -L option it virtually never causes data loss, and in the rare cases where it does it only affects the last file being written.