[PVFS2-users] A problem with the kernel module or pvfs2-client (v 1.1.0) on ppc

[Robert Latham]

On Mon, Oct 03, 2005 at 05:28:06PM -0400, Andrew Pochinsky wrote:
> In the system log I see the following messages 
> before pvfs2-client dies:
> 
> Oct  3 16:51:02 linux kernel: ioctl32(pvfs2-client-co:1471): Unknown 
> cmd fd(0) cmd(00000003){00} arg(100853c4) on /dev/pvfs2-req
> Oct  3 16:51:03 linux kernel: ioctl32(pvfs2-client-co:1483): Unknown 
> cmd fd(0) cmd(00000003){00} arg(100853c4) on /dev/pvfs2-req
> Oct  3 16:51:05 linux kernel: ioctl32(pvfs2-client-co:1485): Unknown 
> cmd fd(0) cmd(00000003){00} arg(100853c4) on /dev/pvfs2-req
> Oct  3 16:51:06 linux kernel: ioctl32(pvfs2-client-co:1496): Unknown 
> cmd fd(0) cmd(00000003){00} arg(100853c4) on /dev/pvfs2-req
> Oct  3 16:52:02 linux kernel: pvfs2_get_sb -- wait timed out (ec0001).  
> aborting attempt.
> Oct  3 16:52:02 linux kernel: pvfs2_get_sb: mount request failed with 
> 15466497
> 
> After that pvfs2-client dies, the kernel module remains loaded and 
> could removed without an apparent problem.
> 
> Does anybody have an idea what the problem might be?

in short, you are running a 64 bit kernel, but are trying to
communicate with it using a 32 bit application.   

Be sure to use the -m64 flag when both compiling (CFLAGS) and linking
(LDFLAGS).  We don't do any 32-to-64 bit conversions in the pvfs2
kernel module, so it's important you build pvfs2-client and
pvfs2-client-core as 64 bit apps when the kernel is 64 bits.

This link has a bit more information when someone was trying to build
pvfs2 on an IBM js20 (not very different from your machine):

http://www.beowulf-underground.org/pipermail/pvfs2-users/2005-April/000611.html

==rob

-- 
Rob Latham
Mathematics and Computer Science Division    A215 0178 EA2D B059 8CDF
Argonne National Labs, IL USA                B29D F333 664A 4280 315B