Values
------
(note, for capped collections, there are more fields that aren't listed here)

.. data:: ns
The full namespace name of the collection

.. data:: firstExtent
.. data:: lastExtent
The disk locations of the first and last extents in the collection, along with the namespaces those extents belong to.

.. data:: extentCount
The number of extents in the collection.

.. :data:: extents
All of the extents in the namespace are enumerated here.

   .. note::

      This sub-document is only returned when you specify the ``full`` option.

   .. :data:: extents.loc
The disk location for the beginning of this extent.

   .. :data:: extents.xnext
The disk location for the extent following this one. "null" if this is the end of the linked list of extents.

   .. :data:: extents.xprev
The disk location for the extent preceding this one. "null" if this is the head of the linked list of extents.

   .. :data:: extents.nsdaig  <--- note typo, should be nsdiag
The namespace this extent belongs to (should be the same as the namespace shown at the beginning of the validate listing).

   .. :data:: extents.size
The number of bytes in this extent.

   .. :data:: extents.firstRecord
   .. :data:: extents.lastRecord
The disk locations of the first and last record in this extent.


.. data:: datasize
The number of bytes in all data records.  This does not include deleted records, nor does it include extent headers, nor record headers, nor space in a file unallocated to any extent.  It does, however, include record padding, which is extra space within a record (document) to avoid moving the record when the record grows in size.

.. data:: nsrecords <--- typo. it's nrecords
Number of data records (documents) in the collection.

.. data:: lastExtentSize
The last new extent in this collection was created with this size.  The extent sizing algorithm uses this value to determine how large to make the next new extent.

.. data:: padding
A floating point value between 1 and 2. When a record is created, the padding factor is used to calculate how much to pad the record.  A value of 1 means no padding; a value of 2 means the record will consume double the amount of space that it actually needs.  The padding will allow a record to be updated in place, and get larger, without needing to be moved to a new location.  Padding factor is automatically adjusted by mongo when it notices that update operations are triggering record moves.

.. data:: firstExtentDetails
Same as above for the extent list.

   .. data:: firstExtentDetails.loc

   .. data:: firstExtentDetails.xnext

   .. data:: firstExtentDetails.xprev

   .. data:: firstExtentDetails.nsdiag

   .. data:: firstExtentDetails.size

   .. data:: firstExtentDetails.firstRecord

   .. data:: firstExtentDetails.lastRecord

.. data:: objectsFound
The number of records actually encountered in a scan of the collection. This should be the same as the nrecords field.

.. data:: invalidObjects
The number of records containing BSON objects that do not pass a validation check.

   .. note::

      This field is only included in the validation output when you
      specify the ``full`` option.

.. data:: byteswWithHeaders  <--- typo
This is similar to datasize, except that it includes the record headers (16 bytes apiece in version 2.0)

   .. note::

      This field is only included in the validation output when you
      specify the ``full`` option.

.. data:: bytesWithoutHeaders
This is a calculated value by scanning all records; it should be the same as datasize above.
   .. note::

      This field is only included in the validation output when you
      specify the ``full`` option.

.. data:: deletedCount
Number of deleted/free records in the collection.

.. data:: deletedSize
Size of all the deleted/free records in the collection.

.. data:: nIndexes
Number of indexes associated with the collection.

.. data:: keysPerIndex
Each index is listed, along with a count of its keys.

.. data:: valid
.. data:: errors
If any validation problems are found, valid is set to false, and the errors array is filled in with explanatory messages

.. data:: ok
If the command fails, ok is set to false.  This can happen if the specified collection does not exist.