Posts: 1,445
skidoo
Joined: 09 Feb 2012
#1
My ongoing attempt to chase a live persistence bug (stranded files accumulate in the aufs..plnk directory)
has been hampered by lack of timestamps (due to the noatime mount directive) so I'm compelled to ask:

during dynamic root persistence, where aufs-live is a tmpfs ramdrive, is noatime even desirable/beneficial ?

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://serverfault.com/questions/644468/will-noatime-on-a-tmpfs-volume-improve-performance"
linktext was:"http://serverfault.com/questions/644468 ... erformance"
====================================

Perhaps the linked answer isn't an authoritative reference, but it states that in a ramdrive scenario, noatime probably provides no demonstrable benefit.
(Intuitively, that makes sense... unless we're talking about a 15yr-old PC with 100MHz RAM installed.)

With intent toward knowing"what(all) files have been written to disk during this live session", can I (dare I?) remount,
(er, bind remount or similar operation) /live/aufs-ram and omit the 'noatime' arg... or must that occur at the outset (would require a live-init edit) ?

Code: Select all

$ cat /{etc}/fstab
$ mount
$ findmnt
/dev/loop0 on /live/linux type squashfs (ro,relatime)
tmpfs on /live/aufs-ram type tmpfs (rw,noatime,size=1638400k)
/live/aufs on / type aufs (rw,noatime,si=bf80c71f)
tmpfs on /media type tmpfs (rw,noatime,size=10240k)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,noatime,size=206724k,mode=755)
tmpfs on /live type tmpfs (rw,noatime,size=10240k,mode=755)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=1031824k,nr_inodes=219323,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
/live/aufs on /live/aufs type aufs (rw,noatime,si=bf80c71f)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
pstore on /sys/fs/pstore type pstore (rw,relatime)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1282400k)
Having lastAccessed timestamps available would also be helpful toward testing during live session:
install a given package... launch...(config files etc are created) ...uninstall via"apt-get purge"
then check which files are left behind (and create a custom cleanup list).
(toward creating a customized cleanup list)
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#2
skidoo wrote:My ongoing attempt to chase a live persistence bug (stranded files accumulate in the aufs..plnk directory)
We have that fixed for the next release. We are mounting the aufs with the noplink mount option.