9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fs64 file server, partition boundaries out of range
Date: Sat,  5 Aug 2006 23:27:08 -0500	[thread overview]
Message-ID: <801d46846a08dbbcb038a6cfb7692f9e@quanstro.net> (raw)
In-Reply-To: <7dd00e3a7067afeaad6074b0a0bc64ec@plan9.bell-labs.com>

you're explination made perfect sense to me.  where is the bitmap consulted?

- erik

On Sat Aug  5 18:22:14 CDT 2006, geoff@plan9.bell-labs.com wrote:
> I didn't explain that as clearly as I could have: all blocks on the
> disk underlying a fake worm can be read from the disk device, but only
> already-written blocks can be read via the fake-worm device, and it's
> the fake worm's allocation bitmap that determines which blocks have
> been written.  This in turn emulates the real worm hardware, which
> only permits reading written blocks.
> 


  reply	other threads:[~2006-08-06  4:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-05 13:08 Gregory Pavelcak
2006-08-05 13:57 ` erik quanstrom
2006-08-05 18:14   ` Gregory Pavelcak
2006-08-05 19:32     ` Anthony Sorace
2006-08-05 20:19       ` Gregory Pavelcak
2006-08-05 20:24         ` erik quanstrom
2006-08-05 23:13           ` geoff
2006-08-05 23:21             ` geoff
2006-08-06  4:27               ` erik quanstrom [this message]
2006-08-05 23:34                 ` geoff
2006-08-06 15:06             ` Gregory Pavelcak
2006-08-07  1:06               ` geoff
2006-08-05 14:38 ` geoff
2006-08-05 18:11   ` Gregory Pavelcak
2006-08-07 21:19 Gregory Pavelcak
2006-08-07 21:29 ` geoff
2006-08-07 22:50   ` Gregory Pavelcak
2006-08-07 23:38     ` geoff
2006-08-10 12:44   ` Gregory Pavelcak

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=801d46846a08dbbcb038a6cfb7692f9e@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /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).