Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Directory\s+mtime\s+update\s+issue\s+$kernel\s+2\.6\.25$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Directory\s+mtime\s+update\s+issue\s+$kernel\s+2\.6\.25$\s*$/: 15 ]

Total 15 documents matching your query.

1. Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Michael-John Turner <mj@xxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 15:45:34 +0100; 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 w; /archives/xfs/2008-06/msg00198.html (9,157 bytes)
2. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 12:33:56 -0400; Posix says about rename(2): Upon successful completion, rename() shall mark for update the st_ctime and st_mtime fields of the parent directory of each file. It doesn't mention anything about timesta; /archives/xfs/2008-06/msg00200.html (11,505 bytes)
3. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Michael-John Turner <mj@xxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 20:10:45 +0100; 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 als; /archives/xfs/2008-06/msg00205.html (8,648 bytes)
4. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Michael-John Turner <mj@xxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 23:30:50 +0100; Just a quick update - the patch does the trick and changes the rename(2) behaviour to be what I expect. Now, when a directory is renamed, its mtime doesn't change, even if it has a new parent. -mj --; /archives/xfs/2008-06/msg00206.html (8,316 bytes)
5. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Thu, 19 Jun 2008 04:21:24 -0400; The patch also passes xfsqa, so it should be ready now.; /archives/xfs/2008-06/msg00218.html (8,643 bytes)
6. Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Michael-John Turner <mj@xxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 15:45:34 +0100; 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 w; /archives/xfs/2008-06/msg00658.html (9,157 bytes)
7. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 12:33:56 -0400; Posix says about rename(2): Upon successful completion, rename() shall mark for update the st_ctime and st_mtime fields of the parent directory of each file. It doesn't mention anything about timesta; /archives/xfs/2008-06/msg00660.html (11,505 bytes)
8. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Michael-John Turner <mj@xxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 20:10:45 +0100; 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 als; /archives/xfs/2008-06/msg00665.html (8,648 bytes)
9. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Michael-John Turner <mj@xxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 23:30:50 +0100; Just a quick update - the patch does the trick and changes the rename(2) behaviour to be what I expect. Now, when a directory is renamed, its mtime doesn't change, even if it has a new parent. -mj --; /archives/xfs/2008-06/msg00666.html (8,316 bytes)
10. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Thu, 19 Jun 2008 04:21:24 -0400; The patch also passes xfsqa, so it should be ready now.; /archives/xfs/2008-06/msg00678.html (8,643 bytes)
11. Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Michael-John Turner <mj@xxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 15:45:34 +0100; 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 w; /archives/xfs/2008-06/msg01118.html (9,172 bytes)
12. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 12:33:56 -0400; Posix says about rename(2): Upon successful completion, rename() shall mark for update the st_ctime and st_mtime fields of the parent directory of each file. It doesn't mention anything about timesta; /archives/xfs/2008-06/msg01120.html (11,565 bytes)
13. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Michael-John Turner <mj@xxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 20:10:45 +0100; 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 als; /archives/xfs/2008-06/msg01125.html (8,751 bytes)
14. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Michael-John Turner <mj@xxxxxxxxxxxx>; Date: Wed, 18 Jun 2008 23:30:50 +0100; Just a quick update - the patch does the trick and changes the rename(2) behaviour to be what I expect. Now, when a directory is renamed, its mtime doesn't change, even if it has a new parent. -mj --; /archives/xfs/2008-06/msg01126.html (8,419 bytes)
15. Re: Directory mtime update issue (kernel 2.6.25) (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Thu, 19 Jun 2008 04:21:24 -0400; The patch also passes xfsqa, so it should be ready now.; /archives/xfs/2008-06/msg01138.html (8,762 bytes)

Current List: 1 - 15
Page: [1]