| To: | Michael-John Turner <mj@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Directory mtime update issue (kernel 2.6.25) |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Thu, 19 Jun 2008 04:21:24 -0400 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <20080618191045.GA10722@aurora.pimp.org.za> |
| References: | <20080618144534.GC11301@aurora.pimp.org.za> <20080618163356.GA6330@infradead.org> <20080618191045.GA10722@aurora.pimp.org.za> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
On Wed, Jun 18, 2008 at 08:10:45PM +0100, Michael-John Turner wrote: > 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? The patch also passes xfsqa, so it should be ready now. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Prevent extent btree block allocation failures, Lachlan McIlroy |
|---|---|
| Next by Date: | Re: XFS: 2.6.26-rc6 link count mismatch for inode, Marco Berizzi |
| Previous by Thread: | Re: Directory mtime update issue (kernel 2.6.25), Michael-John Turner |
| Next by Thread: | Re: Directory mtime update issue (kernel 2.6.25), Michael-John Turner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |