From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Disk backup?
Date: Tue, 26 Mar 2013 16:27:18 +0900 [thread overview]
Message-ID: <6B8ECD0A-BB34-415E-A4BE-33FD27A03D30@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <23765573d3a25fe7c40809294c25090b@brasstown.quanstro.net>
Hello erik,
look free block list in superblocks, and observe their changes.
then you will find some of these free blocks are consumed for new file contents.
if not, your system and mine is different.
On 2013/03/26, at 0:03, erik quanstrom <quanstro@quanstro.net> wrote:
>> it is better to have efficient backup tool. (but not exists yet though)
>> cwfs is not so easy to backup compared to venti.
>> venti is easy to backup because filled areas are shielded and guaranteed not to be modified.
>> but cwfs is not. unwritten blocks exist in deep dumped area.
>> these blocks might be written in future.
>
> untrue. these unwritten blocks are never used. the dump
> consists of only blocks with a waddr greater than the last
> superblock's waddr. /sys/src/fs/dev/cw.c:/^dumpblock is a good
> reference.
>
> - erik
>
next prev parent reply other threads:[~2013-03-26 7:27 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
2013-03-25 15:03 ` erik quanstrom
2013-03-26 7:27 ` arisawa [this message]
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=6B8ECD0A-BB34-415E-A4BE-33FD27A03D30@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--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).