Issue mongodb#409 Complete translate

Author: jerry-shao

locale/zh/LC_MESSAGES/faq/storage.po

@@ -4,7 +4,7 @@ msgstr ""
 "Project-Id-Version: mongodb-manual 2.6\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2014-09-03 15:39-0400\n"
-"PO-Revision-Date: 2015-01-14 22:53-0000\n"
+"PO-Revision-Date: 2015-01-19 12:59-0000\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <[email protected]>\n"
 "MIME-Version: 1.0\n"
@@ -61,21 +61,25 @@ msgid ""
 "memory allows MongoDB to interact with the data in the file as if it were "
 "memory."
 msgstr ""
+"内存映射会将文件以字节的形式之间分配到虚拟内存。一旦产生映射，MongoDB会通过"
+"文件与内存之间的关联与之进行交互，因为文件就像在内存里一样。"
 
 #: ../source/faq/storage.txt:36
 msgid "How does MongoDB work with memory mapped files?"
-msgstr ""
+msgstr "MongoDB与内存映射文件是如何工作的？"
 
 #: ../source/faq/storage.txt:38
 msgid ""
 "MongoDB uses memory mapped files for managing and interacting with all "
 "data. MongoDB memory maps data files to memory as it accesses documents. "
 "Data that isn't accessed is *not* mapped to memory."
 msgstr ""
+"MongoDB使用内存映射文件来管理数据并与之进行交互。MongoDB会使内存与数据文件进"
+"行关联，就像连接文档。数据也会映射到内存中。"
 
 #: ../source/faq/storage.txt:45
 msgid "What are page faults?"
-msgstr "什么是页面错误？"
+msgstr "什么是缺页中断？"
 
 #: ../source/includes/fact-page-fault.rst:1
 msgid ""
@@ -84,6 +88,8 @@ msgid ""
 "operating system page faults happen when physical memory is exhausted and "
 "pages of physical memory are swapped to disk."
 msgstr ""
+"缺页中断会导致MongoDB不在当前的物理内存进行读写操作。然而，操作系统页面错误"
+"是因为物理内存被耗尽或超出磁盘空间。"
 
 #: ../source/faq/storage.txt:49
 msgid ""
@@ -109,14 +115,16 @@ msgid ""
 "This process, particularly on an active system can take a long time, "
 "particularly in comparison to reading a page that is already in memory."
 msgstr ""
+"在这个过程中，特别是处于活动状态的系统，需要很长时间。可以比较一下读取已经在"
+"内存中的页面。"
 
 #: ../source/faq/storage.txt:62 ../source/faq/storage.txt:74
 msgid "See :ref:`administration-monitoring-page-faults` for more information."
-msgstr ""
+msgstr "通过 :ref:`administration-monitoring-page-faults` 查看更多信息。"
 
 #: ../source/faq/storage.txt:65
 msgid "What is the difference between soft and hard page faults?"
-msgstr ""
+msgstr "软硬缺页中断有什么不同？"
 
 #: ../source/faq/storage.txt:67
 msgid ""
@@ -127,6 +135,8 @@ msgid ""
 "another, such as from an operating system file cache. In production, "
 "MongoDB will rarely encounter soft page faults."
 msgstr ""
+":term:`缺页中断 <page fault>` 会导致MongoDB在需要连接数据时不在当前活动的内"
+"存中工作。当MongoDB需要通过磁盘连接数据时，页面\"硬\"错误代表当前的状态。"
 
 #: ../source/faq/storage.txt:79
 msgid "What tools can I use to investigate storage use in MongoDB?"
@@ -166,29 +176,36 @@ msgid ""
 "system. The next time MongoDB needs to access these documents, MongoDB may "
 "incur a hard page fault."
 msgstr ""
+"如果你想让MongoDB扫描集合中的所有文档，工作集将会扩展至每一个文档。基于物理"
+"内存的大小，这个可能会导致文档在工作集中 \"溢出,\" 或者被操作系统从物理内存"
+"中移除。当下次MongoDB需要连接这些文档时，MongoDB可能会引发一个硬缺页中断。"
 
 #: ../source/faq/storage.txt:103
 msgid ""
 "If you run a query that requires MongoDB to scan every :term:`document` in "
 "a collection, the working set includes every active document in memory."
 msgstr ""
+"如果你想让MongoDB扫描集合中的所有 :term:`document`， 工作集的内存中会含有所"
+"有活动的文档。"
 
 #: ../source/faq/storage.txt:107
 msgid ""
 "For best performance, the majority of your *active* set should fit in RAM."
-msgstr ""
+msgstr "多数 *active* 配置在RAM中会得到更好的性能。"
 
 #: ../source/faq/storage.txt:113
 msgid ""
 "Why are the files in my data directory larger than the data in my database?"
-msgstr ""
+msgstr "为什么目录里面的文件比我的数据库还要大？"
 
 #: ../source/faq/storage.txt:115
 msgid ""
 "The data files in your data directory, which is the :file:`/data/db` "
 "directory in default configurations, might be larger than the data set "
 "inserted into the database. Consider the following possible causes:"
 msgstr ""
+"默认存储目录 :file:`/data/db` 中的数据文件可能会比数据库中的数据大，思考一下"
+"下面可能的原因："
 
 #: ../source/faq/storage.txt:119
 msgid "Preallocated data files."
@@ -206,6 +223,12 @@ msgid ""
 "file that may be 90% empty. For most larger databases, unused allocated "
 "space is small compared to the database."
 msgstr ""
+"在数据目录中，MongoDB预配置数据文件为一个指定的大小，这是保护文件系统碎片的"
+"一部分。MongoDB将第一个数据文件命名为 ``<databasename>.0``，第二个为 "
+"``<databasename>.1``等等。第一个文件 :program:`mongod` 分配了64MB，第二个"
+"128MB等等，直到2GB，随后的文件都将是2GB。数据文件包括文件的分配空间但里面没"
+"有数据。 :program:`mongod` 可能会出现1G分配空间中90%未使用的情况。对于大部分"
+"大数据库来说，不对数据库使用分配空间没什么大的差别。"
 
 #: ../source/faq/storage.txt:132
 msgid ""
@@ -225,6 +248,9 @@ msgid ""
 "preallocDataFiles` for testing and with small data sets where you "
 "frequently drop databases."
 msgstr ""
+"你可以通过 :setting:`~storage.preallocDataFiles` 设置将预配置设为 "
+"``false``。但是千万不要设置 :setting:`~storage.preallocDataFiles` ，只需使"
+"用 :setting:`~storage.preallocDataFiles` 调试你经常删除的小数据库。"
 
 #: ../source/faq/storage.txt:144
 msgid ""
@@ -246,28 +272,37 @@ msgid ""
 "should not need to resize the oplog. However, if you do, see :doc:`/"
 "tutorial/change-oplog-size`."
 msgstr ""
+"如果 :program:`mongod` 是复制集成员，数据目录包括 ``local`` 数据库中 :term:`"
+"固定集合` 的 :term:`oplog.rs <oplog>` 文件。在64位安装包中，默认分配空间大约"
+"为磁盘空间的5%，通过 <replica-set-oplog-sizing>` 查看更多信息。在大部分实例"
+"中，你不需要调整oplog的大小。当然，如果你想调整，可以查看 :doc:`/tutorial/"
+"change-oplog-size`。"
 
 #: ../source/faq/storage.txt:162
 msgid "The :term:`journal`."
-msgstr ""
+msgstr ":term:`journal`"
 
 #: ../source/faq/storage.txt:164
 msgid ""
 "The data directory contains the journal files, which store write operations "
 "on disk prior to MongoDB applying them to databases. See :doc:`/core/"
 "journaling`."
 msgstr ""
+"数据目录含有journal文件，它将MongoDB在操作数据库中的写入操作存储在磁盘上。查"
+"看 :doc:`/core/journaling`。"
 
 #: ../source/faq/storage.txt:168
 msgid "Empty records."
-msgstr ""
+msgstr "空记录。"
 
 #: ../source/faq/storage.txt:170
 msgid ""
 "MongoDB maintains lists of empty records in data files when deleting "
 "documents and collections. MongoDB can reuse this space, but will never "
 "return this space to the operating system."
 msgstr ""
+"当删除文档和集合时，MongoDB将会继续列出数据文件中的空记录。MongoDB可以重复使"
+"用这部分空间，但是不会释放这部分空间给操作系统。"
 
 #: ../source/faq/storage.txt:174
 msgid ""
@@ -277,12 +312,17 @@ msgid ""
 "gigabytes of extra disk space to run. Do not use :dbcommand:`compact` if "
 "you are critically low on disk space."
 msgstr ""
+"使用 :dbcommand:`compact`可以重组分配存储空间。通过重置存储，MongoDB可以有效"
+"的利用分配空间。 :dbcommand:`compact` 需要额外2GB磁盘空间来运行。如果磁盘空"
+"间较少，禁止使用 :dbcommand:`compact` 。"
 
 #: ../source/faq/storage.txt:180
 msgid ""
 ":dbcommand:`compact` only removes fragmentation from MongoDB data files and "
 "does not return any disk space to the operating system."
 msgstr ""
+" :dbcommand:`compact` 只会移除MongoDB数据文件中的碎片，不会释放磁盘空间给操"
+"作系统。"
 
 #: ../source/faq/storage.txt:184
 msgid ""
@@ -292,6 +332,9 @@ msgid ""
 "extra disk space to run. Do not use :dbcommand:`repairDatabase` if you are "
 "critically low on disk space."
 msgstr ""
+"使用 :dbcommand:`repairDatabase` 重置存储来重建数据库可以再次利用删除的空"
+"间。 :dbcommand:`repairDatabase` 需要至少2G额外磁盘空间来运行。如果磁盘空间"
+"较少，禁止使用 :dbcommand:`repairDatabase`。"
 
 #: ../source/faq/storage.txt:191
 msgid ""
@@ -300,10 +343,13 @@ msgid ""
 "dbcommand:`repairDatabase` will block all other operations and may take a "
 "long time to complete."
 msgstr ""
+"当使用 :dbcommand:`repairDatabase` 进行修复时，需要足够的磁盘空间来支持新旧"
+"数据库。可以使用 :dbcommand:`repairDatabase` 锁定其它操作，可能需要一定的时"
+"间。"
 
 #: ../source/faq/storage.txt:197
 msgid "How can I check the size of a collection?"
-msgstr ""
+msgstr "如何查看集合的大小？"
 
 #: ../source/faq/storage.txt:199
 msgid ""
@@ -312,10 +358,13 @@ msgid ""
 "example issues :method:`db.collection.stats()` for the ``orders`` "
 "collection:"
 msgstr ""
+"如果想查看集合的大小或其它信息，可以在 :program:`mongo` 命令行中使用 :"
+"method:`db.collection.stats()` 。如下面的例子，在 ``orders`` 集合中使用 :"
+"method:`db.collection.stats()` ："
 
 #: ../source/faq/storage.txt:208
 msgid "To view specific measures of size, use these methods:"
-msgstr ""
+msgstr "通过指定方式查看数据大小，可以使用一下方法："
 
 #: ../source/faq/storage.txt:210
 msgid ""
@@ -342,7 +391,7 @@ msgstr ":method:`db.collection.totalIndexSize()`: 索引的大小"
 msgid ""
 "Also, the following scripts print the statistics for each database and "
 "collection:"
-msgstr ""
+msgstr "当然，下面的脚本可以统计每个数据库和集合："
 
 #: ../source/faq/storage.txt:227
 msgid "How can I check the size of indexes?"
@@ -353,18 +402,24 @@ msgid ""
 "To view the size of the data allocated for an index, use one of the "
 "following procedures in the :program:`mongo` shell:"
 msgstr ""
+"如果想查看索引的数据分配大小，可以在 :program:`mongo` 命令行中参照下面的步"
+"骤："
 
 #: ../source/faq/storage.txt:232
 msgid ""
 "Use the :method:`db.collection.stats()` method using the index namespace. "
 "To retrieve a list of namespaces, issue the following command:"
 msgstr ""
+"通过 :method:`db.collection.stats()` 方法使用索引命名空间。使用以下命令可以"
+"恢复命名空间列表："
 
 #: ../source/faq/storage.txt:240
 msgid ""
 "Check the value of :data:`~collStats.indexSizes` in the output of the :"
 "method:`db.collection.stats()` command."
 msgstr ""
+"在 :method:`db.collection.stats()` 命令中查看 :data:`~collStats.indexSizes` "
+"的值。"
 
 #: ../source/faq/storage.txt:0
 msgid "Example"
@@ -378,7 +433,7 @@ msgstr "该命令会返回一个类似下面的列表："
 msgid ""
 "View the size of the data allocated for the ``orders.$_id_`` index with the "
 "following sequence of operations:"
-msgstr ""
+msgstr "参照下面的操作顺序查看 ``orders.$_id_`` 索引的数据分配大小："
 
 #: ../source/faq/storage.txt:266
 msgid "How do I know when the server runs out of disk space?"
@@ -409,10 +464,15 @@ msgid ""
 "put the journal files on another storage device using a filesystem mount or "
 "a symlink."
 msgstr ""
+"如果journal文件在你的服务运行过程中超出磁盘空间，服务进程将会结束。 :"
+"program:`mongod` 默认在:setting:`~storage.dbPath` 目录中创建journal文件。你"
+"可以使用资源管理器或symlink将其移动到其它磁盘。"
 
 #: ../source/faq/storage.txt:293
 msgid ""
 "If you place the journal files on a separate storage device you will not be "
 "able to use a file system snapshot tool to capture a valid snapshot of your "
 "data files and journal files."
 msgstr ""
+"如果你将journal文件放置在一个外置存储器中，你将无法使用snapshot tool获得你的"
+"数据文件和journal文件。"