9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Disk backup?
Date: Tue, 26 Mar 2013 14:56:40 -0400	[thread overview]
Message-ID: <ffc25e981af674a1a19a514a3670743d@ladd.quanstro.net> (raw)
In-Reply-To: <86d7b1bda15f1dbeba599814a88c12dc@rei2.9hal>

> int
> cwfree(Device *dev, Off addr)
> {
> 	int state;
>
> 	if(dev->type == Devcw) {
> 		state = cwio(dev, addr, 0, Ofree);
> 		if(state != Cdirty)
> 			return 1;	/* do not put in freelist */
> 	}
> 	return 0;			/* put in freelist */
> }
>
> now, such a Cdirty block could just sit in the freelist for a while no?
> while the filesystem does many dump generations. if that Cdirty block
> becomes part of the filesystem again because it is allocated, then
> the next cwrecur() should pick it up and call split() on it.

why wouldn't it be marked for dump on the very
first dump?

- erik



  reply	other threads:[~2013-03-26 18:56 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
2013-03-26 13:19           ` erik quanstrom
2013-03-26 18:34             ` cinap_lenrek
2013-03-26 18:56               ` erik quanstrom [this message]
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=ffc25e981af674a1a19a514a3670743d@ladd.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).