From: Dave MacFarlane <driusan@driusan.net>
To: 9front mailing list <9front@9front.org>
Subject: [9front] Full cwfs fscache
Date: Mon, 01 Jul 2024 20:58:31 -0400 [thread overview]
Message-ID: <A7EA8CDD-969C-4B78-ACE2-4538205F28B3@driusan.net> (raw)
I did something that filled up my fscache partition and it took me a couple of hours trying to figure out how to save my server.
I think it might be worth adding something to the troubleshooting section of the fqa like:
"Q: I filled up my cwfs cache!
A: You can restore your cache from the latest dump with the "recover" command. Boot from an iso and enter a shell with '!rc'. Run 'cwfs64x -c -f $fscachepath' and in the cwfs configuration shell run
recover main
end
"
The wording/instructions could probably be cleaned up by someone who knows it better than me, but the information is currently buried deep in fsconfig(8) which is not the first place you look and hard to access when your filesystem won't mount.
next reply other threads:[~2024-07-03 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 0:58 Dave MacFarlane [this message]
2024-07-04 9:14 ` qwx
2024-07-04 13:15 ` Dave MacFarlane
2024-07-04 17:01 ` Stanley Lieber
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=A7EA8CDD-969C-4B78-ACE2-4538205F28B3@driusan.net \
--to=driusan@driusan.net \
--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).