| To: | Brian Foster <bfoster@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] xfsrestore: use utimensat() to provide atime/mtime with ns resolution |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Fri, 5 Sep 2014 10:45:01 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1409848708-42666-1-git-send-email-bfoster@xxxxxxxxxx> |
| References: | <1409848708-42666-1-git-send-email-bfoster@xxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Thu, Sep 04, 2014 at 12:38:28PM -0400, Brian Foster wrote: > xfsdump encodes and stores the full atime and mtime for each file with > nanosecond resolution. xfsrestore uses utime() to set the times of each > file that is restored. The latter supports resolution of 1 second, thus > sub-second timestamp data is lost on restore. That doesn't seem like a big deal. What sort of problems does this actually cause? FYI, many linux filesystems only have second resolution timestamps and hence applications can't rely on sub-second timestamp resolution to actually mean anything useful.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Ghost items in the end of a dir listing, Dave Chinner |
|---|---|
| Next by Date: | Re: [PATCH] xfsrestore: use utimensat() to provide atime/mtime with ns resolution, Eric Sandeen |
| Previous by Thread: | Re: [PATCH] xfsrestore: use utimensat() to provide atime/mtime with ns resolution, Brian Foster |
| Next by Thread: | Re: [PATCH] xfsrestore: use utimensat() to provide atime/mtime with ns resolution, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |