From: "Senén Vidal Blanco" <senenvidal@sgisoft.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Storage and snapshots as historical yearly
Date: Tue, 19 Sep 2017 13:49:40 +0200 [thread overview]
Message-ID: <2457840.3HpkerP4PG@pcsenen> (raw)
In-Reply-To: <aebb8966-ca9b-7008-d329-3e60989a5c01@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]
Perfect!! Just what I was looking for.
Sorry for the delay, because before doing so, I preferred to test to see if it
actually worked.
I have a doubt. The system works perfectly, but at the time of deleting the
writing disk and merging the data on the read-only disk I fail to understand
the process.
I have tried to remove the seed bit on disk A and delete the write B as you
mention, and so move the data to A, but tells me that disk B does not exist.
These are the orders I have made:
md127-> A
md126-> B
btrfstune -S 0 /dev /md127
mount /dev/md127 /mnt (I mount this disk since the md126 gives error)
btrfs device delete /dev/md126 /mnt
ERROR: error removing device '/dev/md126': No such file or directory
Another thing I've tried is to remove disk B without removing the seed bit,
but it gives me the error:
ERROR: error removing device '/dev/md126': unable to remove the only writeable
device.
Any ideas about it?
Thank you very much for the reply.
Greetings.
El martes, 12 de septiembre de 2017 6:34:15 (CEST) Andrei Borzenkov escribió:
> 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.
--
Senén Vidal Blanco - SGISoft S.L.
Tlf.: 986413322 - 660923711
GPG ID 466431A8AF01F99A
http://www.sgisoft.com/
--
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-09-19 11:49 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
2017-09-19 11:49 ` Senén Vidal Blanco [this message]
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=2457840.3HpkerP4PG@pcsenen \
--to=senenvidal@sgisoft.com \
--cc=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).