From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] hjfs type mismatch
Date: Fri, 01 Nov 2024 10:40:22 -0700 [thread overview]
Message-ID: <2EAE56A49E96CD45AC9B9DED47A695A6@thinktankworkspaces.com> (raw)
In-Reply-To: <3E822A392EA79D0E0C912B6352985D5C@wopr.sciops.net>
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
>
next prev parent reply other threads:[~2024-11-01 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 23:30 william
2024-11-01 2:03 ` qwx
2024-11-01 6:47 ` william
2024-11-01 13:03 ` qwx
2024-11-01 17:40 ` william [this message]
2024-11-01 21:45 ` qwx
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=2EAE56A49E96CD45AC9B9DED47A695A6@thinktankworkspaces.com \
--to=william@thinktankworkspaces.com \
--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).