Before issuing the mount command, you must first install the kernel module
and start the client.  Have these steps been done?

Becky

On Tue, Dec 11, 2012 at 6:11 PM, Michael Robbert <[email protected]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I am setting up a new Orangefs system and am to the point of
> attempting to mount my first client. The command and error that I see is:
>
> mount -t pvfs2 tcp://virtual1.mio:3334 /mnt/orangefs
> mount: Protocol not available
>
> syslog is logging this:
>
> Dec 11 15:27:23 server03 kernel: pvfs2_get_sb: mount request failed
> with -92
>
> and with debugging set to verbose the client logs this:
>
> [D 15:27:23.589346] client_state_machine_terminate smcb 0x171451f0
> [D 15:27:23.589386] client_state_machine_terminate smcb 0x171451f0
> completing
> [D 15:27:23.589397] add smcb 0x171451f0 to completion list
> [D 15:27:23.589411] PINT_sys_release: id 10
> [D 15:27:23.589422] PINT_sys_testsome returned unexp vfs_request
> 0x17140ea0, tag: 101
> [D 15:27:23.589431] [+] dev req msg: sz: 8528,tag: 101,data:
> 0x172777d0,type: 0
> [D 15:27:23.589441] [*] handling new unexp vfs_request 0x17140ea0
> [D 15:27:23.589449] is_op_in_progress called on tag 101
> [D 15:27:23.589459] Got an fs mount request for host:
>   tcp://virtual1.mio:3334
> [D 15:27:23.589474] Using Mount Point <DYNAMIC-1>
> [D 15:27:23.589487] Got Configuration Server: tcp:/ (len=5)
> [D 15:27:23.589501] Got FS Name: virtual1.mio:3334 (len=17)
> [D 15:27:23.589523] activate_method: listen_addr=(null),
> active_method_count-1=0, flags=0
> [D 15:27:23.589536] BMI_tcp_initialize: Initializing TCP/IP module.
> [D 15:27:23.589558] BMI_tcp_initialize: TCP/IP module successfully
> initialized.
> [E 15:27:23.589573] PVFS_isys_fs_add: Failed to initialize any
> appropriate BMI methods for addresses:
> [E 15:27:23.589582]     tcp:/
> [E 15:27:23.589600] Posting fs_add failed: Protocol not available
> [E 15:27:23.589609] Post of op: PVFS2_VFS_OP_FS_MOUNT failed!
> [D 15:27:23.589618] PVFS2_VFS_OP_FS_MOUNT complete (vfs_request
> 0x17140ea0)
>         wtime = 0.000160, utime=0.000000, stime=0.000000 (seconds)
> [D 15:27:23.589639] write_device_response: writing device response.
> tag: 101
> [E 15:27:23.589658] Operation failed: (null)
> [D 15:27:23.589668] PINT_sys_release: id 10
> [D 15:27:23.589677] PINT_sys_dev_unexp
> [D 15:27:23.589687] client_op_state_get_machine 400
> [D 15:27:23.589697] PINT_client_state_machine_post smcb 0x171454a0,
> op: PVFS_DEV_UNEXPECTED
> [D 15:27:23.589706] Posted PVFS_DEV_UNEXPECTED (309) (waiting for
> test)(-1073741839)
> [D 15:27:23.589715] [-] reposted unexp req [0x17140ea0] due to failure
>
> I am running version 2.8.6 compiled locally. My initial client is on
> one of the server hosts and I've tried 2 different hosts with the same
> results. My setup is using Pacemaker for HA so I'm running virtual IPs
> for the servers. I'm probably missing something simple, but I can't
> seem to find it. Does anybody see anything in these logs or is there
> something else I should be looking at?
>
> Thanks,
> Mike Robbert
> Colorado School of Mines
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
>
> iQEcBAEBAgAGBQJQx72NAAoJEFmgPOBxQDtBQrwH/1FZjk2zMZkJiiDax2YSSs5U
> xz9MZpVBTtdFs0NyOIoz4XnUgFFeKA7ChpGxr9dz8Vekzy7gnH7VNsfjogfRX7r0
> MeeM/zu50PrQLmloOJuTM0612Z6fkwUn6bpGcUbt2DzVPpZJvEL7kSJ+bS9VCy59
> isuu2NKGVq9wp5ox++Yow6Z26SfYKO8+5JaAPrrihUAKWzOuKOQPiS+iY6XFQAAW
> W2ov6txuT08I/DfbTCzoXub6i9kFQ9ZLgTAyGd340L5xtdCr6osmkU6bStSA0cT8
> i/dFpgN7jM+INaSsEQaIESOr3tmR5uqOfQe0cKDDbOLOzqzVys4Bn0G7BWKlQcI=
> =l/+I
> -----END PGP SIGNATURE-----
> _______________________________________________
> Pvfs2-users mailing list
> [email protected]
> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
>



-- 
Becky Ligon
OrangeFS Support and Development
Omnibond Systems
Anderson, South Carolina
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users

Reply via email to