Re: [PATCH V3] xfs: do not log/recover swapext extent owner changes for deleted inodes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 3/29/18 8:19 AM, Brian Foster wrote:
> On Wed, Mar 28, 2018 at 05:12:44PM -0500, Eric Sandeen wrote:
>> 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 uncleanly unmount root, as is its wont
>>     to do ...
> 
> Eh? :P

Obviously I meant to say "doesn't not uncleanly unmount" ... o_O
--
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



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux