From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 4BB722898C for ; Thu, 4 Jul 2024 19:03:26 +0200 (CEST) Received: from gaff.inri.net ([168.235.71.243]) by 9front; Thu Jul 4 13:01:53 -0400 2024 Received: from [127.0.0.1] ([168.235.81.125]) by gaff; Thu Jul 4 13:01:53 -0400 2024 Date: Thu, 04 Jul 2024 13:01:51 -0400 From: Stanley Lieber To: 9front@9front.org In-Reply-To: <37b3be7b-57eb-4f87-854a-c1dba39359a4@sciops.net> References: <37b3be7b-57eb-4f87-854a-c1dba39359a4@sciops.net> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: encrypted element blockchain database cloud full-stack-oriented backend Subject: Re: [9front] Full cwfs fscache Reply-To: 9front@9front.org Precedence: bulk On July 4, 2024 5:14:45 AM EDT, qwx@sciops=2Enet wrote: >Jul 3, 2024 03:34:43 Dave MacFarlane : > >> I did something that filled up my fscache partition and it took me a co= uple of hours trying to figure out how to save my server=2E >> >> I think it might be worth adding something to the troubleshooting secti= on of the fqa like: >> >> "Q: I filled up my cwfs cache! >> A: You can restore your cache from the latest dump with the "recover" c= ommand=2E Boot from an iso and enter a shell with '!rc'=2E Run 'cwfs64x -c = -f $fscachepath' and in the cwfs configuration shell run >> =C2=A0=C2=A0 recover main >> =C2=A0=C2=A0 end >> " >> >> The wording/instructions could probably be cleaned up by someone who kn= ows it better than me, but the information is currently buried deep in fsco= nfig(8) which is not the first place you look and hard to access when your = filesystem won't mount=2E > >Hi, > >This is the simplest case, but it would make sense to add a section >about it in fqa9=2E=C2=A0 You also should do 'check rtmp' on the cwfs >console after recovery (see fs(8))=2E=C2=A0 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 >=C2=A0 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=2E > >Again, this only covers the simplest case=2E=C2=A0 I'll think about a nic= e >phrasing for the fqa unless there are any objections=2E > >Cheers, >qwx > sounds good, thanks=2E=20 sl