Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Not-quite-a-newbie, here; I actually manage a number of Linux Boxes and I've been tasked with setting up a new server with an eye towards future expansion -- so my question is about filesystem limits. I ask here in this forum because it's one of those 'basic' questions that I never asked.
What is meant by 'filesystem', when we are informed that the maximum filesystem size under ext3 is 32TB, what is meant by 'filesystem'?
Does it mean:
Everything under / including mounted remote volumes?
Anything on one block device, no matter how it is partitioned?
Any named volume group?
Or does it mean something else?
The budget proposal for the archives' hardware depends on the answers!
Edited for Clarity:
Thanks for the replies, but I think I need to offer some clarification:
Of course wikipedia has a definition of 'filesystem' -- but it's too general. manpages sometimes refer to volumes as filesystems, sometimes to everything under root (/) -- it's not consistent, and therein lies my problem.
I think what I'm asking about is related to address-space.
Some references call anything mounted under / the 'filesystem'. Other references call anything mounted under / (such as /etc or /home or /tmp) different 'filesystems', and this is especially true when each one (/etc /home /tmp) is mounted on a different volume.
So, is it the individual volumes (/etc /home, /tmp ) that are limited to 32TB (The stated Maximum for an ext3 filesystem is 32TB), or is it the total aggregate size under / that is limited to 32TB?
What is the definition of filesystem -- I need the definition, not connotations or common assumptions about it.
Last edited by Fionnbharr; 01-10-2009 at 10:24 AM.
Reason: Clarification of Question
I am sure that wikipedia has a definition of "filesystem".
To me a filesystem is a set of bookeeping stuctures that are written to a disk partition which then allow you to read and write files with relatively user-friendly commands. The interface (driver) for these structures has to be in the operating system. It is analogous to telling a printer to print something---intermediate code (driver, firmware, etc.) gets you to the pulses that are sent to the ink jets.)
excerpt from file system;
(1) The method for storing and retrieving files on a disk.
It is system software that takes commands from the operating
system to read and write the disk clusters (groups of sectors).
The file system manages a folder/directory structure, which
provides an index to the files, and it defines the syntax used
to access them (how the "path" to the file is coded). File
systems dictate how files are named as well as the maximum size
of a file or volume.
There are numerous file systems in use; for example,
FAT32 and NTFS are Windows file systems, and HFS is used on
Macs. Linux uses ext2, ext3 and FAT32. Unix systems use UFS,
ext2, ext3 and ZFS. See cluster, path, FAT32, NTFS, HFS, NFS,
UFS, ext, ZFS and hierarchical file system.
(2) A data processing application that manages individual files.
It opens, closes, reads and writes the file as a single entity.
In a file system, files are related to each other by customized
programming (customers to orders, vendors to purchases, etc.).
Contrast with a "relational database," which has built-in
constructs that can more easily form these relationships. For
example, they can be used to join files together and split them
apart, all without tedious programming. See relational database
Ext3 has a max size between 2 and 16tb, depends on other factors- mainly block size.
The limit is volume size, due to the size set aside for addressing etc., so you could have 100 1tb drives mounted on a system thats on a 1gb hard drive and use it like that, There'd be no problem at all- each 1tb drive would not affect the 1gb drive in such a system.