From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] gefs: call for testing
Date: Mon, 18 Dec 2023 18:51:43 -0500 [thread overview]
Message-ID: <0140A39419537F79388C790BF276C185@eigenstate.org> (raw)
In-Reply-To: <93DC693B46ED09FB497F4B036E3212BA@eigenstate.org>
Quoth ori@eigenstate.org:
> Quoth ori@eigenstate.org:
> >
> > Second, I'm aware of old snapshots sometimes getting fucked;
> > finding and fixing that is my next thing. Hope to have some
> > updates on that front soon.
>
> Found the rather embarrassing bug that was causing old snapshots
> to get corrupted; we were freeing the tree when the refcount
> decreased, which is not necessarily when it went to 0.
>
Had it grind on building isos in a loop for about a day and
a half, with no problems. At this point, the TODO list is
down to:
commit blockers:
- atomics for all archs
- docs
important, after committing:
- repair tools
future features:
- non-adm controlled snapshots
- reclaiming data from deleted files is very delayed
- performance optimization:
- bulk block frees
- root block faster upsert
- small file optimizations
- inline data
The future features can all be added without breaking disk
format -- even tweaking block sizes should be doable, as
long as blocks stay below 64k.
prev parent reply other threads:[~2023-12-18 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 16:22 ori
2023-12-15 20:56 ` ori
2023-12-16 19:25 ` ori
2023-12-18 23:51 ` ori [this message]
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=0140A39419537F79388C790BF276C185@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/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).