-
-An 'obd_statfs' structure conveys file-system-wide information for the
-back-end file system of a given target (MDT or OST).
+****
+An 'obd_statfs' structure conveys file-system-wide information of a
+given target (MDT or OST).
Most of the fields correspond directly to the 'struct statfs' fields
returned by a 'statfs()' system call and have the same meaning. The
Most of the fields correspond directly to the 'struct statfs' fields
returned by a 'statfs()' system call and have the same meaning. The
'os_bfree', and 'os_bavail' respectively. It does not necessarily
represent the minimum or optimal IO size.
'os_bfree', and 'os_bavail' respectively. It does not necessarily
represent the minimum or optimal IO size.
The 'os_maxbytes' field is the maximum size of a single object
(i.e. the maximum byte offset that can be written to). This is the
same value as the 'ocd_maxbytes' field of the 'obd_connect_data'
structure.
The 'os_maxbytes' field is the maximum size of a single object
(i.e. the maximum byte offset that can be written to). This is the
same value as the 'ocd_maxbytes' field of the 'obd_connect_data'
structure.
rebuilding the state is returned with the OS_STATE_DEGRADED (0x1) flag
set. If the file system has been set to read-only, either manually at
mount or automatcially due to detected corruption of the underlying
rebuilding the state is returned with the OS_STATE_DEGRADED (0x1) flag
set. If the file system has been set to read-only, either manually at
mount or automatcially due to detected corruption of the underlying
2*OST_MAX_PRECREATE (2*20000) on the number of precreates it will
allow for an OST. There are currently no precreated objects on an MDT
so it is just 0 in that case.
2*OST_MAX_PRECREATE (2*20000) on the number of precreates it will
allow for an OST. There are currently no precreated objects on an MDT
so it is just 0 in that case.