xfs
[Top] [All Lists]

Re: SGI XFS on ppc

To: Thomas Graichen <graichen@xxxxxxxxxxxxx>, thomas.graichen@xxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx
Subject: Re: SGI XFS on ppc
From: "Nathan Scott" <nathans@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 1 Aug 2000 15:57:00 -0500
In-reply-to: Thomas Graichen <news-innominate.list.sgi.xfs@xxxxxxxxxxxxx> "Re: SGI XFS on ppc" (Aug 1, 3:45pm)
References: <geert@xxxxxxxxxxxxxx> <200007311629.LAA29846@xxxxxxxxxxxxxxxxxxxx> <news2mail-8m5nv9$6tj$1@xxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs-announce@xxxxxxxxxxx
hi,

On Aug 1,  3:45pm, Thomas Graichen wrote:
> Subject: Re: SGI XFS on ppc
> Steve Lord <lord@xxxxxxx> wrote:
> 
> > 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 
> > working
> > out what went wrong. I suspect some read of a block from disk did not wake
> > 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.
> 
> i tried it with the poor mans debugger - printk :-)
> 
> i put printk's all over xfs_mountfs_int (which i hope is the right
> point for the mounting stage) and to my confusion - non of them were
> printed out (the first one was before xfs_mount_common - maybe i
> should move it before the xfs_readsb) ... i'll try to look at this

Try linvfs_read_super - it calls the mount code you're looking
at via the VFSOPS_MOUNT macro.  It does a bunch of stuff before
getting into xfs_mountfs_int, like calling pagebuf_daemon_start
and doing the mount argument parsing, etc.

> a bit deeper - also i will try to find out how to use xmon (if that
> is possible on my machine)
> 

cheers.

-- 
Nathan

<Prev in Thread] Current Thread [Next in Thread>