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] Using cwfs
Date: Sun, 23 Aug 2009 23:27:41 -0400	[thread overview]
Message-ID: <a633dd307a37f09d92fb4fef59eb5999@quanstro.net> (raw)
In-Reply-To: <fe41879c0908231911n14848f1dnfb5b1eab45ab019a@mail.gmail.com>

On Sun Aug 23 22:12:54 EDT 2009, akumar@mail.nanosouffle.net wrote:
> ...: phase error -- cannot happen

i haven't ever seen this error.  i would expect
something like this

minooka; lc
ls: .: phase error -- directory entry not allocated

if you are simply left with a directory that's been
deleted.  maybe something else is going on?

> So, I found the files I lost in an older dump.
> Is there any way I can load them from the
> dump into the cache without having to copy
> them back?
>
> I know bind is an option, but something more
> permanent would be better in this case.

i don't know if i can answer your question as
it is without giving an answer that confuses
the issue.

a file can be on the worm, not in the cache
*and* in the active fs.  my version of the fs has the
option to not copy anything to the cache.  this is
generally a good idea as the cache and worm are generally
on similar disks these days.  the active fs is everything
accessable from the main fs without going through
the dump.  of course, if you ever delete or change
something, there are files accessable only through
the dump.

the cache is mostly orthoganal to this.  except
that between dumps, modifications are in the cache,
though they have actually worm addresses.  this is
why some blocks are usually lost on each dump.
since the maximum allocated address on the worm
is never adjusted down to account for deletions.

so the only way to move a file that only exists in
the dump to the active fs is to copy it.

- erik



  reply	other threads:[~2009-08-24  3:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-23  7:37 Akshat Kumar
2009-08-23 12:54 ` erik quanstrom
2009-08-23 13:07 ` Anthony Sorace
2009-08-23 20:05   ` Akshat Kumar
2009-08-24  1:45     ` Akshat Kumar
2009-08-24  2:11       ` Akshat Kumar
2009-08-24  3:27         ` erik quanstrom [this message]
2009-08-24  3:53           ` Akshat Kumar
2009-08-24 11:10             ` Mathieu L.
2009-08-25 20:55               ` erik quanstrom
2009-08-24 20:38             ` Akshat Kumar
2009-08-24 22:13               ` cinap_lenrek
2009-08-25 20:56             ` erik quanstrom
2009-08-27  1:24               ` Akshat Kumar
2009-08-27  3:29                 ` erik quanstrom
2009-08-27 14:09                   ` Francisco J Ballesteros
2009-08-27 14:16                     ` 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=a633dd307a37f09d92fb4fef59eb5999@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).