nautilus file copy doesn't preserve nanosecond timestamps
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nautilus |
Expired
|
Medium
|
|||
nautilus (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: nautilus
nautilus 1:2.30.1-0ubuntu1.1 in Ubuntu Lucid
When copying files in Nautilus, the low 3 decimal digits in the copy are set to zero. In other words, it only preserves 2-microsecond resolution.
Steps to reproduce:
1. Create a file (on a filesystem supporting nanosecond timestamps) and view its timestamp:
username@
username@
-rw-r--r-- 1 username username 0 2010-09-19 07:27:56.463178584 +0000 original-file
2. Copy file in Nautilus to the same or another filesystem, and view new file's timestamp
# original-file copied to file-nautilus
username@
-rw-r--r-- 1 username username 0 2010-09-19 07:27:56.463178000 +0000 file-nautilus
Expected result: New file has exactly the same timestamp. For example, cp --preserve=all works properly:
username@
username@
-rw-r--r-- 1 username username 0 2010-09-19 07:27:56.463178584 +0000 file-cp
Actual result: last 3 digits of copy are 000.
Changed in nautilus: | |
importance: | Unknown → Medium |
status: | Unknown → New |
tags: | removed: metadata nanosecond |
Changed in nautilus: | |
status: | New → Confirmed |
Changed in nautilus: | |
status: | Confirmed → Expired |
There was a similar bug in OpenSolaris: http:// bugs.opensolari s.org/bugdataba se/view_ bug.do? bug_id= 6539657
I have no idea whether the root cause is related, though.