amd64/123456: /usr/bin/fstat shows error messages and hang.
jhb at freebsd.org
Wed May 7 19:10:03 UTC 2008
The following reply was made to PR amd64/123456; it has been noted by GNATS.
From: John Baldwin <jhb at freebsd.org>
To: freebsd-amd64 at freebsd.org
Cc: KOIE Hidetaka <hide at koie.org>, freebsd-gnats-submit at freebsd.org
Subject: Re: amd64/123456: /usr/bin/fstat shows error messages and hang.
Date: Wed, 7 May 2008 14:29:27 -0400
On Tuesday 06 May 2008 06:53:42 am KOIE Hidetaka wrote:
> fstat -v shows error message like this:
> can't read vnode at 0x0 for pid ***
> can't read znode_phys at 0x**** for pid ***
> unknown file type 5 for file 5 of pid ***
> fstat / hangs.
> Patch for "can't read vnode at 0x0 for pid ***":
> vtrans() is invoked iff vp is not null.
> Patch for "can't read znode_phys at 0x**** for pid ***":
> znode_phys is void *, not int.
> Patch for "unknown file type 5 for file 5 of pid ***":
> consider other DTYPEs.
> Patch for hanging:
> sysctl "debug.sizeof.znode" returns int, not size_t.
I've applied all of the fixes except for the 3rd one. I think that each file
type should show up as unknown until support for it is added to fstat.
More information about the freebsd-amd64