From: Andreas Baer <lnx1@gmx.net>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Large File Support in Kernel 2.6
Date: Thu, 08 Sep 2005 21:27:42 +0200 [thread overview]
Message-ID: <432090AE.2030200@gmx.net> (raw)
In-Reply-To: <43208B77.9060009@tmr.com>
I have a question about the Large File Support using Linux and glibc 2.3
on a 32-Bit machine. What's the correct limit for the file size and the
file system using LFS (just for the kernel, not to mention filesystem
limits etc)?
I found two references:
"The 2.6 kernel imposes its own limits on the size of files and file
systems handled by it. These are as follows:
- file size: On 32-bit systems, files may not exceed the size of 2 TB.
- file system size: File systems may be up to 2e73 bytes large. However,
this limit is still out of reach for the currently available hardware."
Source:
http://www.novell.com/documentation/suse91/suselinux-adminguide/html/apas04.html
"Kernel 2.6: For both 32-bit systems with option CONFIG_LBD set and for
64-bit systems: The size of a file system is limited to 2e73 (far too
much for today). On 32-bit systems (without CONFIG_LBD set) the size of
a file is limited to 2 TiB. Note that not all filesystems and hardware
drivers might handle such large filesystems."
Source: http://www.suse.de/~aj/linux_lfs.html
I think it's 2TB for the file size and 2e73 for the file system, but I
don't understand the second reference and the part about the CONIFG_LBD.
What is exactly the CONFIG_LBD option?
next prev parent reply other threads:[~2005-09-08 19:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4IcUz-7H2-27@gated-at.bofh.it>
[not found] ` <4J2gx-3zf-3@gated-at.bofh.it>
[not found] ` <4J5R1-cH-21@gated-at.bofh.it>
[not found] ` <4J6ao-L9-21@gated-at.bofh.it>
[not found] ` <4J6jZ-Xg-11@gated-at.bofh.it>
[not found] ` <4J8vt-43Y-13@gated-at.bofh.it>
2005-09-02 6:08 ` RFC: i386: kill !4KSTACKS Alex Davis
2005-09-04 12:49 ` Denis Vlasenko
2005-09-04 13:30 ` Ed Tomlinson
2005-09-04 14:49 ` Alan Cox
2005-09-04 16:44 ` Paul Misner
2005-09-04 17:07 ` Pekka Enberg
2005-09-04 17:12 ` Bas Westerbaan
2005-09-04 19:22 ` Horst von Brand
2005-09-04 19:33 ` Adrian Bunk
2005-09-04 20:13 ` Bas Westerbaan
2005-09-04 20:37 ` Dave Jones
2005-09-07 16:38 ` Bill Davidsen
2005-09-07 17:53 ` Mike Galbraith
2005-09-08 19:05 ` Bill Davidsen
2005-09-08 19:27 ` Andreas Baer [this message]
2005-09-08 20:16 ` Large File Support in Kernel 2.6 Mike Houston
2005-09-09 8:39 ` Andreas Baer
2005-09-05 22:32 ` RFC: i386: kill !4KSTACKS Thorild Selen
2005-09-05 23:06 ` Kyle Moffett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=432090AE.2030200@gmx.net \
--to=lnx1@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.