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 66A4730778 for ; Fri, 1 Nov 2024 18:43:24 +0100 (CET) Received: from maat.thinktankworkspaces.com ([45.79.94.76]) by 9front; Fri Nov 1 13:40:25 -0400 2024 Message-ID: <2EAE56A49E96CD45AC9B9DED47A695A6@thinktankworkspaces.com> To: 9front@9front.org Date: Fri, 01 Nov 2024 10:40:22 -0700 From: william@thinktankworkspaces.com In-Reply-To: <3E822A392EA79D0E0C912B6352985D5C@wopr.sciops.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: proven social CMS standard Subject: Re: [9front] hjfs type mismatch Reply-To: 9front@9front.org Precedence: bulk Does it matter which image I use? I can use both regardless of architecture and I often do although I do notice a performance issue if it doesn't match the host OS. Quoth qwx@sciops.net: > On Fri Nov 1 07:47:27 +0100 2024, william@thinktankworkspaces.com wrote: > > 9front-10522.386.iso > > its qcow2 or I installed it on an AWS ec2. i run qemu with tmux. I never power it off and it ran fine for about two weeks. No heavy usage. Just serves a single page. I copied the image back over to my system > > to do further debugging and I just don't understand how or why. > > You're using the 386 image, not the amd64 one? I don't know much > about AWS or running VMs under it; there were bugs leading to file > corruption on 9front a while ago, but nothing I've heard of recently. > > > > Are there maintenance things I should be running like some sort of dump commands for daily weekly thing or? > > No. If there is nothing else to go on, I'd blame the qemu on aws setup > causing some issue. Check which image you're running and how. > > Hope this helps, > qwx >