All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsrestore: use utimensat() to provide atime/mtime with ns resolution
Date: Fri, 5 Sep 2014 10:45:01 +1000	[thread overview]
Message-ID: <20140905004501.GU20518@dastard> (raw)
In-Reply-To: <1409848708-42666-1-git-send-email-bfoster@redhat.com>

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@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2014-09-05  0:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 16:38 [PATCH] xfsrestore: use utimensat() to provide atime/mtime with ns resolution Brian Foster
2014-09-04 19:47 ` Eric Sandeen
2014-09-04 21:35   ` Brian Foster
2014-09-05  0:45 ` Dave Chinner [this message]
2014-09-05  1:04   ` Eric Sandeen
2014-09-05  1:24     ` Dave Chinner
2014-09-05 11:02       ` Brian Foster
2014-09-05 11:19         ` Greg Freemyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140905004501.GU20518@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.