On Thu, 29 Aug 2024 19:02:22 +0800, Yang Erkun wrote:
> Any extending write for ext4 requires the inode to be placed on the
> orphan list before the actual write. In addition, the inode can be
> actually removed from the orphan list only after all writes are
> completed. Otherwise we'd leave allocated blocks beyond i_disksize if we
> could not copy all the data into allocated block and e2fsck would
> complain.
>
> [...]
Applied, thanks!
[1/1] ext4: dax: keep orphan list before truncate overflow allocated blocks
commit: 59efe53e380ee305ec11378233adb6aaebe1856c
Best regards,
--
Theodore Ts'o <tytso@xxxxxxx>
