On Tue, Apr 21, 2020 at 07:06:09PM -0700, Darrick J. Wong wrote: > From: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > > When we're sorting recovered log items ahead of recovering them and > encounter a log item of unknown type, actually print the type code when > we're rejecting the whole transaction to aid in debugging. > > Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > --- Reviewed-by: Brian Foster <bfoster@xxxxxxxxxx> > fs/xfs/xfs_log_recover.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > > diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c > index 11c3502b07b1..5f803083ddc3 100644 > --- a/fs/xfs/xfs_log_recover.c > +++ b/fs/xfs/xfs_log_recover.c > @@ -1887,8 +1887,8 @@ xlog_recover_reorder_trans( > break; > default: > xfs_warn(log->l_mp, > - "%s: unrecognized type of log operation", > - __func__); > + "%s: unrecognized type of log operation (%d)", > + __func__, ITEM_TYPE(item)); > ASSERT(0); > /* > * return the remaining items back to the transaction >
