From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Bad Karma with old kit
Date: Sat, 4 Jun 2005 15:26:18 -0700 [thread overview]
Message-ID: <3ceef387c19a6598d0e2767bed0c040a@collyer.net> (raw)
In-Reply-To: <62eb7aa995305986b9050a5bcaf00a5e@proxima.alt.za>
[Lucio, I tried to mail this to you privately, but keep getting
Sat Jun 4 15:16:22 PDT 2005 connect to tcp!proxima.alt.za:
550 5.0.0 Access denied ]
You can compile the 64-bit fs to be compatible on-disk with the 32-bit
fs by adding -DOLD to CFLAGS in the mkfile for that system. It might
be worth trying the newer code. The old IDE code was a little weak on
error checks.
Bad block size sounds like a good guess, but aren't you booting the
same fs kernel that you used to run on this machine? The block size
is compiled in, so I'm not sure how it could have changed.
I'm a little puzzled by the references in the devinit lines to D5 and
D14; those don't look like valid file server device strings, which is
worrisome. It looks like `D' is a `can't happen' condition, in Zfmt()
at /sys/src/fs/port/sub.c:602.
next prev parent reply other threads:[~2005-06-04 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 13:18 lucio
2005-06-04 22:26 ` geoff [this message]
2005-06-05 11:18 ` lucio
2005-06-05 21:49 ` geoff
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=3ceef387c19a6598d0e2767bed0c040a@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/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).