On Mon, Jun 22, 2020 at 10:14:36PM +0900, Wang Shilong wrote: > From: Wang Shilong <wshilong@xxxxxxx> > > Currently WAS_TRIMMED flag is not persistent, whenever filesystem was > remounted, fstrim need walk all block groups again, the problem with > this is FSTRIM could be slow on very large LUN SSD based filesystem. > > To avoid this kind of problem, we introduce a block group flag > EXT4_BG_WAS_TRIMMED, the side effect of this is we need introduce > extra one block group dirty write after trimming block group. > > And When clearing TRIMMED flag, block group will be journalled > anyway, so it won't introduce any overhead. This persistent flag will not be accurate if there are blocks that were freed in the block group in the same transaction, before EXT4_BG_WAS_TRIMMED flag is set. That's because we can't trim (or reuse) a block which has been released until the transaction has committed, since if we crash before it is commited, the file unlink or truncate will not have happened, and so we can't trash the block until after the deallocation has been freed. This problem is also there with a non-persistent flag, granted; but when the file system is unmounted and remounted, we will eventually trim the block via a fstrim. When we make the flag persistent, the problem becomes worse, since it might mean that there are some blocks that have been released, that might never get discarded. I suppose the question is whether the sysadmin really wants unused blocks to be discarded, either to not leak blocks in some kind of thin-provisioned storage device, or if the sysadmin is depending on the discard for some kind of security/privacy application (because they know that a particular storage device actually has reliable, secure discards), and how does that get balanced with sysadmins think performance of fstrim is more important, especially if the device is really slow at doing discard. - Ted
