From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Can't ream fs. Panic: config io
Date: Wed, 23 Jul 2008 12:46:00 -0400 [thread overview]
Message-ID: <5f95c8e1db924a29bb00b346994f9832@coraid.com> (raw)
In-Reply-To: <072320081630.5717.48875CB4000B6166000016552202888744050E0C040A90>
> config w0
> filsys main w0
> I don't have anything set up to capture output, but I hope I can give you enough here. It looks something like
>
> drive w0
> 35885393 blocks at 512 bytes each
> 2242834 logical blocks at 8192 bytes each
> 16 multiplier
> tag = 0/0; expected 0/10 not flushed
>
> stack trace of 2
> ...
> panic: config io
> cpu 0 halted
i don't think you can put your configuration in the
same place you put your fs.
i think the superblock's tag is getting written to the
configuration area.
you can use my fs tree from sources which supports
a cec console. you should be able to capture output
with it.
- erik
next parent reply other threads:[~2008-07-23 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <072320081630.5717.48875CB4000B6166000016552202888744050E0C040A90>
2008-07-23 16:46 ` erik quanstrom [this message]
2008-07-23 16:59 ` a
2008-07-23 16:30 g.pavelcak
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=5f95c8e1db924a29bb00b346994f9832@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@9fans.net \
/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).