From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Disk backup?
Date: Mon, 25 Mar 2013 09:43:08 -0400 [thread overview]
Message-ID: <65cc71e69757338cbdee9deafc395e11@brasstown.quanstro.net> (raw)
In-Reply-To: <bfc85197e580cf9736b3c4d063621dbf@rei2.9hal>
On Mon Mar 25 00:37:51 EDT 2013, cinap_lenrek@gmx.de wrote:
> i was thinking about this some time ago... theres the fakeworm
> device "f<subdevice>" that will maintain a block bitmap of
> the blocks that have already been written. one could write
> a program that also backups the block bitmap and on backup,
> compares the bitmaps prior copying blocks so only newly
> written blocks get backed up.
the fakeworm device causes more trouble than it's worth. and
there's no reason other than tradition to use it. if you simply
drop the "f" from an existing configuration that uses it, you'll
be free of the little nanny that will break things if you device
size changes by a little, say from running from a backup, or
you need to recover a botched dump.
it's much simplier just to do a bit copy and know that the same
configuration will run as long as the existing worm will fit.
- erik
next prev parent reply other threads:[~2013-03-25 13:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 22:10 trebol
2013-03-25 0:33 ` erik quanstrom
2013-03-25 2:04 ` trebol
2013-03-25 3:14 ` arisawa
2013-03-25 4:36 ` cinap_lenrek
2013-03-25 5:46 ` arisawa
2013-03-25 7:19 ` cinap_lenrek
2013-03-25 7:32 ` arisawa
2013-03-25 13:43 ` erik quanstrom [this message]
2013-03-25 15:03 ` erik quanstrom
2013-03-26 7:27 ` arisawa
2013-03-26 13:19 ` erik quanstrom
2013-03-26 18:34 ` cinap_lenrek
2013-03-26 18:56 ` erik quanstrom
2013-03-26 19:07 ` cinap_lenrek
2013-03-26 19:10 ` erik quanstrom
2013-03-26 19:15 ` erik quanstrom
2013-03-26 19:23 ` cinap_lenrek
2013-03-26 7:07 ` arisawa
2013-03-26 12:52 ` erik quanstrom
2013-03-26 23:22 ` trebol
2013-03-28 7:51 ` arisawa
2013-03-28 13:17 ` erik quanstrom
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=65cc71e69757338cbdee9deafc395e11@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).