From: pg-9Cpm1x5jwYpury8xqvH7Ik8g8846gVy9@public.gmane.org (Peter Grandi)
To: Linux fs NILFS <linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: changing CP's create time
Date: Thu, 28 Dec 2017 15:12:12 +0000 [thread overview]
Message-ID: <23109.2508.875917.216412@tree.ty.sabi.co.uk> (raw)
In-Reply-To: <20171228120336.2b53a10c@babalu>
> But when I rsync the data do another nilfs2 partition,
> snapshot by snapshot,
Are you using something like '--compare-dest' or '--link-dest'?
> each "cp_create" is stamped with today's date.
RSYNC is a POSIX command, checkpoints are not part of POSIX.
> Since I have a script that deletes all CP's older than 60
> days, it will be a problem to guess what do delete as all CP's
> will have almost the same timestamp. I probably doing it the
> wrong way [ ... ]
Perhaps some meditation on the difference between checkpoints
and snapshots, and the role of checkpoints in NILFS2, might be
of benefit here. Including the realization that you can turn
checkpoints into snapshots *on the target*.
Hint: NILFS2 checkpoints/snapshots are not quite the same as
"checkins" in a version control system or Btrfs snapshots.
> So I decided to thought changing the cp_create values back in
> time to resemble the original time of creation and hence the
> first question.
That could be done by adding some new 'ioctl' and modifying
'rsync' too, but looks messy to me, because checkpoints on the
source and checkpoints on the destination need not happen at the
same intervals, and checkpointing is "automatic" so far.
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-12-28 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 14:03 changing CP's create time Ethy H. Brito
2017-12-28 15:12 ` Peter Grandi [this message]
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=23109.2508.875917.216412@tree.ty.sabi.co.uk \
--to=pg-9cpm1x5jwypury8xqvh7ik8g8846gvy9@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox