diff options
| author |   Lukas Czerner <lczerner@redhat.com> | 2013-03-12 12:40:04 -0400 |
|---|---|---|
| committer |   Theodore Ts'o <tytso@mit.edu> | 2013-03-12 12:40:04 -0400 |
| commit | 4f42f80a8f08d4c3f52c4267361241885d5dee3a (patch) | |
| tree | 7c41541fe7d89daef1e511d46b0853f85f70d589 /fs/ext4/move_extent.c | |
| parent | ext4: use atomic64_t for the per-flexbg free_clusters count (diff) | |
| download | linux-dev-4f42f80a8f08d4c3f52c4267361241885d5dee3a.tar.xz linux-dev-4f42f80a8f08d4c3f52c4267361241885d5dee3a.zip | |
ext4: use s_extent_max_zeroout_kb value as number of kb
Currently when converting extent to initialized, we have to decide
whether to zeroout part/all of the uninitialized extent in order to
avoid extent tree growing rapidly.
The decision is made by comparing the size of the extent with the
configurable value s_extent_max_zeroout_kb which is in kibibytes units.
However when converting it to number of blocks we currently use it as it
was in bytes. This is obviously bug and it will result in ext4 _never_
zeroout extents, but rather always split and convert parts to
initialized while leaving the rest uninitialized in default setting.
Fix this by using s_extent_max_zeroout_kb as kibibytes.
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@vger.kernel.org
Diffstat (limited to 'fs/ext4/move_extent.c')
0 files changed, 0 insertions, 0 deletions