From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] hjfs type mismatch
Date: Thu, 31 Oct 2024 23:47:15 -0700 [thread overview]
Message-ID: <D50DA56F0CB2FD92A5F0C83ABD49141E@thinktankworkspaces.com> (raw)
In-Reply-To: <7D2855B4081B6EDC6968457EE6FDCB18@wopr.sciops.net>
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.
I have a linode server running fine for many years now but I can't seem to get something to run on AWS
as of late.
Are there maintenance things I should be running like some sort of dump commands for daily weekly thing or?
Quoth qwx@sciops.net:
> On Fri Nov 1 00:30:14 +0100 2024, william@thinktankworkspaces.com wrote:
> > I switched over from cwfs to hjfs. Twice I seem to crash on cwfs and couldn't figure out why.
>
> Crashing cwfs is not normal and something you're welcome to report,
> along with some debug information.
>
>
> > hjfs: type mismatch, dev /dev/sdC0/fs, block 138952, got raw, want dentry, caller 0x860d
> > ls: .: phase error -- type mismatch
> >
> >
> > Its like the user is dead/broken corrupt or something when I try to rcpu
> >
> > rcpu -h tmryk -u william
> > lost connection
> >
> > here is the log
> > tlssrv: tls reports can't exec /bin/rc: file does not exist: '/bin/rc'
> >
> > Thoughts?
>
> Your file system is corrupt.
>
> Which version of 9front and qemu are you using? What format is the
> virtual disk and how is it stored? How are you powering the VM down?
> Catastrophic failures with both filesystems seems suspicious.
>
> Cheers,
> qwx
>
next prev parent reply other threads:[~2024-11-01 6:48 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 [this message]
2024-11-01 13:03 ` qwx
2024-11-01 17:40 ` william
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=D50DA56F0CB2FD92A5F0C83ABD49141E@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).