Linux NILFS development
 help / color / mirror / Atom feed
From: "Ethy H. Brito" <ethy.brito-INItM/9t2qJfJ/NunPodnw@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: changing CP's create time
Date: Thu, 28 Dec 2017 12:03:36 -0200	[thread overview]
Message-ID: <20171228120336.2b53a10c@babalu> (raw)


Hi

What are the implications of changing the cp_create value for a bunch of
control points?

Motivation: I stumbled in this: 
NILFS: bad btree node (blocknr=115718887) ... 
and I decided to backup and recreate the partition since I could not find
any solution "googgling" for an answer.

(btw: any suggestions is really appreciated to solve this "bad btree" problem)

But when I rsync the data do another nilfs2 partition, snapshot by snapshot,
each "cp_create" is stamped with today's date.
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 but nothing clever came to my mind and I
must have this operation done by Tuesday morning when the folks returns to work.

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.

Again, any suggestions are welcome to save my you know what.

Regards

Ethy
--
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

             reply	other threads:[~2017-12-28 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28 14:03 Ethy H. Brito [this message]
2017-12-28 15:12 ` changing CP's create time Peter Grandi

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=20171228120336.2b53a10c@babalu \
    --to=ethy.brito-initm/9t2qjfj/nunpodnw@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