public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael-John Turner <mj@mjturner.net>
To: xfs@oss.sgi.com
Subject: Directory mtime update issue (kernel 2.6.25)
Date: Wed, 18 Jun 2008 15:45:34 +0100	[thread overview]
Message-ID: <20080618144534.GC11301@aurora.pimp.org.za> (raw)

Hi all,

I'm a recent convert to XFS and am experiencing something that I consider
rather odd. When I move a directory on the same filesystem, XFS updates the
directory's mtime, which is something I wouldn't expect to happen. I tested
the same set of commands on a tmpfs filesystem and the renamed directory's
mtime doesn't change. Similarly, when I move a file between directories on
an XFS filesystem, the file's mtime doesn't change (as expected).

Is this behaviour correct? I'm running Linux kernel 2.6.25.6 on an x86_64
system, filesystem mounted with the standard options (see below).

For example (~ and ~/tmp are the same filesystem, /home):

[0] mj@majestic:~/tmp$ mount |grep home
/dev/mapper/data-home on /home type xfs (rw)
[0] mj@majestic:~/tmp$ mkdir test
[0] mj@majestic:~/tmp$ ls -ld test
drwxr-sr-x 2 mj mj 6 Jun 18 15:28 test
[0] mj@majestic:~/tmp$ touch -t 200801011530 test
[0] mj@majestic:~/tmp$ ls -ld test
drwxr-sr-x 2 mj mj 6 Jan  1 15:30 test
[0] mj@majestic:~/tmp$ stat test
  File: `test'
  Size: 6               Blocks: 0          IO Block: 4096   directory
Device: fd00h/64768d    Inode: 951267331   Links: 2
Access: (2755/drwxr-sr-x)  Uid: ( 1000/      mj)   Gid: ( 1000/      mj)
Access: 2008-01-01 15:30:00.000000000 +0000
Modify: 2008-01-01 15:30:00.000000000 +0000
Change: 2008-06-18 15:29:08.173750666 +0100
[0] mj@majestic:~/tmp$ mv test test1
[0] mj@majestic:~/tmp$ ls -ld test1
drwxr-sr-x 2 mj mj 6 Jan  1 15:30 test1
[0] mj@majestic:~/tmp$ mv test1 ..
[0] mj@majestic:~/tmp$ ls -ld ../test1
drwxr-sr-x 2 mj mj 6 Jun 18 15:30 ../test1
  File: `../test1'
  Size: 6               Blocks: 0          IO Block: 4096   directory
Device: fd00h/64768d    Inode: 951267331   Links: 2
Access: (2755/drwxr-sr-x)  Uid: ( 1000/      mj)   Gid: ( 1000/      mj)
Access: 2008-01-01 15:30:00.000000000 +0000
Modify: 2008-06-18 15:30:02.814078187 +0100
Change: 2008-06-18 15:30:02.814078187 +0100

-mj
-- 
Michael-John Turner 
mj@mjturner.net      <>  http://mjturner.net/

             reply	other threads:[~2008-06-18 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 14:45 Michael-John Turner [this message]
2008-06-18 16:33 ` Directory mtime update issue (kernel 2.6.25) Christoph Hellwig
2008-06-18 19:10   ` Michael-John Turner
2008-06-19  8:21     ` Christoph Hellwig
2008-06-18 22:30   ` Michael-John Turner

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=20080618144534.GC11301@aurora.pimp.org.za \
    --to=mj@mjturner.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox