Sponsored Content
Operating Systems AIX Questions about setting up GPFS Post 302733131 by bstring on Monday 19th of November 2012 09:42:32 PM
Old 11-19-2012
Questions about setting up GPFS

Hello, I need to test whether our product will work with GPFS filesystems and I have some questions regarding the setup:

1. Do I need to dedicate an entire hard disk if I want to have GPFS on it? Or can I somehow split a disk into 2 virtual disks, and only use 1 for gpfs?
2. If lspv returns "none" that means the disk is connected but has not been allocated, and thus available for use in GPFS setup?
Example (hdisk3):
Code:
[root@aix01: /]# lspv
hdisk0          00ca0c3546524b4e                    rootvg          active
hdisk1          00ca0c35797dab06                    vg1             active
hdisk2          00ca0c35797daba9                    vg1             active
hdisk3          none                                None
hdisk4          00ca0c35645c51bf                    san1            active
hdisk5          00ca0c3564646ef3                    san2            active

3. Do I have to have a second node in order to create a cluster and create a gpfs on that cluster? Or can I start with one node (just to test functionality) and add a second node later? (basically, can I use that one system above with hdisk3 available to test gpfs on its own?)

Thanks in advance
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Setting com port questions

I have a piece of equipment, a Baytech RPC-3, that I need to communicate with through the com port. I normally use this equipment at home and am able to connect to it without problems using FC5 and minicom; I brought the equipment into work and cannot get my pc, using Suse 10 and minicom to... (0 Replies)
Discussion started by: thumper
0 Replies

2. AIX

two gpfs in one node issue

dear all can i create two gpfs in one node each gpfs is pointing to single hdiskpower (1 Reply)
Discussion started by: thecobra151
1 Replies

3. AIX

SSD with GPFS ?

Hi, does anyone here happen to know if I could run GLVM or GPFS on Solid State Disks? I have a high volume / high transaction Sybase HACMP cluster currently setup with SRDF to the DR datacentre. My business now considers to move everything to SSD storage but we still need to get the data to... (0 Replies)
Discussion started by: zxmaus
0 Replies

4. AIX

AIX GPFS Setup

:cool:Hello, can someone guide me how to create a GPFS filesystem, I've read a couple of redbooks however certain things are still not certain, like if you require to download files or licenses... any help would be appreciated! (2 Replies)
Discussion started by: ollie01
2 Replies

5. AIX

How to configure new hdisk such that it has a gpfs fs on it and is added to a running gpfs cluster?

Hi, I have a running GPFS cluster. For one every mountpoint that i have created i have one disk assigned to it. That disk is converted to an NSD and is a part of the GPFS Cluster. Now i have a new disk and there is this requirement to add it to the GPFS cluster, such that this becomes an NSD.... (1 Reply)
Discussion started by: aixromeo
1 Replies

6. AIX

GPFS

Hello I am interested if anybody uses GPFS and is it must to have GPFS in the POWERHA environment? and can GPFS work as cluster active active or active passive thanks in advance (0 Replies)
Discussion started by: Vit0_Corleone
0 Replies

7. AIX

GPFS 3.3

Dear all for the last few days i was searching in IBM web site for GPFS 3.3 to upgrade my gpfs from 3.2 to 3.3 and i did not find the download link for the GPFS 3.3 in IBM website please can anyone give me the link . (4 Replies)
Discussion started by: thecobra151
4 Replies

8. AIX

How to get rid of GPFS ?

Hi We are doing the migration of DMX3 disks to DMX4 disks using migratepv. We are not using GPFS but we have gpfs disks present in the server. Can anyone advise how to get rid of GPFS in both the servers cbspsrdb01 and cbspsrdb02. I will do migratepv for the other disks present in the servers... (2 Replies)
Discussion started by: newtoaixos
2 Replies

9. AIX

GPFS is too slow after installtion

we have implement GPFS 3.5.0.10 with 4 nodes cluster AIX 6.1 TL8 and they VIO clients , after that we noticed a big delay while we execute any command like mmgetstate -a will take about 2.5 minutes . time mmgetstate -a Node number Node name GPFS state ... (3 Replies)
Discussion started by: thecobra151
3 Replies

10. AIX

Difference between NFS and GPFS

Hello Gurus, Could you please help me out of the difference between GPFS and NFS. Thanks- P (1 Reply)
Discussion started by: pokhraj_d
1 Replies
VFS_GPFS(8)						    System Administration tools 					       VFS_GPFS(8)

NAME
vfs_gpfs - gpfs specific samba extensions like acls and prealloc SYNOPSIS
vfs objects = gpfs DESCRIPTION
This VFS module is part of the samba(7) suite. The gpfs VFS module is the home for all gpfs extensions that Samba requires for proper integration with GPFS. It uses the GPL library interfaces provided by GPFS. Currently the gpfs vfs module provides extensions in following areas : o NFSv4 ACL Interfaces with configurable options for GPFS o Kernel oplock support on GPFS o Lease support on GPFS NOTE:This module follows the posix-acl behaviour and hence allows permission stealing via chown. Samba might allow at a later point in time, to restrict the chown via this module as such restrictions are the responsibility of the underlying filesystem than of Samba. This module makes use of the smb.conf parameter acl map full control = acl map full control When set to yes (the default), this parameter will add in the FILE_DELETE_CHILD bit on a returned ACE entry for a file (not a directory) that already contains all file permissions except for FILE_DELETE and FILE_DELETE_CHILD. This can prevent Windows applications that request GENERIC_ALL access from getting ACCESS_DENIED errors when running against a filesystem with NFSv4 compatible ACLs. This module is stackable. Since Samba 4.0 all options are per share options. OPTIONS
gpfs:sharemodes = [ yes | no ] Enable/Disable cross node sharemode handling for GPFS. o yes(default) - propagate sharemodes across all GPFS nodes. o no - do not propagate sharemodes across all GPFS nodes. This should only be used if the GPFS file system is exclusively exported by Samba. Access by local unix application or NFS exports could lead to corrupted files. gpfs:leases = [ yes | no ] Enable/Disable cross node leases (oplocks) for GPFS. You should also set the oplocks and kernel oplocks options to the same value. o yes(default) - propagate leases across all GPFS nodes. o no - do not propagate leases across all GPFS nodes. This should only be used if the GPFS file system is exclusively exported by Samba. Access by local unix application or NFS exports could lead to corrupted files. gpfs:hsm = [ yes | no ] Enable/Disable announcing if this FS has HSM enabled. o no(default) - Do not announce HSM. o yes - Announce HSM. gpfs:getrealfilename = [ yes | no ] Enable/Disable usage of the gpfs_get_realfilename_path() function. This improves the casesensitive wildcard file name access. o yes(default) - use gpfs_get_realfilename_path(). o no - do not use gpfs_get_realfilename_path(). It seems that gpfs_get_realfilename_path() doesn't work on AIX. gpfs:winattr = [ yes | no ] Enable/Disable usage of the windows attributes in GPFS. GPFS is able to store windows file attributes e.g. HIDDEN, READONLY, SYSTEM and others natively. That means Samba doesn't need to map them to permission bits or extended attributes. o no(default) - do not use GPFS windows attributes. o yes - use GPFS windows attributes. gpfs:merge_writeappend = [ yes | no ] GPFS ACLs doesn't know about the 'APPEND' right. This option lets Samba map the 'APPEND' right to 'WRITE'. o yes(default) - map 'APPEND' to 'WRITE'. o no - do not map 'APPEND' to 'WRITE'. gpfs:acl = [ yes | no ] This option lets Samba use or ignore GPFS ACLs. o yes(default) - use GPFS ACLs. o no - do not use GPFS ACLs and pass everything to the next SMB_VFS module. gpfs:refuse_dacl_protected = [ yes | no ] As GPFS does not support the ACE4_FLAG_NO_PROPAGATE NFSv4 flag (which would be the mapping for the DESC_DACL_PROTECTED flag), the status of this flag is currently silently ignored by Samba. That means that if you deselect the "Allow inheritable permissions..." checkbox in Windows' ACL dialog and then apply the ACL, the flag will be back immediately. To make sure that automatic migration with e.g. robocopy does not lead to ACLs silently (and unintentionally) changed, you can set gpfs:refuse_dacl_protected = yes to enable an explicit check for this flag and if set, it will return NT_STATUS_NOT_SUPPORTED so errors are shown up on the Windows side and the Administrator is aware of the ACLs not being settable like intended o no(default) - ignore the DESC_DACL_PROTECTED flags. o yes - reject ACLs with DESC_DACL_PROTECTED. gpfs:dfreequota = [ yes | no ] Adjust reporting of the size and free space of a share according to quotas. If this setting is "yes", a request for size and free space will also evaluate the user quota of the user requesting the data, the group quota of the primary group of the user and the fileset quota for the fileset containing the top level directory of the share. If any of the soft or hard quota limits has been reached, the free space will be reported as 0. If a quota is in place, but the limits have not been reached, the free space will be reported according to the space left in the quota. If more than one quota applies the free space will be reported as the smallest space left in those quotas. The size of the share will be reported according to the quota usage. If more than one quota applies, the smallest size will be reported for the share size according to these quotas. o yes - include the quotas when reporting the share size and free space o no(default) - do not include quotas, simply report the size and free space of the file system gpfs:prealloc = [ yes | no ] If set to yes the gpfs_prealloc function will be used in the fallocate callback when appropriate. If set to no gpfs_prealloc will not be used. In both cases the system and libc calls are avoided. o yes (default) - Use gpfs_prealloc for the fallocate callback. o no - Do not use gpfs_prealloc for the fallocate callback. nfs4:mode = [ simple | special ] Controls substitution of special IDs (OWNER@ and GROUP@) on GPFS. The use of mode simple is recommended. In this mode only non inheriting ACL entries for the file owner and group are mapped to special IDs. The following MODEs are understood by the module: o simple(default) - use OWNER@ and GROUP@ special IDs for non inheriting ACEs only. o special(deprecated) - use OWNER@ and GROUP@ special IDs in ACEs for all file owner and group ACEs. nfs4:acedup = [dontcare|reject|ignore|merge] This parameter configures how Samba handles duplicate ACEs encountered in GPFS ACLs. GPFS allows/creates duplicate ACE for different bits for same ID. Following is the behaviour of Samba for different values : o dontcare (default) - copy the ACEs as they come o reject - stop operation and exit with error on ACL set op o ignore - don't include the second matching ACE o merge - bitwise OR the 2 ace.flag fields and 2 ace.mask fields of the 2 duplicate ACEs into 1 ACE nfs4:chown = [yes|no] This parameter allows enabling or disabling the chown supported by the underlying filesystem. This parameter should be enabled with care as it might leave your system insecure. Some filesystems allow chown as a) giving b) stealing. It is the latter that is considered a risk. Following is the behaviour of Samba for different values : o yes - Enable chown if as supported by the under filesystem o no (default) - Disable chown gpfs:syncio = [yes|no] This parameter makes Samba open all files with O_SYNC. This triggers optimizations in GPFS for workloads that heavily share files. Following is the behaviour of Samba for different values: o yes - Open files with O_SYNC o no (default) - Open files as normal Samba would do EXAMPLES
A GPFS mount can be exported via Samba as follows : [samba_gpfs_share] vfs objects = gpfs path = /test/gpfs_mount nfs4: mode = special nfs4: acedup = merge CAVEATS
Depending on the version of gpfs, the libgpfs_gpl library or the libgpfs library is needed at runtime by the gpfs VFS module: Starting with gpfs 3.2.1 PTF8, the complete libgpfs is available as open source and libgpfs_gpl does no longer exist. With earlier versions of gpfs, only the libgpfs_gpl library was open source and could be used at run time. At build time, only the header file gpfs_gpl.h is required , which is a symlink to gpfs.h in gpfs versions newer than 3.2.1 PTF8. VERSION
This man page is correct for version 3.0.25 of the Samba suite. AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. The GPFS VFS module was created with contributions from Volker Lendecke and the developers at IBM. This manpage was created by the IBM FSCC team Samba 4.0 06/17/2014 VFS_GPFS(8)
All times are GMT -4. The time now is 11:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy