Bug 6772
| Summary: | truncate() updates timestamps even if file size does not change | ||
|---|---|---|---|
| Product: | File System | Reporter: | Michael Kerrisk (michael.kerrisk) |
| Component: | XFS | Assignee: | XFS Guru (xfs-masters) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | normal | CC: | protasnb |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.17 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
Is the problem still there with the recent kernel? Thanks. This commit: http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs-2.6.git;a=commit;h=170c815e88c41859c9d79c9454c92dd9dd455bbe is in the XFS git tree that will be merged into 2.6.26. So it's fixed, just not yet in mainline. Verified present, closing |
Most recent kernel where this bug did not occur: unknown Distribution: SUSE 10.0 Hardware Environment: x86 Software Environment: Problem Description: POSIX requires that truncate() only change the ctime and mtime on the file if the file size actually changes (see "man 3p truncate"). On ext2 and ext3, this seems to work as required. However, ox XFS, truncate() changes the timestamps of the file even if the file size remains unchanged. This should not happen. Steps to reproduce: Something like the following can be used to test: ... int main(int argc, char *argv[]) { if (truncate(argv[1], atoi(argv[2])) == -1) perror("truncate") }