Whamcloud - gitweb
LU-11882 e2fsck: zero date is not inode badness 13/34113/2
authorArtem Blagodarenko <c17828@cray.com>
Fri, 25 Jan 2019 16:35:24 +0000 (19:35 +0300)
committerAndreas Dilger <adilger@whamcloud.com>
Tue, 28 May 2019 06:25:30 +0000 (06:25 +0000)
commitc478288dddf485459115e14c57470c4466740e8d
tree0c0a179525f9cdc5361f20ecc31cdf1e88e4673f
parenta2afee7659260924ca4224dd4eaf41474570cedb
LU-11882 e2fsck: zero date is not inode badness

Lustre FS OST has some precreated objects which have zeroed
creation time. e2fsck adds badness points for such inodes.
If OST has many precreated objects, e2fsck spends too much time
during phase2, because processes each of such inode.

Let's allow Lustre FS inode has zeroed time field for
precreated objects.

Change-Id: I171a0fe741449ca99b29b5af51032a7b4c716344
Cray-bug-id: LUS-6857
Signed-off-by: Artem Blagodarenko <c17828@cray.com>
Reviewed-on: https://review.whamcloud.com/34113
Tested-by: Jenkins
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Reviewed-by: Li Dongyang <dongyangli@ddn.com>
Tested-by: Maloo <maloo@whamcloud.com>
e2fsck/pass1.c