On Mar 6, 9:55pm, Lars Kellogg-Stedman wrote:
> Subject: Re: More raid5 issues: Kernel panic running xfs_db (fwd)
> (I meant to cc this to the list.)
>
> On Wed, 7 Mar 2001, Nathan Scott wrote:
> ...
> > Perhaps the use of xfs_db/xfs_admin is a red herring - do
> > you see the panic while the filesystem is mounted?
>
> No,
OK, cool - thats an important data point, I think.
> the panic only occurs when running xfs_db (or, in fact, xfs_logprint,
> which makes me suspect other xfs command may exhibit the same problem).
> The panic only occurs when the raid5 volume is involved.
>
The only other thing I can think of that may be implicated
here is the BLKSETSIZE ioctl, which all of the xfs tools
will use to try and set the device blksize to 512 before
they get started. Other than that, its all reads/writes.
Martin, does this sound fishy to you? Any idea if the use
of this ioctl is the cause here?
> > Are you using Russell/Martin's md patch?
>
> Possibly. I'm using a patch Scott (Smyth) sent me, which I presume
> incorporates this work -- the patch fixed the problem with the raid5 resync
> process wedging when the volume was mounted.
>
cheers.
--
Nathan
|