Talk:fstab

Untitled

I'm not certain...but isn't their an option for defining a RAID level? 67.171.79.175 04:45, 1 August 2007 (UTC) sorry, wasn't signed in Mwv2 04:45, 1 August 2007 (UTC)[reply]

192.55.52.4 22:54, 5 November 2007 (UTC)Wouldn't it make sense to properly edit and not just wholesale copy/paste the contents of other websites into the page? I understand that tuxfiles.org is credited but:[reply]

There's no indication that the site contents are under the GFDL (and unless specifically stated, they're not and can't be used here)
The text still reads like it was written for a personal webpage: at bootup, just like I told you a bit earlier,

Do we really need to be THAT sloppy?

Also What about UUID inclusion Xubuntu / Ubuntu fstab files ? —Preceding unsigned comment added by 86.10.58.166 (talk) 21:17, 2 April 2008 (UTC)[reply]

fstab and UUID

I don't want to just jump in and do it, but shouldn't this article be rewritten to reflect the preference for UUID now present in the kernel? And it is a much better system as well. --DuLithgow (talk) 09:40, 22 August 2008 (UTC)[reply]

What is the connection between fstab and UUIDs?--85.176.232.250 (talk) 02:57, 14 August 2008 (UTC)[reply]

see https://help.ubuntu.com/community/UsingUUID

errors

could we document errors=remount-ro errors=continue ... etc as i cant find documentation anywhere —Preceding unsigned comment added by 77.99.150.12 (talk) 22:04, 28 February 2009 (UTC)[reply]

That option simply defines the behaviour of of the mount point if an error is encountered. In other words, errors=remount-ro tells the kernel to remount the partition as read only iff an error occurs. You can find all the documentation you need in the mount man page (or you can Google it). --Thorwald (talk) 23:17, 28 February 2009 (UTC)[reply]

new options

This article misses a recent option :

nodiratime

--Oliver.hessling (talk) 08:38, 16 May 2009 (UTC)[reply]

missing information

The file-system-specific entries that apply to vfat also apply to NTFS.

The options for setting the filesystem charset are also missing for vfat/ntfs:

nls=[charset] (NTFS) and iocharset=[charset] where charset is the charset used for the filesystem are also options for these two drive types.

For example, 'nls=utf8' would include the utf-8 charset for non-english speaking users.

Reference: http://www.linuxquestions.org/questions/linux-general-1/new-fstab-mount-option-guide-for-fixed-drives-suggestions-mistakes-547302/

fstab doesn't only mount filesystems

Although 'fstab' and 'mount' are typically used to mount filesystems, they are also capable of mounting hardlinks. For instance, using 'mount' it's possible to create a mountpoint that points to the same inode as a file|directory on the system.

An example of such usage would be 'mount --bind [directory|file] [mountpoint]' where [directory|file] is the inode being referenced and mountpoint is the mountpoint on the filesystem that points to that reference.

Note: this is the equivalent to creating a symlink (ln -s) that can't be deleted, not even by root. A mountpoint can only be removed by unmounting it.

The equivalent usage in fstab to the above example would be:

[directory|file] [mountpoint] none defaults,bind 0 0

or...

/examplepath1 /examplepath2 none defaults,bind 0 0

As you may notice, it works the same as any other mountpoint except the filesystem is set to none and it includes an additional bind option.

Reference: http://stateless.geek.nz/2005/10/26/bind-mount-in-fstab/

This is a great article but needs to be updated

This is a bit dated, i.e. no mention of btrfs which is the default of distributions like openSUSE. DrKC MD (talk) 20:53, 6 June 2023 (UTC)[reply]