summaryrefslogtreecommitdiffstats
path: root/fs/jbd2
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2012-05-21 11:42:02 -0400
committerTheodore Ts'o <tytso@mit.edu>2012-05-21 11:42:02 -0400
commitf32aaf2d2b996b14e993da1c23f7ee22ea7333a3 (patch)
tree8ba6ce1e09319f0a62b69436aade6e06fe76c085 /fs/jbd2
parentb09de7fa5217bbcb4caf3d19bd5e94816947ff7a (diff)
downloadlinux-f32aaf2d2b996b14e993da1c23f7ee22ea7333a3.tar.gz
linux-f32aaf2d2b996b14e993da1c23f7ee22ea7333a3.tar.bz2
linux-f32aaf2d2b996b14e993da1c23f7ee22ea7333a3.zip
ext4: enable the 64-bit jbd2 feature based on the 64-bit ext4 feature
Previously we were only enabling the 64-bit jbd2 feature if the number of blocks in the file system was greater 2**32-1. The problem with this is that it makes it harder to test the 64-bit journal code paths with small file systems, since a small test file system would with the 64-bit ext4 feature enable would use a 64-bit file system on-disk data structures, but use a 32-bit journal. This would also cause problems when trying to do an online resize to grow the filesystem above the 2**32-1 boundary. Fortunately the patch to support online resize for 64-bit file systems hasn't been merged yet, so this problem hasn't arisen in practice. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/jbd2')
0 files changed, 0 insertions, 0 deletions