DebianThis forum is for the discussion of Debian Linux.
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.
In /etc there is a file mkfs something that defines the default options when mkfs.ext3 is called without parameter. Probably during install the same configuration file is used... hopefully.
I don't have access to my machine at the moment, I don't know exactly the name.
I would think tune2fs would be used to alter journal options on a existing file system.
For existing ones, I'm not sure anymore. Looking at the man page is not so clear.
I recall that -o remount can not do a lot of things so I guess you are right, tune2fs has to be used.
Set or clear the indicated default mount options in the filesystem. Default mount options can be overridden by mount
options specified either in /etc/fstab(5) or on the command line arguments to mount(8). Older kernels may not support
this feature; in particular, kernels which predate 2.4.20 will almost certainly ignore the default mount options field
in the superblock.
More than one mount option can be cleared or set by separating features with commas. Mount options prefixed with a
caret character (’^’) will be cleared in the filesystem’s superblock; mount options without a prefix character or pre‐
fixed with a plus character (’+’) will be added to the filesystem.
The following mount options can be set or cleared using tune2fs:
debug Enable debugging code for this filesystem.
Emulate BSD behaviour when creating new files: they will take the group-id of the directory in which they
were created. The standard System V behaviour is the default, where newly created files take on the fsgid
of the current process, unless the directory has the setgid bit set, in which case it takes the gid from the
parent directory, and also gets the setgid bit set if it is a directory itself.
Enable user-specified extended attributes.
acl Enable Posix Access Control Lists.
uid16 Disables 32-bit UIDs and GIDs. This is for interoperability with older kernels which only store and expect
When the filesystem is mounted with journalling enabled, all data (not just metadata) is committed into the
journal prior to being written into the main filesystem.
When the filesystem is mounted with journalling enabled, all data is forced directly out to the main file
system prior to its metadata being committed to the journal.
When the filesystem is mounted with journalling enabled, data may be written into the main filesystem after
its metadata has been committed to the journal. This may increase throughput, however, it may allow old
data to appear in files after a crash and journal recovery.
* The benefits of journalling and ReiserFS (Part 1)
* Setting up a ReiserFS system (Part 2)
* Using the tmpfs virtual memory filesystem and bind mounts (Part 3)
* The benefits of devfs, the device management filesystem (Part 4)
* Beginning the conversion to devfs (Part 5)
* Completing the conversion to devfs using an init wrapper (Part 6)
* The benefits of the ext3 filesystem (Part 7)
* An in-depth look at ext3 and the latest kernel updates (Part 8)
* The technology behind XFS (Part 9)