| 1 |
Nikos Chantziaras <realnc@×××××.de> posted gt7r28$cql$1@×××××××××.org, |
| 2 |
excerpted below, on Wed, 29 Apr 2009 00:05:33 +0300: |
| 3 |
|
| 4 |
> I have "defaults,noatime" and yet mount reports: |
| 5 |
> |
| 6 |
> /dev/root on / type ext4 (rw,noatime,barrier=1,data=ordered) |
| 7 |
> |
| 8 |
> Where does "rw,barrier=1,data=ordered" come from if not from "defaults"? |
| 9 |
|
| 10 |
Those (but for rw which is the normal default) are defaults of either |
| 11 |
the kernel or the filesystem itself, as set at mkfs time or with tune2fs. |
| 12 |
|
| 13 |
There's really quite a hierarchy of options and fall-thru defaults: |
| 14 |
|
| 15 |
Anything set on the mount commandline takes priority (well, after |
| 16 |
physical properties such as read-only for CDROM and floppies with write- |
| 17 |
protect set), |
| 18 |
|
| 19 |
followed by what's in fstab or the hal config, |
| 20 |
|
| 21 |
followed by options set for that particular filesystem at mkfs time or |
| 22 |
with the filesystem tuner (tun2fs, reiserfstune, whatever), |
| 23 |
|
| 24 |
followed by kernel defaults specific to that type of fs (ext3 defaulted |
| 25 |
to data=ordered but that's set to change to data=writeback in 2.6.30, |
| 26 |
after some fixes they've done but it's still rather controversial), |
| 27 |
|
| 28 |
followed by mount's normal defaults. |
| 29 |
|
| 30 |
-- |
| 31 |
Duncan - List replies preferred. No HTML msgs. |
| 32 |
"Every nonfree program has a lord, a master -- |
| 33 |
and if you use the program, he is your master." Richard Stallman |
Archives