The 11th point here mentions noatime and nodiratime options as good for performance and power consumption.
So curious I looked into my /etc/fstab to see if those options are enabled and if not to put them in. However, since it says defaults under options I am not sure whether these options do or don't fall under these defaults.
The question then is, what options are the default options? Does this differ from distribution to distribution? If yes, I'm on Ubuntu Feisty.
Thanks
__________________












From
man mount:defaults
Use default options: rw, suid, dev, exec, auto, nouser,
and async.
Yn falch o ddefnyddio Linux a FLOSS!
Login or register to post comments 3 points
Ah I should have looked there.
Then it's safe to just add
noatimeandnodiratime.The options are the same regardless of the file system (ext3, reiserfs etc.) right?
Thanks
Let's not fear freedom.
Login or register to post comments 2 points
Those options increase performance, and can just be added. Be sure to note, however, that some tools might work worse with them; For example, I heard that mutt gets confused by noatime. (I have been using noatime for a while without noticing any problems... but they are not completely safe)
Thomas Jollans
GnuPG key: 1024D/A6B5 9461 B60F 2C80 2399 6B1E 2698 A70E F421 434B
Login or register to post comments -2 points
noatime is a superset of nodiratime, btw.
(seen here)
So if you have noatime, nodiratime is not necessary because it is implied by the first.
I also added data=writeback to my fstab, the "risk" of this is that you may end up with old data in a file in case of an OS crash or power failure. The filesystem won't be corrupted, though. Since I don't run any cron jobs or such that *need* to have their data in the right state, this is good enough for me.
CAN I HAS FIXD CAPSLOK KEE PLZ?
Login or register to post comments -2 points
I just added noatime to my fstab (couple of devices) and also made the decision to implement this in EasyLFS, for 0.4 already. It will be an option, but it'll default to on I think.
Login or register to post comments 2 points
Be sure to note, however, that some tools might work worse with them; For example, I heard that mutt gets confused by noatime.
I never use mutt. I suppose problems are very rare (which was also indicated in that article) so it should really be safe.
So if you have noatime, nodiratime is not necessary because it is implied by the first.
I see, thanks for pointing that out.
I also added data=writeback to my fstab, the "risk" of this is that you may end up with old data in a file in case of an OS crash or power failure.
You mean when you save something to a file and there is a crash, it may actually end up showing the old file (previous to the last save) once rebooted?
If it's something much more subtler than that I can live with it, but for now I think it'd be safest without that option.
I just added noatime to my fstab (couple of devices) and also made the decision to implement this in EasyLFS, for 0.4 already.
That sounds great.
Let's not fear freedom.
Login or register to post comments 0 points
I also added data=writeback to my fstab, the "risk" of this is that you may end up with old data in a file in case of an OS crash or power failure.
You mean when you save something to a file and there is a crash, it may actually end up showing the old file (previous to the last save) once rebooted?
Only when the crash happened while the OS was still busy writing the file to disk. How often does Linux crash anyway?
CAN I HAS FIXD CAPSLOK KEE PLZ?
Login or register to post comments 0 points
Ah I see, then it's quite safe. It never crashes really, and in exceptions to that rule the crash is related to a program which doesn't actually save important files, like games.
Let's not fear freedom.
Login or register to post comments 2 points
... and you shouldn't be playing games while editing important files anyway
CAN I HAS FIXD CAPSLOK KEE PLZ?
Login or register to post comments 0 points
Other options I use:
user_xattr,aclI think user_xattr is there for Git performance. acl is there because POSIX ACLs are a cool feature
Thomas Jollans
GnuPG key: 1024D/A6B5 9461 B60F 2C80 2399 6B1E 2698 A70E F421 434B
Login or register to post comments 0 points
What do those mean?
Actually, to be honest, I don't exactly know what noatime and data=writeback really mean either. I'm asking on behalf of anyone else reading this who may be wondering too.
Let's not fear freedom.
Login or register to post comments 2 points
Problems! Apparently the data=writeback thing causes some sort of an error on my ext3 root partition causing it to remount as readonly (as set in options). I removed that option now.
Let's not fear freedom.
Login or register to post comments 0 points
RTFM
(it's
man mount)noatime: don't store access times on disk (-> a read is a read and leaves the FS as it was)
user_xattr: allow users to use custom POSIX extended file attributes. Git uses this to store metadata in the file system and speed itself up.
acl: Enable the use of POSIX ACLs (access control lists), a way to specify more granula file permissions on UNIX systems
Thomas Jollans
GnuPG key: 1024D/A6B5 9461 B60F 2C80 2399 6B1E 2698 A70E F421 434B
Login or register to post comments -2 points
Actually I did read man mount exactly because I expected someone to suggest me to read the fine manual.
It's just that explanations there are quite minimal and susceptible to a bit of guesswork to those without deeper understanding of the context.
For user_xattr / nouser_xattr man says: "Support "user." extended attributes (or not)" Now that makes it so very immediately clear. Yeah right.
For noatime it says "Do not update inode access times on this file system (e.g, for faster access on the news spool to speed up news servers)." I guess that's a bit better, supposing you have any idea what an "inode" might be. Luckily I have only a vague idea.
Your response, however, was better than that.
Cheers
Let's not fear freedom.
Login or register to post comments 2 points
weird. I have reiserfs (can you tell I haven't installed the distro du jour for a while?), to be honest I don't know if the option actually does something on that fs...
CAN I HAS FIXD CAPSLOK KEE PLZ?
Login or register to post comments 2 points
I switched to noatime on both machines, my LFS-PC and my Fedora-notebook, both run ext3, both have survived the switch without any problems (so far). And for the notebook I can honestly say that now it's booting considerably faster; my PC already was booting pretty quick before, thanks to LFS (GUI-login after around 40 seconds; last time I stopped, which was still with my old hardware).
Login or register to post comments 2 points