summaryrefslogtreecommitdiffstats
path: root/init
diff options
context:
space:
mode:
authorBartlomiej Zolnierkiewicz <bzolnier@gmail.com>2009-04-21 09:27:03 +0200
committerJens Axboe <jens.axboe@oracle.com>2009-04-28 07:37:33 +0200
commitdb29a6b49674085f136331014ba0eee249c16a2c (patch)
tree423676abaf2067b2d359a2439e00616812ee55f7 /init
parentide-dma: don't reset request fields on dma_timeout_retry() (diff)
downloadlinux-db29a6b49674085f136331014ba0eee249c16a2c.tar.xz
linux-db29a6b49674085f136331014ba0eee249c16a2c.zip
block: enable by default support for large devices and files on 32-bit archs
Enable by default support for large devices and files (CONFIG_LBD): - With 1TB disks being a commodity hardware it is quite easy to hit 2TB limitation while building RAIDs etc. and many distros have been using CONFIG_LBD=y by default already (at least Fedora 10 and openSUSE 11.1). - This should also prevent a subtle ext4 filesystem compatibility issue: mke2fs.ext4 defaults to creating filesystems with huge_files feature enabled and such filesystems cannot be later mounted read-write on machines with CONFIG_LBD=n (it should be quite easy to hit this issue when trying to use filesystem created using distro kernel on system running the self-build kernel, think about USB disk enclosures & co.). While at it: - Clarify config option help text w.r.t. mounting ext4 filesystems (they can be mounted with CONFIG_LBD=n but in the read-only mode). Cc: "Theodore Ts'o" <tytso@mit.edu> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions