public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Sturmlechner <asturm@gentoo.org>
To: pr <pr@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] News Item v2: sys-fs/cryfs-0.10.2 update
Date: Sat, 26 Oct 2019 22:57:42 +0200	[thread overview]
Message-ID: <4711034.d950OIdMpC@tuxk10> (raw)
In-Reply-To: <2364611.2xGvymeTQd@tuxk10>

[-- Attachment #1: Type: text/plain, Size: 913 bytes --]

Title: sys-fs/cryfs-0.10.2 update 
Author: Andreas Sturmlechner <asturm@gentoo.org>
Content-Type: text/plain
Posted: 2019-10-26
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <sys-fs/cryfs-0.10

Filesystems created with CryFS 0.9.x are incompatible with the new storage 
format. [1] Migration is necessary before mounting with CryFS 0.10 and 
possible for old containers going back as far as CryFS 0.9.4. [2]

However, upstream recommend to create new containers with 0.10 to avoid 
potential data loss from a failed migration, and in order to benefit from all 
performance advantages of the new format.

Before updating, copy all data from cryfs containers to a temporary and secure
location. After the update, move it back into a newly created container. Don't 
forget to remove the temporary files afterwards.

[1] https://bugs.gentoo.org/690324
[2] https://github.com/cryfs/cryfs/releases/tag/0.10.1

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2019-10-26 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26 18:39 [gentoo-dev] [RFC] News Item: sys-fs/cryfs-0.10.2 update Andreas Sturmlechner
2019-10-26 20:57 ` Andreas Sturmlechner [this message]
2019-10-28  0:38   ` [gentoo-dev] Re: [RFC] News Item v3: " Andreas Sturmlechner
2019-10-28 10:54     ` Ulrich Mueller
2019-10-29  9:58       ` Andreas Sturmlechner
2019-10-29 15:01       ` [gentoo-dev] [RFC] News Item v2: Desktop profile switching USE default to elogind Andreas Sturmlechner

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=4711034.d950OIdMpC@tuxk10 \
    --to=asturm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=pr@gentoo.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