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 15:24:40 -0500 [thread overview]
Message-ID: <1eb60af701688ea28c07b2ca3ad595d0@quanstro.net> (raw)
In-Reply-To: <20060805202005.6F647A9C0@mail.cse.psu.edu>
i'd really be suprised if you had actually used up 50G. i think that
the problem is that copyworm trys to copy the whole worm --- even
empty blocks.
the relevant check in getbuf combined with written size seems to do
this:
static Devsize
writtensize()
{
Devsize lim;
for(lim = devsize(worm); lim > 0; lim--)
if(blocknum(lim) is "active" OR blocknum(lim) can be read)
return lim+1;
return 0;
}
am i missing something? it's not obvious to me how to determine the last
block that's actually got data in it.
- erik
On Sat Aug 5 15:22:54 CDT 2006, g.pavelcak@comcast.net wrote:
>
> Well, don't I feel silly. I thought I had stumbled upon a problem
> that required an fs wizard, but, unless Geoff says otherwise, I'm
> now convinced that I was just trying to get an elephant into a
> hamster cage. I'll just have to rethink my disk usage. Or maybe I'll
> try fossil/venti. Fs has been great, but the graph indicates that
> venti grows more slowly, and I don't want to give up my mirror for
> concatenation.
>
> Now, the question is, if I switch to venti, how do I do it without
> losing my history? Seems to me that I've seen posts saying something
> like "Nemo posted a script", but I've never found the script. But
> that's just a vague memory. I'll have to do some 9fans archive
> searching.
>
> Thanks.
>
> Greg
next prev parent reply other threads:[~2006-08-05 20:24 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 [this message]
2006-08-05 23:13 ` geoff
2006-08-05 23:21 ` geoff
2006-08-06 4:27 ` erik quanstrom
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=1eb60af701688ea28c07b2ca3ad595d0@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).