| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [NEWBIE] Why aren't directory mtimes updated like other filesystems? |
| From: | "Kevin P. Fleming" <kpfleming@xxxxxxx> |
| Date: | Thu, 13 Mar 2003 14:10:05 -0700 |
| In-reply-to: | <1047589045.12814.2.camel@xxxxxxxxxxxxxxxxxxxx> |
| References: | <3E70E46A.20901@xxxxxxx> <1047586257.30836.58.camel@xxxxxxxxxxxxxxxxxxxx> <3E70ECD9.2080008@xxxxxxx> <1047589045.12814.2.camel@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030311 |
Steve Lord wrote: Strange, I try exactly the same commands and the ctime gets updated but the mtime does not. Are you running on 2.5?Ah, this is 2.4, I don't have a spare box for 2.5 here right now, but I know someone who does. The core xfs code is the same, and it is updating the timestamp fields in the inode. Possibly it is something in the stat path. Actually, it may be more insidious than that. When I did some testing over a 30 minute period, at one point making a new subdirectory caused the parent's mtime to update, but it updated to a time of about 10 minutes previous, when I had mad other changes. So it did change, but not to the current time. Very strange. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [NEWBIE] Why aren't directory mtimes updated like other filesystems?, Steve Lord |
|---|---|
| Next by Date: | Re: [NEWBIE] Why aren't directory mtimes updated like other filesystems?, Danny Cox |
| Previous by Thread: | Re: [NEWBIE] Why aren't directory mtimes updated like other filesystems?, Steve Lord |
| Next by Thread: | Re: [NEWBIE] Why aren't directory mtimes updated like other filesystems?, Danny Cox |
| Indexes: | [Date] [Thread] [Top] [All Lists] |