From: "Dave MacFarlane" <driusan@driusan.net>
To: 9front@9front.org
Subject: Re: [9front] Full cwfs fscache
Date: Thu, 04 Jul 2024 09:15:13 -0400 [thread overview]
Message-ID: <7B7FE2CD3B70BD08013B07FE0B772C39@driusan.net> (raw)
In-Reply-To: <37b3be7b-57eb-4f87-854a-c1dba39359a4@sciops.net>
Quoth qwx@sciops.net:
> Hi,
>
> This is the simplest case, but it would make sense to add a section
> about it in fqa9. You also should do 'check rtmp' on the cwfs
> console after recovery (see fs(8)). So, in case you fill up your
> cache or have an unclean shutdown or such, typically you would:
>
> - boot and append the -c flag to bootargs to enter config mode (instead
> of using the iso or entering the shell and starting cwfs manually)
> - enter 'recover main' and 'end'
> - run 'check rtmp' etc in the cwfs console once successfully booted.
>
> Again, this only covers the simplest case. I'll think about a nice
> phrasing for the fqa unless there are any objections.
>
> Cheers,
> qwx
>
That makes sense to me, like I said someone else could write a better
entry than me. I just wanted to include something in my message as a
starting point. I think the important part to me is that what to try
if a cwfs cache is filled is documented somewhere other than scattered
around man pages on the file system that won't mount and in various
developer's heads.
(I forgot to include it in the instructions but I did do a check rtmp
on my system.)
- Dave
next prev parent reply other threads:[~2024-07-04 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 0:58 Dave MacFarlane
2024-07-04 9:14 ` qwx
2024-07-04 13:15 ` Dave MacFarlane [this message]
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=7B7FE2CD3B70BD08013B07FE0B772C39@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).