On Thu, Mar 15, 2012 at 22:23, Bruno Silva <bs@xxxxxxxxxxx> wrote:
<snip>
> 1 17.4kB 53.7GB 53.7GB ext3 1 msftres
> I have tested with ext4 file system, create ext4 file system with
> 4K block size.
>
> # mkfs.ext4 -b 4096 /dev/sdb1
> -----------------------------------------------------------------
i suspect you might encounter some issues with ext4, once you get past
the initial setup problems.
> The steps 1, 2 and 3 i did to all machines (data servers, metadata
> server and client).
assuming iSCSI as the underlying storage model, generally speaking:
* blkmapd and blocklayoutdriver are client-specific (as jim mentioned).
* ctl daemon is MDS-specific.
* iSCSI target is DS-specific.
* both MDS and client will need iSCSI initiator.
you'll need to discover and login to the iSCSI target on the DS from
both the MDS and the client for proper pNFS operation.
security often gets in the way, mind the ACLs on the iSCSI targets and
firewall settings on all three (client/MDS/DS) and between them.
> I adopted the export option in metadata server exports file.
> /mnt *(rw,sync,fsid=0,insecure,no_subtree_check,no_root_squash,pnfs)
<snip>
> If the data server and metadata server have been run on the same
> machine everything works normally.
see above. once you set everything up make sure you're actually running
in pNFS mode, i.e. that client sends/receives file data directly from
the DS over iSCSI, not as a fallback through MDS.
solo.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
