Arch Linux

cedricmc

Member

From: Valencia, Spain

Registered: 2011-11-20

Posts: 62

fstab: defaults vs rw (and other explicit defaults)

Hi there,

I've been wandering across the populated forum and the insightful wiki, and I've come to wonder on the subject's title. I've seen that many people and wiki examples show as mounting options (in /etc/fstab) explicit default options, in particular rw,noatime,data=ordered. The first option, rw, is already included in the option set defaults, which also include suid,dev,exec,auto,nouser,async. The second, noatime, is a common non-default option to improve SSD's performance and live. The third, data=ordered is a default option, not included in defaults, that also improves SSD's performance. So my question would be, why to explicitly set default options like rw and data=ordered? The only reason I see is to know specifically what options will be used at boot mount, but then, why not to include all the other default options? Am I missing something?

Cheers,
me, I and myself

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: fstab: defaults vs rw (and other explicit defaults)

The reason you see those so frequently is probably because most people are using genfstab:

$ mkfs.ext4 /dev/sdf1
$ mount /dev/sdf1 /mnt/test
$ genfstab /mnt/test
# UUID=8c9d1161-ef58-4fd2-a335-b2d5a6977610
/dev/sdf1           	/         	ext4      	rw,relatime,data=ordered	0 1

Last edited by alphaniner (2015-03-30 18:23:31)

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner