From: Andrei Borzenkov <arvidjaar@gmail.com>
To: "Senén Vidal Blanco" <senenvidal@sgisoft.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Storage and snapshots as historical yearly
Date: Tue, 12 Sep 2017 06:34:15 +0300 [thread overview]
Message-ID: <aebb8966-ca9b-7008-d329-3e60989a5c01@gmail.com> (raw)
In-Reply-To: <9208764.SjP1vfhOIA@pcsenen>
[-- Attachment #1.1: Type: text/plain, Size: 843 bytes --]
11.09.2017 21:17, Senén Vidal Blanco пишет:
> I am trying to implement a system that stores the data in a unit (A) with
> BTRFS format that is untouchable and that future files and folders created or
> modified are stored in another physical unit (B) with BTRFS format.
> Each year the new files will be moved to store A and start over.
>
> The idea is that a duplicate of disk A can be made to keep it in a safe place
> and that the files stored there can not be modified until the mixture of (A) and
> (B) is made.
>
This can probably be achieved using seed device. Mark original device as
seed and all changes will go to another writable device, similar to
overlay; then remove seed bit from original device, "btrfs device remove
writable" device and it should relocate its content back. Rinse and repeat.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-09-12 3:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 18:17 Storage and snapshots as historical yearly Senén Vidal Blanco
2017-09-11 18:49 ` Austin S. Hemmelgarn
2017-09-11 21:36 ` Pete
2017-09-12 12:16 ` Austin S. Hemmelgarn
2017-09-13 11:51 ` Pete
2017-09-13 12:26 ` Austin S. Hemmelgarn
2017-09-19 19:09 ` Senén Vidal Blanco
2017-09-12 3:34 ` Andrei Borzenkov [this message]
2017-09-19 11:49 ` Senén Vidal Blanco
2017-09-19 18:33 ` Andrei Borzenkov
2017-09-19 19:19 ` Austin S. Hemmelgarn
2017-09-21 10:07 ` Senén Vidal Blanco
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=aebb8966-ca9b-7008-d329-3e60989a5c01@gmail.com \
--to=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=senenvidal@sgisoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).