| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Directory mtime update issue (kernel 2.6.25) |
| From: | Michael-John Turner <mj@xxxxxxxxxxxx> |
| Date: | Wed, 18 Jun 2008 20:10:45 +0100 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20080618163356.GA6330@xxxxxxxxxxxxx> |
| References: | <20080618144534.GC11301@xxxxxxxxxxxxxxxxxx> <20080618163356.GA6330@xxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (NetBSD aurora.pimp.org.za 4.0_STABLE sparc64) |
On Wed, Jun 18, 2008 at 12:33:56PM -0400, Christoph Hellwig wrote: > XFS does indeed updated the mtime too for the case when the source is > a directory and we get a new parent but just the ctime in all other > cases, which seems highly dubious to me. Thanks for the prompt reply and the patch. I'm surprised this hasn't been mentioned before as every other Unix filesystem I've used has not updated the moved file's mtime during a rename(2). It's also odd that XFS only changes the mtime when there's a new parent. What does everyone else think? Would it be possible to have this patch or a similar one committed upstream? -mj -- Michael-John Turner mj@xxxxxxxxxxxx <> http://mjturner.net/ |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: is the flush-on-close-after-truncate still needed?, Eric Sandeen |
|---|---|
| Next by Date: | Re: Directory mtime update issue (kernel 2.6.25), Michael-John Turner |
| Previous by Thread: | Re: Directory mtime update issue (kernel 2.6.25), Christoph Hellwig |
| Next by Thread: | Re: Directory mtime update issue (kernel 2.6.25), Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |