From: Steve Lord <lord@sgi.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Thomas Graichen <graichen@innominate.de>,
thomas.graichen@innominate.de, linuxppc-dev@lists.linuxppc.org,
linux-xfs@oss.sgi.com
Subject: Re: SGI XFS on ppc
Date: Mon, 31 Jul 2000 11:29:36 -0500 [thread overview]
Message-ID: <200007311629.LAA29846@jen.americas.sgi.com> (raw)
In-Reply-To: Message from Geert Uytterhoeven <geert@linux-m68k.org> of "Mon, 31 Jul 2000 13:59:57 +0200." <Pine.LNX.4.10.10007311357070.442-100000@cassiopeia.home>
> On 31 Jul 2000, Thomas Graichen wrote:
> > * how to test the xfs filesystem without the tools? - i just made
> > a small 32mb xfs filesystem on an x86 and dd'ed to a file which
> > you can easily dd onto any partition and mount it as xfs fs there
> > (verified to work on x86)
> > * trying to mount the dd'ed filesystem just hangs the machine - no
> > output so far (xfs is compiled with debug and vnode tracing and
> > syslog will give *.* to the console) ...
> =
> Is XFS now always big endian (as we discussed about at Linux-Kongre=DF =
1999),
> or is it still native endian, so you cannot use an x86 image on big end=
ian
> machines?
> =
> Gr{oetje,eeting}s,
> =
> Geert
> =
XFS is now always bigendian - it should be possible to move a disk image
between systems. =
As for debugging this hang - it is a little tricky without something like=
kdb. Getting a stack trace for the mount process would be critical to wor=
king
out what went wrong. I suspect some read of a block from disk did not wak=
e
up the requesting thread. There is tracing in the pagebuf module, but it
relied on kdb to dump the results, mapping these trace calls onto printk
messages, or some other mechanism may help.
Steve
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-31 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-31 0:33 SGI XFS on ppc Thomas Graichen
2000-07-31 0:51 ` Keith Owens
2000-07-31 1:20 ` Dan Malek
2000-07-31 2:02 ` Keith Owens
2000-07-31 2:10 ` Dan Malek
2000-07-31 11:59 ` Geert Uytterhoeven
2000-07-31 16:29 ` Steve Lord [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-31 6:17 Thomas Graichen
[not found] <news2mail-8m35cd$3nu$2@mate.bln.innominate.de>
2000-07-31 6:34 ` Keith Owens
2000-07-31 6:48 ` Thomas Graichen
2000-07-31 8:02 ` Michel Dänzer
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=200007311629.LAA29846@jen.americas.sgi.com \
--to=lord@sgi.com \
--cc=geert@linux-m68k.org \
--cc=graichen@innominate.de \
--cc=linux-xfs@oss.sgi.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=thomas.graichen@innominate.de \
/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).