From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] kfs and cwfs comparison
Date: Sun, 24 Apr 2011 14:03:18 -0400 [thread overview]
Message-ID: <9a3c8f55b55f706a76241eeb179eff34@ladd.quanstro.net> (raw)
In-Reply-To: <BANLkTinD8SFho4xG2EQuuCbZVQKH7JL3qA@mail.gmail.com>
On Sun Apr 24 13:37:08 EDT 2011, john@jfloren.net wrote:
> On Sun, Apr 24, 2011 at 9:10 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> > both have a weak spot.
> > kfs. there's one copy of the file system. if you corrupt it, you're out of
> > luck. i've never seen this happen.
> >
> > cwfs. if the fs is halted during the dump, there is a non-zero chance
> > of corruption. i have seen this, but "recover main" can usually roll the
> > fs back to the last good dump. the same mechanism can recover a fs
> > if an untimely shutdown has corrupted the cache.
> >
>
> The other day I managed to fill up a cwfs fscache, making it
> impossible to dump or boot the machine. Is it possible to recover from
> this state?
recover main should flush the cache, but that's probablly not what you want.
if you're not using the fast-cache option, just make the cache device bigger.
this is a bug and should be fixed or mitigated.
- erik
next prev parent reply other threads:[~2011-04-24 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 10:44 errno
2011-04-24 11:13 ` erik quanstrom
2011-04-24 11:31 ` errno
2011-04-24 14:10 ` David du Colombier
2011-04-24 15:52 ` erik quanstrom
2011-04-24 15:01 ` Steve Simon
2011-04-24 16:10 ` erik quanstrom
2011-04-24 17:36 ` John Floren
2011-04-24 18:03 ` erik quanstrom [this message]
2011-04-24 18:56 ` errno
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=9a3c8f55b55f706a76241eeb179eff34@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).