diff options
| author | Eric Sandeen <sandeen@sandeen.net> | 2018-03-28 17:48:08 -0700 |
|---|---|---|
| committer | Darrick J. Wong <darrick.wong@oracle.com> | 2018-03-29 10:19:15 -0700 |
| commit | dc1baa715bbfbb1902da942d06497e79b40e7bc7 (patch) | |
| tree | b36dbcf78a250483195788279ae23f5c6a5a8bb7 /fs/btrfs/reada.c | |
| parent | 72c44e35f02a1cb4032e476c398a7234badcf49f (diff) | |
xfs: do not log/recover swapext extent owner changes for deleted inodes
Today if we run xfs_fsr and crash[1], log replay can fail because
the recovery code tries to instantiate the donor inode from
disk to replay the swapext, but it's been deleted and we get
verifier failures when we try to read the inode off disk with
i_mode == 0.
This fixes both sides: We don't log the swapext change if the
inode has been deleted, and we don't try to recover it either.
[1] or if systemd doesn't cleanly unmount root, as it is wont
to do ...
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Diffstat (limited to 'fs/btrfs/reada.c')
0 files changed, 0 insertions, 0 deletions