example 'OBD_CONNECT_RDONLY' is optional depending on client mount
options). The request also contains other fields that are only valid
if the matching flag is set. The server replies in 'ocd_connect_flags'
-with the subset of feature flags that it understands and intends to honour.
+with the subset of feature flags that it understands and intends to honor.
The server may set fields in the reply for mutually-understood features.
The 'ocd_connect_flags' field encodes the connect flags giving the
If the OBD_CONNECT_INDEX flag is set then the 'ocd_index' field is
valid. The 'ocd_index' value is set in a request to hold the LOV
index of the OST or the LMV index of the MDT. The server's export for
-the target holds the correct value, and if the client send a value
-that does not match the server returns the -EBDF error.
+the target holds the correct value, and if the client sends a value
+that does not match the server returns the -EBADF error.
If the OBD_CONNECT_BRW_SIZE flag is set then the 'ocd_brw_size' field
is valid. The 'ocd_brw_size' value sets the maximum supported bulk
If the OBD_CONNECT_GRANT_PARAM flag is set then the 'ocd_blocksize',
'ocd_inodespace', and 'ocd_grant_extent' fields are honored. A server
reply uses the 'ocd_blocksize' value to inform the client of the log
-base two of the size in bytes of the backend file system's blocks.
+base two of the size in bytes of the OSD's blocks.
A server reply uses the 'ocd_inodespace' value to inform the client of
the log base two of the size of an inode.
of the maximum OST object size for this target. A file that is striped
uniformly across multiple OST objects (RAID-0) cannot be larger than the
number of stripes times the minimum 'ocd_maxbytes' value from any of its
-consituent objects.
+constituent objects.
The additional space in the 'obd_connect_data' structure is unused and
reserved for future use.
from this client.
If the OBD_CONNECT_SRVLOCK flag is set then the client and server
-support lockless IO. The server will take locks for client IO requests
+support lock-less IO. The server will take locks for client IO requests
with the OBD_BRW_SRVLOCK flag in the 'niobuf_remote' structure
flags. This is used for Direct IO or when there is significant lock
contention on a single OST object. The client takes no LDLM lock and
delegates locking to the server.
If the OBD_CONNECT_ACL flag is set then the server supports the ACL
-mount option for its filesystem. If the server is mounted with ACL
+mount option for its file system. If the server is mounted with ACL
support but the client does not pass OBD_CONNECT_ACL then the client
mount is refused.
If the OBD_CONNECT_XATTR flag is set then the server supports user
extended attributes. This is requested by the client if mounted
with the appropriate mount option, but is enabled or disabled by the
-mount options of the backend file system of MDT0000.
+mount options of the OSD for MDT0000.
If the OBD_CONNECT_TRUNCLOCK flag is set then the client and the
-server support lockless truncate. This is realized in an OST_PUNCH RPC
+server support lock-less truncate. This is realized in an OST_PUNCH RPC
by setting the 'obdo' structure's 'o_flag' field to include the
OBD_FL_SRVLOCK. In that circumstance the client takes no lock, and the
server must take a lock on the resource while performing the truncate.
If the OBD_CONNECT_CANCELSET is set then early batched cancels are
enabled. The ELC (Early Lock Cancel) feature allows client locks to
-be cancelled prior the cancellation callback if it is clear that lock
+be canceled prior the cancellation callback if it is clear that lock
is not needed anymore, for example after rename, after removing file
or directory, link, etc. This can reduce amount of RPCs significantly.
lock to the old clients that do not support this feature.
If the OBD_CONNECT_64BITHASH is set then the client supports 64-bit
-directory readdir cookie. The server will also use 64-bit hash mode
+directory 'readdir' cookie. The server will also use 64-bit hash mode
while working with ldiskfs.
If the OBD_CONNECT_JOBSTATS is set then the client fills jobid in
optimize a recovery of open requests.
If the OBD_CONNECT_OPEN_BY_FID is set then an open by FID won't pack
-the name in a request. This is used by HSM or other ChangeLog consumers
+the name in a request. This is used by HSM or other 'ChangeLog' consumers
for accessing objects by their FID via .lustre/fid/ instead of by name.
If the OBD_CONNECT_MDS_MDS is set then the current connection is an
MDS avoiding glimpse request to OSTs. This feature was implemented as
demo feature and wasn't enabled by default. Finally it was removed in
Lustre 2.7 because it causes quite complex recovery cases to handle
-with relatevely small benefits.
+with relatively small benefits.
The OBD_CONNECT_QUOTA64 was used prior Lustre 2.4 for quota purposes,
it is obsoleted due to new quota design.
RPC error properly. The quota design requires that client must resend
request with -EINPROGRESS error indefinitely, until successful
completion or another error. This flag is set on both client and
-server by default. Meanwhile this flag is not checked anywere, so does
+server by default. Meanwhile this flag is not checked anywhere, so does
nothing.
If the OBD_CONNECT_FLOCK_OWNER is set then 1.8 clients has fixed flock
git://git.whamcloud.com / doc / protocol.git / blobdiff