All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: atime not written to disk
Date: Tue, 21 Oct 2008 17:21:00 +1100	[thread overview]
Message-ID: <48FD74CC.907@sgi.com> (raw)

Hi,

Before I investigate further ;-),
it appears that in XFS (seen in recent xfs-dev tree and on older issp release
on default mkfs/mount options),
that the atime is not being written out to disk in xfs,
at least, in the simple scenario below.

emu:/home/tes # echo bill >/mnt/test/bill
emu:/home/tes # ls -l /mnt/test/bill
-rw-r--r-- 1 root root 5 2008-10-21 16:03 /mnt/test/bill
emu:/home/tes # ls -lu /mnt/test/bill
-rw-r--r-- 1 root root 5 2008-10-21 16:03 /mnt/test/bill

... wait a bit to change the atime...

emu:/home/tes # cat /mnt/test/bill
bill
emu:/home/tes # ls -lu /mnt/test/bill
-rw-r--r-- 1 root root 5 2008-10-21 16:11 /mnt/test/bill

emu:/home/tes # cd /
emu:/ # umount /mnt/test
emu:/ # mount /mnt/test
emu:/mnt/test # ls -lu /mnt/test/bill
-rw-r--r-- 1 root root 5 2008-10-21 16:03 /mnt/test/bill

I believe that the atime is handled by the vfs and in xfs_iflush_int
we sync up with the linux inode.
Perhaps i_update_core needs to be set so that xfs_iflush_int
will proceed and call xfs_synchronize_atime() and
somehow that is not happening??

I haven't looked further yet, but I thought I'd ask on the list
in case others, such as Christoph and Dave have thoughts on this.

Thanks,
Tim.

             reply	other threads:[~2008-10-21  6:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21  6:21 Timothy Shimmin [this message]
2008-10-21  6:49 ` atime not written to disk Utako Kusaka
2008-10-22  8:17   ` [PATCH, RFC] " Dave Chinner
2008-10-23  2:52     ` Niv Sardi
2008-10-23  2:53     ` Niv Sardi
2008-10-23  4:20       ` Dave Chinner
2008-10-24  5:37         ` Niv Sardi
2008-10-24  6:08           ` Dave Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48FD74CC.907@sgi.com \
    --to=tes@sgi.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.