Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 3
    The inode at top and bottom is 261889. If you mean why is the ctime value changed, then that is because the file's metadata changed - it's what ctime tracks. Commented Jun 21, 2015 at 10:56
  • 1
    I don't understand what it is that you don't understand. The change timestamp was updated because the file name was changed, but nothing else is changed. What did you expect? Commented Jun 21, 2015 at 10:58
  • The inode is the same (see the inode number). Everything is fine. You updated the file info (the name), which updated the "change" time. Commented Jun 21, 2015 at 12:00
  • 5
    Except OP poses a valid question why would inode's ctime be modified in this case. As was noted, at the end of the day the inode in question has not changed one bit. In fact POSIX ( pubs.opengroup.org/onlinepubs/009695399/functions/rename.html ) explicitly states that ctime update here is optional. So the question is why would linux do that. Commented Jun 21, 2015 at 13:02