100 | ddp |
ddp |
1001 | 操作: |
Operation: |
1002 | 上下文: |
Context: |
1003 | 错误特定详细信息: |
Error-specific details: |
1004 | 故障: |
Failure: |
1011 | 错误 |
Error |
1012 | 卷名 |
Volume name |
1013 | 卷影副本卷 |
Shadow copy volume |
1014 | 配置文件 |
Configuration file |
1015 | 无法使用域控制器。 |
The domain controller is unavailable. |
1016 | 服务器 |
Server |
1017 | 域 |
Domain |
1018 | 文件名 |
File name |
1020 | 目录 |
Directory |
1021 | 区块存储 |
Chunk store |
1022 | 区块 ID |
Chunk ID |
1023 | 流映射 |
Stream map |
1024 | 区块存储容器 |
Chunk store container |
1025 | 文件路径 |
File path |
1026 | 文件 ID |
File ID |
1027 | 区块大小 |
Chunk size |
1028 | 区块偏移 |
Chunk offset |
1029 | 区块标志 |
Chunk flags |
1030 | 录制时间 |
Recorded time |
1031 | 错误消息 |
Error message |
1034 | 源上下文 |
Source context |
1037 | 内部错误上下文 |
Inner error context |
1038 | 错误时间戳 |
Error timestamp |
1039 | 文件偏移量 |
File offset |
1040 | 失败原因 |
Failure reason |
1041 | 重试计数 |
Retry count |
1042 | 请求 ID |
Request ID |
1043 | 流映射计数 |
Stream map count |
1044 | 区块计数 |
Chunk count |
1045 | 数据大小 |
Data size |
2001 | 正在启动文件服务器删除重复服务。 |
Starting File Server Deduplication Service. |
2002 | 正在停止重复数据删除服务。 |
Stopping the Data Deduplication service. |
2003 | 正在检查文件服务器删除重复全局配置存储。 |
Checking the File Server Deduplication global configuration store. |
2101 | 正在初始化重复数据删除微筛选器。 |
Initializing the data deduplication mini-filter. |
2105 | 将备份组件列表发送到 VSS 系统。 |
Sending backup components list to VSS system. |
2106 | 准备备份。 |
Preparing for backup. |
2107 | 执行还原前操作。 |
Performing pre-restore operations. |
2108 | 执行还原后操作。 |
Performing post-restore operations. |
2110 | 正在处理文件服务器删除重复事件。 |
Processing File Server Deduplication event. |
2111 | 正在创建区块存储。 |
Creating a chunk store. |
2112 | 初始化区块存储。 |
Initializing chunk store. |
2113 | 取消初始化区块存储。 |
Uninitializing chunk store. |
2114 | 创建区块存储会话。 |
Creating a chunk store session. |
2115 | 提交区块存储会话。 |
Committing a chunk store session. |
2116 | 中止区块存储会话。 |
Aborting a chunk store session. |
2117 | 开始创建区块存储流。 |
Initiating creation of a chunk store stream. |
2118 | 将新区块插入区块存储流。 |
Inserting a new chunk to a chunk store stream. |
2119 | 正在将现有区块插入到区块流中。 |
Inserting an existing chunk to a chunk stream. |
2120 | 提交区块存储流的创建。 |
Committing creation of a chunk store stream. |
2121 | 正在中止创建区块存储流。 |
Aborting creation of a chunk store stream. |
2122 | 提交对区块存储容器的更改。 |
Committing changes to a chunk store container. |
2123 | 已经刷新对磁盘的区块存储容器的更改。 |
Changes made to a chunk store container have been flushed to disk. |
2124 | 使新区块存储容器准备就绪,可以投入使用。 |
Making a new chunk store container ready to use. |
2125 | 回退上一次提交的对区块存储容器的更改。 |
Rolling back the last committed changes to a chunk store container. |
2126 | 将区块存储容器标记为只读。 |
Marking a chunk store container as read-only. |
2127 | 枚举区块存储中的所有容器。 |
Enumerating all containers in a chunk store. |
2128 | 准备区块存储容器以插入区块。 |
Preparing a chunk store container for chunk insertion. |
2129 | 初始化新的区块存储容器。 |
Initializing a new chunk store container. |
2130 | 打开现有的区块存储容器。 |
Opening an existing chunk store container. |
2131 | 将新的区块插入到区块存储容器。 |
Inserting a new chunk to a chunk store container. |
2132 | 修复区块存储戳文件。 |
Repairing a chunk store stamp file. |
2133 | 创建区块存储戳文件。 |
Creating a chunk store stamp file. |
2134 | 打开区块存储流。 |
Opening a chunk store stream. |
2135 | 从区块存储流读取流映射条目。 |
Reading stream map entries from a chunk store stream. |
2136 | 读取区块存储区块。 |
Reading a chunk store chunk. |
2137 | 关闭区块存储流。 |
Closing a chunk store stream. |
2138 | 读取区块存储容器。 |
Reading a chunk store container. |
2139 | 打开区块存储容器日志文件。 |
Opening a chunk store container log file. |
2140 | 读取区块存储容器日志文件。 |
Reading a chunk store container log file. |
2141 | 将条目写入到区块存储容器日志文件。 |
Writing entries to a chunk store container log file. |
2142 | 正在枚举区块存储容器日志文件。 |
Enumerating chunk store container log files. |
2143 | 删除区块存储容器日志文件。 |
Deleting chunk store container log files. |
2144 | 读取区块存储容器位图文件。 |
Reading a chunk store container bitmap file. |
2145 | 写入区块存储容器位图文件。 |
Writing a chunk store container bitmap file. |
2146 | 删除区块存储容器位图文件。 |
Deleting a chunk store container bitmap file. |
2147 | 启动区块存储垃圾收集。 |
Starting chunk store garbage collection. |
2148 | 对活动区块参照编制索引。 |
Indexing active chunk references. |
2149 | 处理删除的区块存储流。 |
Processing deleted chunk store streams. |
2150 | 标识未参照的区块。 |
Identifying unreferenced chunks. |
2151 | 枚举区块存储。 |
Enumerating the chunk store. |
2152 | 初始化区块存储枚举器。 |
Initializing the chunk store enumerator. |
2153 | 初始化流映射分析程序。 |
Initializing the stream map parser. |
2154 | 迭代流映射。 |
Iterating the stream map. |
2155 | 初始化区块存储压缩。 |
Initializing chunk store compaction. |
2156 | 压缩区块存储容器。 |
Compacting chunk store containers. |
2157 | 初始化流映射压缩协调。 |
Initializing stream map compaction reconciliation. |
2158 | 由于数据压缩正在协调流映射。 |
Reconciling stream maps due to data compaction. |
2159 | 初始化区块存储协调。 |
Initializing chunk store reconciliation. |
2160 | 协调区块存储中的重复区块。 |
Reconciling duplicate chunks in the chunk store. |
2161 | 正在初始化删除重复垃圾回收作业。 |
Initializing the deduplication garbage collection job. |
2162 | 运行重复项清除垃圾收集工作。 |
Running the deduplication garbage collection job. |
2163 | 取消重复项清除垃圾收集工作。 |
Canceling the deduplication garbage collection job. |
2164 | 等待重复项清除垃圾收集工作完成。 |
Waiting for the deduplication garbage collection job to complete. |
2165 | 正在初始化删除重复作业。 |
Initializing the deduplication job. |
2166 | 运行重复项清除工作。 |
Running the deduplication job. |
2167 | 取消重复项清除工作。 |
Canceling the deduplication job. |
2168 | 正在等待删除重复完成。 |
Waiting for the deduplication to complete. |
2169 | 初始化重复项清除的擦除工作。 |
Initializing the deduplication scrubbing job. |
2170 | 运行重复项清除的擦除工作。 |
Running the deduplication scrubbing job. |
2171 | 取消重复项清除的擦除工作。 |
Canceling the deduplication scrubbing job. |
2172 | 等待重复项清除的擦除工作完成。 |
Waiting for the deduplication scrubbing job to complete. |
2173 | 打开损坏的日志文件。 |
Opening a corruption log file. |
2174 | 读取损坏的日志文件。 |
Reading a corruption log file. |
2175 | 正在向损坏的日志文件中写入项目。 |
Writing an entry to a corruption log file. |
2176 | 枚举损坏的日志文件。 |
Enumerating corruption log files. |
2206 | 创建区块存储的区块顺序。 |
Creating a chunk store chunk sequence. |
2207 | 正在向区块存储序列中添加区块。 |
Adding a chunk to a chunk store sequence. |
2208 | 正在完成区块存储序列的创建。 |
Completing creation of a chunk store sequence. |
2209 | 正在读取区块存储序列。 |
Reading a chunk store sequence. |
2210 | 正在继续区块存储序列。 |
Continuing a chunk store sequence. |
2211 | 正在中止区块存储序列。 |
Aborting a chunk store sequence. |
2212 | 初始化重复项清除的分析工作。 |
Initializing the deduplication analysis job. |
2213 | 运行重复项清除的分析工作。 |
Running the deduplication analysis job. |
2214 | 取消重复项清除的分析工作。 |
Canceling the deduplication analysis job. |
2215 | 等待重复项清除的分析工作完成。 |
Waiting for the deduplication analysis job to complete. |
2216 | 修复区块存储容器标头。 |
Repair chunk store container header. |
2217 | 修复区块存储容器重定向表。 |
Repair chunk store container redirection table. |
2218 | 修复区块存储区块。 |
Repair chunk store chunk. |
2219 | 克隆区块存储容器。 |
Clone chunk store container. |
2220 | 擦除区块存储。 |
Scrubbing chunk store. |
2221 | 检测损坏存储中的损坏项。 |
Detecting corruption store corruptions. |
2222 | 加载重复项清除损坏日志。 |
Loading the deduplication corruption logs. |
2223 | 清理重复项清除损坏日志。 |
Cleaning up the deduplication corruption logs. |
2224 | 确定受区块存储损坏影响的用户文件集。 |
Determining the set of user files affected by chunk store corruptions. |
2225 | 报告损坏。 |
Reporting corruptions. |
2226 | 评估重复项清除擦除工作的内存要求。 |
Estimating memory requirement for the deduplication scrubbing job. |
2227 | 已经启动深入垃圾回收初始化。 |
Deep garbage collection initialization has started. |
2228 | 正在流映射容器上启动深入垃圾回收。 |
Starting deep garbage collection on stream map containers. |
2229 | 正在数据容器上启动深入垃圾回收。 |
Starting deep garbage collection on data containers. |
2230 | 初始化容器上的位图 |
Initialize bitmaps on containers |
2231 | 扫描重分析点索引以确定当前参考哪个流映射。 |
Scanning the reparse point index to determine which stream map is being referenced. |
2232 | 保存删除位图。 |
Saving deletion bitmap. |
2233 | 扫描流映射容器以标记参考区块。 |
Scan the stream map containers to mark referenced chunks. |
2234 | 将位图转化成区块删除日志 |
Convert bitmap to chunk delete log |
2235 | 压缩数据容器 |
Compact Data Containers |
2236 | 压缩流映射容器 |
Compact Stream Map Containers |
2237 | 更改区块存储容器版本。 |
Change a chunk store container generation. |
2238 | 启动更改日志记录。 |
Start change logging. |
2239 | 结束更改日志记录。 |
Stop change logging. |
2240 | 添加合并目标区块存储容器。 |
Add a merged target chunk store container. |
2241 | 正在处理暂时删除的区块。 |
Processing tentatively deleted chunks. |
2242 | 检查区块存储版本。 |
Check version of chunk store. |
2243 | 正在初始化损坏表。 |
Initializing the corruption table. |
2244 | 正在填写损坏表。 |
Writing out the corruption table. |
2245 | 正在删除损坏表文件。 |
Deleting the corruption table file. |
2246 | 正在修复损坏。 |
Repairing corruptions. |
2247 | 正在使用新日志更新损坏表。 |
Updating corruption table with new logs. |
2248 | 正在破坏区块存储。 |
Destroying chunk store. |
2249 | 将区块存储标记为已删除。 |
Marking chunk store as deleted. |
2250 | 正在将损坏条目插入表中。 |
Inserting corruption entry into table. |
2251 | 正在检查区块存储一致性。 |
Checking chunk store consistency. |
2252 | 正在更新区块存储文件列表。 |
Updating a chunk store file list. |
2253 | 正在从冗余恢复区块存储文件列表。 |
Recovering a chunk store file list from redundancy. |
2254 | 正在向区块存储文件列表中添加条目。 |
Adding an entry to a chunk store file list. |
2255 | 正在替换区块存储文件列表中的条目。 |
Replacing an entry in a chunk store file list. |
2256 | 正在删除区块存储文件列表中的条目。 |
Deleting an entry in a chunk store file list. |
2257 | 正在读取区块存储文件列表。 |
Reading a chunk store file list. |
2258 | 正在读取区块存储容器目录文件。 |
Reading a chunk store container directory file. |
2259 | 正在写入区块存储容器目录文件。 |
Writing a chunk store container directory file. |
2260 | 正在删除区块存储容器目录文件。 |
Deleting a chunk store container directory file. |
2261 | 正在为区块存储容器文件设置文件系统分配。 |
Setting FileSystem allocation for chunk store container file. |
2262 | 正在初始化重复数据删除取消优化作业。 |
Initializing the deduplication unoptimization job. |
2263 | 正在运行重复数据删除取消优化作业。 |
Running the deduplication unoptimization job. |
2264 | 正在还原数据重复删除文件 |
Restoring dedup file |
2265 | 正在读取数据重复删除信息 |
Reading dedup information |
2266 | 正在生成容器列表 |
Building container list |
2267 | 正在生成读取计划 |
Building read plan |
2268 | 正在执行读取计划 |
Executing read plan |
2269 | 运行深入清理 |
Running deep scrubbing |
2270 | 深入清理期间扫描重分析点索引 |
Scanning reparse point index during deep scrub |
2271 | 深入清理期间记录重分析点 |
Logging reparse point during deep scrub |
2272 | 深入清理期间扫描流映射容器 |
Scanning stream map containers during deep scrub |
2273 | 清理流映射容器 |
Scrubbing a stream map container |
2274 | 深入清理期间记录流映射的条目 |
Logging a stream map's entries during deep scrub |
2275 | 深入清理期间读取容器的重定向表 |
Reading a container's redirection table during deep scrub |
2276 | 深入清理期间扫描数据容器 |
Scanning data containers during deep scrub |
2277 | 清理数据容器 |
Scrubbing a data container |
2278 | 清理数据区块 |
Scrubbing a data chunk |
2279 | 验证 DC 哈希链接的 SM 入口 |
Verifying SM entry to DC hash link |
2280 | 深入清理期间进行记录 |
Logging a record during deep scrub |
2281 | 深入清理期间写入一批日志记录 |
Writing a batch of log records during deep scrub |
2282 | 正在完成深入清理临时日志 |
Finalizing a deep scrub temporary log |
2283 | 正在深入清理日志管理器日志记录 |
Deep scrubbing log manager log record |
2284 | 正在完成深入清理日志管理器 |
Finalizing deep scrub log manager |
2285 | 正在初始化深入清理区块索引表 |
Initializing deep scrub chunk index table |
2286 | 正在向深入清理区块索引表中插入区块 |
Inserting a chunk into deep scrub chunk index table |
2287 | 正在从深入清理区块索引表中查找区块 |
Looking up a chunk from deep scrub chunk index table |
2288 | 在深入清理期间重构区块索引表 |
Rebuilding a chunk index table during deep scrub |
2289 | 正在重置深入清理记录器缓存 |
Resetting the deep scrubbing logger cache |
2290 | 正在重置深入清理日志管理器 |
Resetting the deep scrubbing log manager |
2291 | 深入清理期间扫描热点容器 |
Scanning hotspot containers during deep scrub |
2292 | 正在清理热点容器 |
Scrubbing a hotspot container |
2293 | 正在扫描热点表 |
Scrubbing the hotspot table |
2294 | 正在清理删除重复深入清理损坏日志 |
Cleaning up the deduplication deep scrub corruption logs |
2295 | 正在计算删除重复文件元数据 |
Computing deduplication file metadata |
2296 | 深入清理期间扫描撤回位图 |
Scanning recall bitmap during deep scrub |
2297 | 正在加载用户文件的热度地图 |
Loading a heat map for a user file |
2298 | 正在保存用户文件的热度地图 |
Saving a heat map for a user file |
2299 | 正在将热区块插入到区块流中。 |
Inserting a hot chunk to a chunk stream. |
2300 | 正在删除用户文件的热度地图 |
Deleting a heat map for a user file |
2301 | 创建卷影副本集。 |
Creating shadow copy set. |
2302 | 初始化扫描以进行优化。 |
Initializing scan for optimization. |
2303 | 正在扫描 NTFS USN 日志 |
Scanning the NTFS USN journal |
2304 | 正在初始化 USN 扫描仪 |
Initializing the USN scanner |
2305 | 启动新的数据块区存储会话 |
Start a new data chunkstore session |
2306 | 提交数据块区存储会话 |
commit a data chunkstore session |
2307 | 正在初始化重复数据删除数据端口作业。 |
Initializing the deduplication data port job. |
2308 | 正在运行重复数据删除数据端口作业。 |
Running the deduplication data port job. |
2309 | 正在取消重复数据删除数据端口作业。 |
Canceling the deduplication data port job. |
2310 | 正在等待重复数据删除数据端口作业完成。 |
Waiting for the deduplication data port job to complete. |
2311 | 查找区块请求。 |
Lookup chunks request. |
2312 | 插入区块请求。 |
Insert chunks request. |
2313 | 提交流映射请求。 |
Commit stream maps request. |
2314 | 获取流请求。 |
Get streams request. |
2315 | 获取区块请求。 |
Get chunks request. |
2401 | 正在初始化工作负载管理器。 |
Initializing workload manager. |
2402 | 正在取消作业。 |
Canceling a job. |
2403 | 将作业排入队列。 |
Enqueue a job. |
2404 | 初始化作业清单。 |
Initialize job manifest. |
2405 | 启动作业主机进程。 |
Launch a job host process. |
2406 | 验证作业主机进程。 |
Validate a job host process. |
2407 | 正在初始化作业。 |
Initializing a job. |
2408 | 终止作业主机进程。 |
Terminate a job host process. |
2409 | 正在取消初始化工作负荷管理器。 |
Uninitializing workload manager. |
2410 | 正在与作业握手。 |
Handshaking with a job. |
2411 | 作业完成回调。 |
Job completion callback. |
2412 | 正在运行作业。 |
Running a job. |
2413 | 正在检查 CSV 卷的所有权。 |
Checking ownership of Csv volume. |
2414 | 正在添加要监视的 CSV 卷。 |
Adding Csv volume for monitoring. |
5001 | TRUE |
TRUE |
5002 | FALSE |
FALSE |
5003 | |
|
5005 | 未知错误 |
Unknown error |
5101 | Data Deduplication Service |
Data Deduplication Service |
5102 | 通过数据删除重复服务,可以对所选卷上的数据使用删除重复和压缩,以便优化使用的磁盘空间。如果停止此服务,则不再进行优化,但是仍然可以继续访问已经优化的数据。 |
The Data Deduplication service enables the deduplication and compression of data on selected volumes in order to optimize disk space used. If this service is stopped, optimization will no longer occur but access to already optimized data will continue to function. |
5105 | Dedup |
Dedup |
5106 | 重复数据删除筛选器驱动程序能够对已复制文件启用读/写 I/O。 |
The Data Deduplication filter driver enables read/write I/O to deduplicated files. |
5201 | 卷 %s 上的区块存储,如果你使用的是优化备份,请选择此选项。 |
The chunk store on volume %s, Select this if you are using optimized backup. |
5202 | 卷 %s 上的重复数据删除配置 |
Data deduplication configuration on volume %s |
5203 | Data Deduplication Volume Shadow Copy Service |
Data Deduplication Volume Shadow Copy Service |
5204 | 重复数据删除 VSS 编写器已指导备份应用程序使用重复数据备份卷。 |
Data Deduplication VSS writer guided backup applications to back up volumes with deduplication. |
5205 | 卷 %s 上的重复数据删除状态 |
Data deduplication state on volume %s |
5301 | 重复数据删除优化 |
Data deduplication optimization |
5302 | 重复数据删除垃圾回收 |
Data deduplication garbage collection |
5303 | 重复数据删除清理 |
Data deduplication scrubbing |
5304 | 取消重复数据删除优化 |
Data deduplication unoptimization |
5305 | 已排队 |
Queued |
5306 | 正在初始化 |
Initializing |
5307 | 正在运行 |
Running |
5308 | 已完成 |
Completed |
5309 | 等待取消 |
Pending Cancel |
5310 | 已取消 |
Canceled |
5311 | 失败 |
Failed |
5312 | 应在此卷上运行数据重复删除清理作业。 |
Data deduplication scrubbing job should be run on this volume. |
5313 | 检测到不支持的路径,将跳过该路径。 |
An unsupported path was detected and will be skipped. |
5314 | 重复数据删除数据端口 |
Data deduplication dataport |
5401 | 此任务会在启用的所有卷上运行重复数据删除优化作业。 |
This task runs the data deduplication optimization job on all enabled volumes. |
5402 | 此任务会在启用的所有卷上运行重复数据删除垃圾回收作业。 |
This task runs the data deduplication garbage collection job on all enabled volumes. |
5403 | 此任务会在启用的所有卷上运行重复数据删除清理作业。 |
This task runs the data deduplication scrubbing job on all enabled volumes. |
5404 | 此任务会在启用的所有卷上运行重复数据删除取消优化作业。 |
This task runs the data deduplication unoptimization job on all enabled volumes. |
5405 | 此任务在所有已启用的卷上运行重复数据删除数据端口作业。 |
This task runs the data deduplication data port job on all enabled volumes. |
0x00565301 | 区块存储的协调到期。 |
Reconciliation of chunk store is due. |
0x00565302 | 没有与此作业相关的操作。 |
There are no actions associated with this job. |
0x00565303 | 重复数据删除无法在此节点的该 CSV 卷上运行该作业。 |
Data deduplication cannot runing this job on this Csv volume on this node. |
0x00565304 | 重复数据删除无法在此节点的此 Csv 卷上运行此 cmdlet。 |
Data deduplication cannot runing this cmdlet on this Csv volume on this node. |
0x10000001 | 报告 |
Reporting |
0x10000002 | 筛选器 |
Filter |
0x10000003 | 内核模式流存储 |
Kernel mode stream store |
0x10000004 | 内核模式区块存储 |
Kernel mode chunk store |
0x10000005 | 内核模式区块容器 |
Kernel mode chunk container |
0x10000006 | 内核模式文件缓存 |
Kernel mode file cache |
0x30000000 | 信息 |
Info |
0x30000001 | 开始 |
Start |
0x30000002 | 停止 |
Stop |
0x50000003 | 警告 |
Warning |
0x70000001 | 重复数据删除优化任务 |
Data Deduplication Optimization Task |
0x70000002 | 重复数据删除垃圾回收任务 |
Data Deduplication Garbage Collection Task |
0x70000003 | 重复数据删除清理任务 |
Data Deduplication Scrubbing Task |
0x70000004 | 重复数据删除取消优化任务 |
Data Deduplication Unoptimization Task |
0x70000005 | 打开流存储流 |
Open stream store stream |
0x70000006 | 准备分页 IO |
Prepare for paging IO |
0x70000007 | 读取流映射 |
Read stream map |
0x70000008 | 读取区块 |
Read chunks |
0x70000009 | 计算校验和 |
Compute checksum |
0x7000000A | 获取容器条目 |
Get container entry |
0x7000000B | 获取容器的最大版本 |
Get maximum generation for container |
0x7000000C | 打开区块容器 |
Open chunk container |
0x7000000D | 初始化区块容器重定向表 |
Initialize chunk container redirection table |
0x7000000E | 验证区块容器重定向表 |
Validate chunk container redirection table |
0x7000000F | 获取区块容器有效数据长度 |
Get chunk container valid data length |
0x70000010 | 获取区块容器重定向表偏移量 |
Get offset from chunk container redirection table |
0x70000011 | 读取区块容器块 |
Read chunk container block |
0x70000012 | 清除区块容器块 |
Clear chunk container block |
0x70000013 | 复制区块 |
Copy chunk |
0x70000014 | 初始化文件缓存 |
Initialize file cache |
0x70000015 | 映射文件缓存数据 |
Map file cache data |
0x70000016 | 取消固定文件缓存数据 |
Unpin file cache data |
0x70000017 | 复制文件缓存数据 |
Copy file cache data |
0x70000018 | 读取基本文件缓存数据 |
Read underlying file cache data |
0x70000019 | 获取区块容器文件大小 |
Get chunk container file size |
0x7000001A | 固定流映射 |
Pin stream map |
0x7000001B | 固定区块容器 |
Pin chunk container |
0x7000001C | 固定区块 |
Pin chunk |
0x7000001D | 分配池缓冲区 |
Allocate pool buffer |
0x7000001E | 取消固定区块容器 |
Unpin chunk container |
0x7000001F | 取消固定区块 |
Unpin chunk |
0x70000020 | 重复数据删除读取处理 |
Dedup read processing |
0x70000021 | 获取第一个流映射条目 |
Get first stream map entry |
0x70000022 | 读取区块元数据 |
Read chunk metadata |
0x70000023 | 读取区块数据 |
Read chunk data |
0x70000024 | 引用 TlCache 数据 |
Reference TlCache data |
0x70000025 | 从流存储中读取区块数据 |
Read chunk data from stream store |
0x70000026 | 组合区块数据 |
Assemble chunk data |
0x70000027 | 解压缩区块数据 |
Decompress chunk data |
0x70000028 | 将区块数据复制到用户缓冲区 |
Copy chunk data in to user buffer |
0x70000029 | 将区块数据插入到 tlcache |
Insert chunk data in to tlcache |
0x7000002A | 从重复数据删除重新分析点文件中读取数据 |
Read data from dedup reparse point file |
0x7000002B | 准备流映射 |
Prepare stream map |
0x7000002C | 修补清理范围 |
Patch clean ranges |
0x7000002D | 将数据写入到重复数据删除文件 |
Writing data to dedup file |
0x7000002E | 将重复数据删除文件写入请求排入队列中 |
Queue write request on dedup file |
0x7000002F | 对重复数据删除文件执行写入时复制操作 |
Do copy on write work on dedup file |
0x70000030 | 对重复数据删除文件执行完全重新调用 |
Do full recall on dedup file |
0x70000031 | 对重复数据删除文件执行部分重新调用 |
Do partial recall on dedup file |
0x70000032 | 对重复数据删除文件执行虚拟分页读取 |
Do dummy paging read on dedup file |
0x70000033 | 读取清理数据以重新调用文件 |
Read clean data for recalling file |
0x70000034 | 将清理数据正常写入到重复数据删除文件 |
Write clean data to dedup file normally |
0x70000035 | 以分页方式将清理数据写入到重复数据删除文件 |
Write clean data to dedup file paged |
0x70000036 | 使用分页 IO 重新调用重复数据删除文件 |
Recall dedup file using paging Io |
0x70000037 | 在重新调用后刷新重复数据删除文件 |
Flush dedup file after recall |
0x70000038 | 在重新调用重复数据删除文件后更新位图 |
Update bitmap after recall on dedup file |
0x70000039 | 删除重复数据删除重新分析点 |
Delete dedup reparse point |
0x7000003A | 打开重复数据删除文件 |
Open dedup file |
0x7000003B | 锁定以禁止读取用户缓冲区 |
Locking user buffer for read |
0x7000003C | 获取 MDL 系统地址 |
Get system address for MDL |
0x7000003D | 读取清理重复数据删除文件 |
Read clean dedup file |
0x7000003E | 获取范围状态 |
Get range state |
0x7000003F | 获取区块正文 |
Get chunk body |
0x70000040 | 释放区块 |
Release chunk |
0x70000041 | 释放解压缩区块上下文 |
Release decompress chunk context |
0x70000042 | 准备解压缩区块上下文 |
Prepare decompress chunk context |
0x70000043 | 将数据复制到压缩的缓冲区 |
Copy data to compressed buffer |
0x70000044 | 从 TL 缓存中释放数据 |
Release data from TL Cache |
0x70000045 | 将异步读取请求排入队列 |
Queue async read request |
0x80565301 | 找不到请求的对象。 |
The requested object was not found. |
0x80565302 | 为任务计划程序提供的一个(或多个)参数无效。 |
One (or more) of the arguments given to the task scheduler is not valid. |
0x80565303 | 指定的对象已存在。 |
The specified object already exists. |
0x80565304 | 找不到指定的路径。 |
The specified path was not found. |
0x80565305 | 指定的用户无效。 |
The specified user is invalid. |
0x80565306 | 指定的路径无效。 |
The specified path is invalid. |
0x80565307 | 指定的名称无效。 |
The specified name is invalid. |
0x80565308 | 指定的属性超出范围。 |
The specified property is out of range. |
0x80565309 | 没有为服务安装、加载或准备好所需的筛选器驱动程序。 |
A required filter driver is either not installed, not loaded, or not ready for service. |
0x8056530A | 磁盘空间不足,无法执行请求的操作。 |
There is insufficient disk space to perform the requested operation. |
0x8056530B | 不支持指定的卷类型。固定的、支持写入的 NTFS 数据卷以及由 NTFS 数据卷提供支持的 CSV 支持重复数据删除。 |
The specified volume type is not supported. Deduplication is supported on fixed, write-enabled NTFS data volumes and CSV backed by NTFS data volumes. |
0x8056530C | 重复数据删除遇到意外错误。请查看数据删除重复运行事件日志以了解详细信息。 |
Data deduplication encountered an unexpected error. Check the Data Deduplication Operational event log for more information. |
0x8056530D | 指定的扫描日志光标已经过期。 |
The specified scan log cursor has expired. |
0x8056530E | 文件系统可能已损坏。请运行 CHKDSK 实用程序。 |
The file system might be corrupted. Please run the CHKDSK utility. |
0x8056530F | 无法创建卷影副本,或卷影副本被意外删除。 |
A volume shadow copy could not be created or was unexpectedly deleted. |
0x80565310 | 重复数据删除遇到损坏的 XML 配置文件。 |
Data deduplication encountered a corrupted XML configuration file. |
0x80565311 | 重复数据删除服务无法访问全局配置,因为群集服务未运行。 |
The Data Deduplication service could not access the global configuration because the Cluster service is not running. |
0x80565312 | 重复数据删除服务无法访问全局配置,因为尚未安装该配置。 |
The Data Deduplication service could not access the global configuration because it has not been installed yet. |
0x80565313 | 重复数据删除无法访问卷。该卷可能已脱机。 |
Data deduplication failed to access the volume. It may be offline. |
0x80565314 | 模块遇到一个无效参数或一个具有无效值的有效参数,或者找不到预期的模块参数。请查看运行事件日志以了解详细信息。 |
The module encountered an invalid parameter or a valid parameter with an invalid value, or an expected module parameter was not found. Check the operational event log for more information. |
0x80565315 | 试图执行初始化操作,但是初始化已完成。 |
An attempt was made to perform an initialization operation when initialization has already been completed. |
0x80565316 | 试图执行取消初始化操作,但是该操作已完成。 |
An attempt was made to perform an uninitialization operation when that operation has already been completed. |
0x80565317 | 重复数据删除服务检测到某个内部文件夹不安全。要保护该文件夹,请在卷上安装重复数据删除。 |
The Data Deduplication service detected an internal folder that is not secure. To secure the folder, reinstall deduplication on the volume. |
0x80565318 | 数据区块已启动。 |
Data chunking has already been initiated. |
0x80565319 | 已尝试从无效的状态执行操作。 |
An attempt was made to perform an operation from an invalid state. |
0x8056531A | 已尝试在初始化之前执行操作。 |
An attempt was made to perform an operation before initialization. |
0x8056531B | 调用 ::PushBuffer 以继续区块或调用 ::Drain 以枚举任意部分区块。 |
Call ::PushBuffer to continue chunking or ::Drain to enumerate any partial chunks. |
0x8056531C | 重复数据删除服务检测到多个区块存储文件夹。但是,只有一个区块存储文件夹得到允许。要解决此问题,请在卷上重新安装重复数据删除。 |
The Data Deduplication service detected multiple chunk store folders; however, only one chunk store folder is permitted. To fix this issue, reinstall deduplication on the volume. |
0x8056531D | 数据无效。 |
The data is invalid. |
0x8056531E | 该进程处于未知状态。 |
The process is in an unknown state. |
0x8056531F | 该进程未运行。 |
The process is not running. |
0x80565320 | 打开文件时出现错误。 |
There was an error while opening the file. |
0x80565321 | 由于未找到作业,因此无法启动作业进程。 |
The job process could not start because the job was not found. |
0x80565322 | 客户端进程 ID 与已启动的主机进程的 ID 不匹配。 |
The client process ID does not match the ID of the host process that was started. |
0x80565323 | 未针对重复数据删除启用指定的卷。 |
The specified volume is not enabled for deduplication. |
0x80565324 | 零字符区块 ID 无效。 |
A zero-character chunk ID is not valid. |
0x80565325 | 索引已达到最大容量。 |
The index is filled to capacity. |
0x80565327 | 会话已经存在。 |
Session already exists. |
0x80565328 | 不支持所选的压缩格式。 |
The compression format selected is not supported. |
0x80565329 | 压缩的缓冲区大于未压缩的缓冲区。 |
The compressed buffer is larger than the uncompressed buffer. |
0x80565330 | 缓冲区不够大。 |
The buffer is not large enough. |
0x8056533A | 索引擦除日志错误所处位置: 查找、读、写或创建 |
Index Scratch Log Error in: Seek, Read, Write, or Create |
0x8056533B | 作业类型无效。 |
The job type is invalid. |
0x8056533C | 持久性层枚举错误。 |
Persistence layer enumeration error. |
0x8056533D | 已取消操作。 |
The operation was cancelled. |
0x8056533E | 由于此作业所需的内存大于当前能够提供的内存,因此将不会在预定时间运行。 |
This job will not run at the scheduled time because it requires more memory than is currently available. |
0x80565341 | 作业在处于取消或挂起状态时终止。 |
The job was terminated while in a cancel or pending state. |
0x80565342 | 作业在处于握手挂起状态时终止。 |
The job was terminated while in a handshake pending state. |
0x80565343 | 作业由于服务关闭而终止。 |
The job was terminated due to a service shutdown. |
0x80565344 | 作业在启动前即已放弃。 |
The job was abandoned before starting. |
0x80565345 | 作业进程意外退出。 |
The job process exited unexpectedly. |
0x80565346 | 重复数据删除服务检测发现无法压缩或更新容器,原因是其已达到最大生成量。 |
The Data Deduplication service detected that the container cannot be compacted or updated because it has reached the maximum generation version. |
0x80565347 | 损坏日志已达到最大大小。 |
The corruption log has reached its maximum size. |
0x80565348 | 重复数据删除清理作业无法处理损坏日志。 |
The data deduplication scrubbing job failed to process the corruption logs. |
0x80565349 | 重复数据删除无法创建新的区块存储容器文件。为该卷分配更大空间。 |
Data deduplication failed to create new chunk store container files. Allocate more space to the volume. |
0x80565350 | 打开文件时出错,因为文件在使用中。 |
An error occurred while opening the file because the file was in use. |
0x80565351 | 删除文件重复数据时发现错误。现在将跳过该文件。 |
An error was discovered while deduplicating the file. The file is now skipped. |
0x80565352 | 在枚举区块存储中的区块时,文件服务器重复数据删除遇到损坏。 |
File Server Deduplication encountered corruption while enumerating chunks in a chunk store. |
0x80565353 | 扫描日志无效。 |
The scan log is not valid. |
0x80565354 | 由于出现校验和(CRC)不匹配错误,数据无效。 |
The data is invalid due to checksum (CRC) mismatch error. |
0x80565355 | 重复数据删除遇到文件损坏错误。 |
Data deduplication encountered file corruption error. |
0x80565356 | 作业已完成,但出现一些错误。请查看事件日志以了解详细信息。 |
Job completed with some errors. Check event logs for more details. |
0x80565357 | 此卷上找到的区块存储版本不支持重复数据删除。 |
Data deduplication is not supported on the version of the chunk store found on this volume. |
0x80565358 | 重复数据删除在此卷上遇到未知版本的区块存储。 |
Data deduplication encountered an unknown version of chunk store on this volume. |
0x80565359 | 分配给作业的内存低于其运行所需的最低内存量。 |
The job was assigned less memory than the minimum it needs to run. |
0x8056535A | 无法修改数据重复删除作业计划。 |
The data deduplication job schedule cannot be modified. |
0x8056535B | 区块存储容器的有效数据长度未对齐。 |
The valid data length of chunk store container is misaligned. |
0x8056535C | 文件访问被拒绝。 |
File access is denied. |
0x8056535D | 由于损坏的文件太多,重复数据删除作业已停止。 |
Data deduplication job stopped due to too many corrupted files. |
0x8056535E | 由于 BCrypt SHA-512 提供程序中存在内部错误,重复数据删除作业已停止。 |
Data deduplication job stopped due to an internal error in the BCrypt SHA-512 provider. |
0x8056535F | 由于存储协调而停止重复数据删除作业。 |
Data deduplication job stopped for store reconciliation. |
0x80565360 | 由于文件大小,重复数据删除已跳过文件。 |
File skipped for deduplication due to its size. |
0x80565361 | 由于重复数据删除重试限制,已跳过文件。 |
File skipped due to deduplication retry limit. |
0x80565362 | 管道缓冲区缓存已满。 |
The pipeline buffer cache is full. |
0x80565363 | 此卷上已有另一个重复数据删除作业在运行。 |
Another Data deduplication job already running on this volume. |
0x80565364 | 重复数据删除无法在此节点的该 CSV 卷上运行此作业。请尝试在 CSV 卷资源所有者节点上运行该作业。 |
Data deduplication cannot run this job on this Csv volume on this node. Try running the job on the Csv volume resource owner node. |
0x80565365 | 重复数据删除无法在此节点上初始化群集状态。 |
Data deduplication failed to initialize cluster state on this node. |
0x80565366 | 范围优化已被重复数据删除筛选器驱动程序中止。 |
Optimization of the range was aborted by the dedup filter driver. |
0x80565367 | 由于并发 IO 操作,无法执行此操作。 |
The operation could not be performed because of a concurrent IO operation. |
0x80565368 | 重复数据删除遇到意外错误。如果在群集配置中,请验证是否已在所有节点上启用重复数据删除。有关详细信息,请查看重复数据删除操作事件日志。 |
Data deduplication encountered an unexpected error. Verify deduplication is enabled on all nodes if in a cluster configuration. Check the Data Deduplication Operational event log for more information. |
0x80565369 | 只有在维护模式下,才能禁用对已删除重复数据的 CSV 卷的数据访问。有关详细信息,请查看重复数据删除操作事件日志。 |
Data access for data deduplicated CSV volumes can only be disabled when in maintenance mode. Check the Data Deduplication Operational event log for more information. |
0x8056536A | 重复数据删除遇到 IO 设备错误,该错误可能指示存储子系统中存在硬件故障。 |
Data Deduplication encountered an IO device error that may indicate a hardware fault in the storage subsystem. |
0x8056536B | 重复数据删除无法在此节点的此 Csv 卷上运行此 cmdlet。请尝试在 Csv 卷资源所有者节点上运行此 cmdlet。 |
Data deduplication cannot run this cmdlet on this Csv volume on this node. Try running the cmdlet on the Csv volume resource owner node. |
0x8056536C | 滚动群集升级期间不支持重复数据删除作业。 |
Deduplication job not supported during rolling cluster upgrade. |
0x8056536D | 滚动群集升级期间不支持重复数据删除设置。 |
Deduplication setting not supported during rolling cluster upgrade. |
0x8056536E | 数据端口作业未准备好接受请求。 |
Data port job is not ready to accept requests. |
0x8056536F | 由于超出请求计数/大小限制,未接受数据端口请求。 |
Data port request not accepted due to request count/size limit exceeded. |
0x80565370 | 数据端口请求已完成,但有一些错误。请查看事件日志,了解更多详细信息。 |
Data port request completed with some errors. Check event logs for more details. |
0x80565371 | 数据端口请求失败。请查看事件日志,了解更多详细信息。 |
Data port request failed. Check event logs for more details. |
0x80565372 | 访问哈希索引时出现数据端口错误。请查看事件日志,了解更多详细信息。 |
Data port error accessing the hash index. Check event logs for more details. |
0x80565373 | 访问流存储时出现数据端口错误。请查看事件日志,了解更多详细信息。 |
Data port error accessing the stream store. Check event logs for more details. |
0x80565374 | 数据端口文件存根错误。请查看事件日志,了解更多详细信息。 |
Data port file stub error. Check event logs for more details. |
0x80565375 | 数据端口遇到重复数据删除筛选器错误。请查看事件日志,了解更多详细信息。 |
Data port encountered a deduplication filter error. Check event logs for more details. |
0x80565376 | 由于缺少区块,数据端口无法提交流映射。请查看事件日志,了解更多详细信息。 |
Data port cannot commit stream map due to missing chunk. Check event logs for more details. |
0x80565377 | 由于流映射元数据无效,数据端口无法提交流映射。请查看事件日志,了解更多详细信息。 |
Data port cannot commit stream map due to invalid stream map metadata. Check event logs for more details. |
0x80565378 | 由于流映射条目无效,数据端口无法提交流映射。请查看事件日志,了解更多详细信息。 |
Data port cannot commit stream map due to invalid stream map entry. Check event logs for more details. |
0x80565379 | 数据端口无法检索卷的作业接口。请查看事件日志,了解更多详细信息。 |
Data port cannot retrieve job interface for volume. Check event logs for more details. |
0x8056537A | 不支持指定的路径。 |
The specified path is not supported. |
0x8056537B | // 数据端口无法解压缩区块。请查看事件日志,了解更多详细信息。 |
// Data port cannot decompress chunk. Check event logs for more details. |
0x8056537C | 数据端口无法计算块哈希。请查看事件日志,了解更多详细信息。 |
Data port cannot calculate chunk hash. Check event logs for more details. |
0x8056537D | 数据端口无法读取区块流。请查看事件日志,了解更多详细信息。 |
Data port cannot read chunk stream. Check event logs for more details. |
0x8056537E | 目标文件不是已删除重复数据的文件。有关详细信息,请查看事件日志。 |
The target file is not a deduplicated file. Check event logs for more details. |
0x8056537F | 目标文件已部分撤回。有关详细信息,请查看事件日志。 |
The target file is partially recalled. Check event logs for more details. |
0x90000001 | Data Deduplication |
Data Deduplication |
0x90000002 | Application |
Application |
0x91000001 | Data Deduplication Change Events |
Data Deduplication Change Events |
0xB0001000 | 卷“%1”显示为已断开连接,此服务将忽略该卷。你可能需要重新扫描磁盘。错误: %2。%n%3 |
Volume \"%1\" appears as disconnected and it is ignored by the service. You may want to rescan disks. Error: %2.%n%3 |
0xB0001001 | 无法在计算机“%3”上启动具有 CLSID %1 和名称“%2”的 COM 服务器。很可能是因为 CPU 负载过重。错误: %4。%n%5 |
The COM Server with CLSID %1 and name \"%2\" cannot be started on machine \"%3\". Most likely the CPU is under heavy load. Error: %4.%n%5 |
0xB0001002 | 无法在计算机“%3”上启动具有 CLSID %1 和名称“%2”的 COM 服务器。错误: %4。%n%5 |
The COM Server with CLSID %1 and name \"%2\" cannot be started on machine \"%3\". Error: %4.%n%5 |
0xB0001003 | 在安全模式下,无法在计算机“%3”上启动具有 CLSID %1 和名称“%2”的 COM 服务器。无法在安全模式下启动重复数据删除服务。错误: %4。%n%5 |
The COM Server with CLSID %1 and name \"%2\" cannot be started on machine \"%3\" during Safe Mode. The Data Deduplication service cannot start while in safe mode. Error: %4.%n%5 |
0xB0001004 | 未注册重复数据删除所需的关键组件。如果在 Windows 安装期间出现错误,或计算机未安装 Windows Server 2012 或更高版本的重复数据删除服务,则可能会出现这种情况。从计算机“%3”上具有 CLSID %1 和名称“%2”的类中的 CoCreateInstance 返回的错误为 %4。%n%5 |
A critical component required by Data Deduplication is not registered. This might happen if an error occurred during Windows setup, or if the computer does not have the Windows Server 2012 or later version of Deduplication service installed. The error returned from CoCreateInstance on class with CLSID %1 and Name \"%2\" on machine \"%3\" is %4.%n%5 |
0xB0001005 | 由于空闲超时,将关闭重复数据删除服务。%n%1 |
Data Deduplication service is shutting down due to idle timeout.%n%1 |
0xB0001006 | 由于服务控制管理器中的关闭事件,将关闭重复数据删除服务。%n%1 |
Data Deduplication service is shutting down due to shutdown event from the Service Control Manager.%n%1 |
0xB0001007 | 卷“%2”上类型为“%1”的重复数据删除作业已完成,返回代码: %3%n%4 |
Data Deduplication job of type \"%1\" on volume \"%2\" has completed with return code: %3%n%4 |
0xB0001008 | 重复数据删除错误: 在调用例程 %1 时出现意外错误。hr = %2。%n%3 |
Data Deduplication error: Unexpected error calling routine %1. hr = %2.%n%3 |
0xB0001009 | 重复数据删除错误: 意外错误。%n%1 |
Data Deduplication error: Unexpected error.%n%1 |
0xB000100A | 重复数据删除警告: %1%n错误: %2。%n%3 |
Data Deduplication warning: %1%nError: %2.%n%3 |
0xB000100B | 重复数据删除错误: 意外 COM 错误 %1: %2。错误代码: %3。%n%4 |
Data Deduplication error: Unexpected COM error %1: %2. Error code: %3.%n%4 |
0xB000100C | 重复数据删除无法访问以下文件或卷:“%1”。该文件或卷当前可能被其他应用程序锁定,或者你可能需要授予该文件或卷的本地系统访问权限。%n%2 |
Data Deduplication was unable to access the following file or volume: \"%1\". This file or volume might be locked by another application right now, or you might need to give Local System access to it.%n%2 |
0xB000100D | 在对“%1”中装载的卷(“%2”)进行扫描期间,重复数据删除遇到意外错误。要了解有关该错误的根本原因的详细信息,请查看应用程序/系统事件日志以了解与这些卷有关的其他重复数据删除服务(VSS 或 VOLSNAP)错误。此外,你还可能需要确保可使用如下 VSSADMIN 命令在这些卷上创建卷影副本: VSSADMIN CREATE SHADOW /For=C:%n%3 |
Data Deduplication encountered an unexpected error during volume scan of volumes mounted at \"%1\" (\"%2\"). To find out more information about the root cause for this error please consult the Application/System event log for other Deduplication service, VSS or VOLSNAP errors related with these volumes. Also, you might want to make sure that you can create shadow copies on these volumes by using the VSSADMIN command like this: VSSADMIN CREATE SHADOW /For=C:%n%3 |
0xB000100E | 重复数据删除无法创建或访问在“%1”中装载的卷(“%2”)的卷影副本。可能的原因包括: 卷影副本配置不正确,磁盘空间不足或系统内存、I/O 或 CPU 负载已到达极限。要了解有关该错误的根本原因的详细信息,请查看应用程序/系统事件日志以了解与这些卷有关的其他重复数据删除服务(VSS 或 VOLSNAP)错误。此外,你还可能需要确保可使用如下 VSSADMIN 命令在这些卷上创建卷影副本: VSSADMIN CREATE SHADOW /For=C:%n%3 |
Data Deduplication was unable to create or access the shadow copy for volumes mounted at \"%1\" (\"%2\"). Possible causes include an improper Shadow Copy configuration, insufficient disk space, or extreme memory, I/O or CPU load of the system. To find out more information about the root cause for this error please consult the Application/System event log for other Deduplication service, VSS or VOLSNAP errors related with these volumes. Also, you might want to make sure that you can create shadow copies on these volumes by using the VSSADMIN command like this: VSSADMIN CREATE SHADOW /For=C:%n%3 |
0xB000100F | 重复数据删除无法访问在“%1”中装载的卷(“%2”)。请确保在运行重复数据删除时不要执行卸载或格式化操作。%n%3 |
Data Deduplication was unable to access volumes mounted at \"%1\" (\"%2\"). Make sure that dismount or format operations do not happen while running deduplication.%n%3 |
0xB0001010 | 重复数据删除无法访问某个文件或卷。详细信息: %n%n%1%n无法访问该卷以执行 I/O 操作,或该卷标记为只读。对于群集卷,这可能是故障转移期间暂时出现的故障。%n%2 |
Data Deduplication was unable to access a file or volume. Details:%n%n%1%n The volume may be inaccessible for I/O operations or marked read-only. In case of a cluster volume, this may be a transient failure during failover.%n%2 |
0xB0001011 | 重复数据删除无法扫描卷“%1”(“%2”)。%n%3 |
Data Deduplication was unable to scan volume \"%1\" (\"%2\").%n%3 |
0xB0001012 | 重复数据删除在文件“%1”中的偏移量“%2”处检测到损坏。如果这种情况持续出现,请使用以前的备份还原数据。损坏详细信息: 结构 = %3,损坏类型 = %4,额外数据 = %5%n%6 |
Data Deduplication detected a corruption on file \"%1\" at offset (\"%2\"). If this condition persists then please restore the data from a previous backup. Corruption details: Structure=%3, Corruption type = %4, Additional data = %5%n%6 |
0xB0001013 | 在卷“%1”上协调区块存储时,重复数据删除遇到错误。错误代码为 %2。将为当前优化作业禁用协调。%n%3 |
Data Deduplication encountered failure while reconciling chunk store on volume \"%1\". The error code was %2. Reconciliation is disabled for the current optimization job.%n%3 |
0xB0001016 | 在执行完全垃圾回收时,重复数据删除遇到损坏的区块容器 %1。将跳过损坏的区块容器。%n%2 |
Data Deduplication encountered corrupted chunk container %1 while performing full garbage collection. The corrupted chunk container is skipped.%n%2 |
0xB0001017 | 重复数据删除无法初始化 %1 下面的更改日志。错误代码为 %2。%n%3 |
Data Deduplication could not initialize change log under %1. The error code was %2.%n%3 |
0xB0001018 | 重复数据删除服务无法将区块容器 %1 标记为已协调。错误代码为 %2。%n%3 |
Data Deduplication service could not mark chunk container %1 as reconciled. The error code was %2.%n%3 |
0xB0001019 | 重复数据删除配置文件已损坏。可能需要使用备份还原系统或卷。%n%1 |
A Data Deduplication configuration file is corrupted. The system or volume may need to be restored from backup.%n%1 |
0xB000101A | 由于磁盘已满错误,重复数据删除无法在卷“%1”上保存某个配置存储: 如果磁盘已满,请对其进行清理(扩展卷或删除部分文件)。如果磁盘未满,但卷根目录上具有硬配额,请删除、禁用或增加此配额。%n%2 |
Data Deduplication was unable to save one of the configuration stores on volume \"%1\" due to a disk-full error: If the disk is full, please clean it up (extend the volume or delete some files). If the disk is not full, but there is a hard quota on the volume root, please delete, disable or increase this quota.%n%2 |
0xB000101B | 由于群集服务未运行,重复数据删除无法访问全局配置。请启动群集服务并重试该操作。%n%1 |
Data Deduplication could not access global configuration since the cluster service is not running. Please start the cluster service and retry the operation.%n%1 |
0xB000101C | 在生成存储报告期间,删除了卷影副本“%1”。为卷“%2”配置的卷影副本存储区域可能不足。重复数据删除无法处理该卷。%n%3 |
Shadow copy \"%1\" was deleted during storage report generation. Volume \"%2\" might be configured with inadequate shadow copy storage area. Data Deduplication could not process this volume.%n%3 |
0xB000101D | 在重试 %2 分钟后,为卷“%1”创建卷影副本失败,因为正在创建其他卷影副本。请将重复数据删除重新安排在不太忙的时间。%n%3 |
Shadow copy creation failed for volume \"%1\" after retrying for %2 minutes because other shadow copies were being created. Reschedule the Data Deduplication for a less busy time.%n%3 |
0xB000101E | 卷“%1”不支持卷影复制。可能从系统中删除了该卷。重复数据删除服务无法处理该卷。%n%2 |
Volume \"%1\" is not supported for shadow copy. It is possible that the volume was removed from the system. Data Deduplication service could not process this volume.%n%2 |
0xB000101F | 已从系统中删除卷“%1”。%n%2 |
The volume \"%1\" has been deleted or removed from the system.%n%2 |
0xB0001020 | 无法为卷“%1”创建卷影副本,错误为 %2。为该卷配置的卷影副本存储区域可能不足。文件服务器重复数据删除服务无法处理该卷。%n%3 |
Shadow copy creation failed for volume \"%1\" with error %2. The volume might be configured with inadequate shadow copy storage area. File Serve Deduplication service could not process this volume.%n%3 |
0xB0001021 | 卷“%1”上的文件系统可能已损坏。请运行 CHKDSK 实用程序以检查并修复文件系统。%n%2 |
The file system on volume \"%1\" is potentially corrupted. Please run the CHKDSK utility to verify and fix the file system.%n%2 |
0xB0001022 | 重复数据删除检测到不安全的内部文件夹。要保护该文件夹,请在卷上重新安装重复数据删除。%n%1 |
Data Deduplication detected an insecure internal folder. To secure the folder, reinstall deduplication on the volume again.%n%1 |
0xB0001023 | 重复数据删除在卷上找不到区块存储。%n%1 |
Data Deduplication could not find a chunk store on the volume.%n%1 |
0xB0001024 | 重复数据删除检测到多个区块存储文件夹。要进行恢复,请在卷上重新安装重复数据删除。%n%1 |
Data Deduplication detected multiple chunk store folders. To recover, reinstall deduplication on the volume.%n%1 |
0xB0001025 | 重复数据删除检测到冲突的区块存储文件夹:“%1”和“%2”。%n%3 |
Data Deduplication detected conflicting chunk store folders: \"%1\" and \"%2\".%n%3 |
0xB0001026 | 数据无效。%n%1 |
The data is invalid.%n%1 |
0xB0001027 | 重复数据删除计划程序无法初始化,错误为“%1”。%n%2 |
Data Deduplication scheduler failed to initialize with error \"%1\".%n%2 |
0xB0001028 | 重复数据删除无法在卷“%2”上验证作业类型“%1”,错误为“%3”。%n%4 |
Data Deduplication failed to validate job type \"%1\" on volume \"%2\" with error \"%3\".%n%4 |
0xB0001029 | 重复数据删除无法在卷“%2”上启动作业类型“%1”,错误为“%3”。%n%4 |
Data Deduplication failed to start job type \"%1\" on volume \"%2\" with error \"%3\".%n%4 |
0xB000102C | 重复数据删除检测到卷“%2”上的作业类型“%1”使用的内存太多。分配了 %3 MB,但使用了 %4 MB。%n%5 |
Data Deduplication detected job type \"%1\" on volume \"%2\" uses too much memory. %3 MB is assigned. %4 MB is used.%n%5 |
0xB000102D | 重复数据删除检测到卷“%2”上的作业类型“%1”使用的内存已降到理想的水平。%n%3 |
Data Deduplication detected job type \"%1\" on volume \"%2\" memory usage has dropped to desirable level.%n%3 |
0xB000102E | 重复数据删除取消了卷“%2”上的作业类型“%1”。它使用的内存比分配的内存多得多。%n%3 |
Data Deduplication cancelled job type \"%1\" on volume \"%2\". It uses too much memory than the amount assigned to it.%n%3 |
0xB000102F | 重复数据删除取消了卷“%2”上的作业类型“%1”。计算机或作业中的内存资源不足。%n%3 |
Data Deduplication cancelled job type \"%1\" on volume \"%2\". Memory resource is running low on the machine or in the job.%n%3 |
0xB0001030 | 卷“%2”上的重复数据删除作业类型“%1”无法向该服务报告完成,错误为: %3。%n%4 |
Data Deduplication job type \"%1\" on volume \"%2\" failed to report completion to the service with error: %3.%n%4 |
0xB0001031 | 重复数据删除检测到无法压缩或更新容器,因为它已达到最高版本。%n%1 |
Data Deduplication detected a container cannot be compacted or updated because it has reached the maximum generation.%n%1 |
0xB0001032 | 重复数据删除损坏日志“%1”已损坏。%n%2 |
Data Deduplication corruption log \"%1\" is corrupted.%n%2 |
0xB0001033 | 重复数据删除损坏日志“%1”已达到允许的最大大小“%2”。请运行清理作业以处理损坏日志。在处理该日志后,才会报告更多损坏。%n%3 |
Data Deduplication corruption log \"%1\" has reached maximum allowed size \"%2\". Please run scrubbing job to process corruption log. No more corruptions will be reported until the log is processed.%n%3 |
0xB0001034 | 重复数据删除损坏日志“%1”已达到允许的最大大小“%2”。在处理该日志后,才会报告更多损坏。%n%3 |
Data Deduplication corruption log \"%1\" has reached maximum allowed size \"%2\". No more corruptions will be reported until the log is processed.%n%3 |
0xB0001035 | 重复数据删除计划程序无法取消初始化,错误为“%1”。%n%2 |
Data Deduplication scheduler failed to uninitialize with error \"%1\".%n%2 |
0xB0001036 | 重复数据删除检测到无法在区块存储中创建新的容器,因为可用的容器 ID 不足。%n%1 |
Data Deduplication detected a new container could not be created in a chunk store because it ran out of available container Id.%n%1 |
0xB0001037 | 卷“%1”上的重复数据删除完全垃圾回收第 1 阶段(清理与文件相关的元数据)失败,错误为: %2。该作业将继续执行第 2 阶段(数据区块清理)。%n%3 |
Data Deduplication full garbage collection phase 1 (cleaning file related metadata) on volume \"%1\" failed with error: %2. The job will continue with phase 2 execution (data chunk cleanup).%n%3 |
0xB0001039 | 重复数据删除完全垃圾回收无法实现最大空间回收,因为无法清理数据容器 %1 的删除日志。%n%2 |
Data Deduplication full garbage collection could not achieve maximum space reclamation because delete logs for data container %1 could not be cleaned up.%n%2 |
0xB000103A | 由于超过了卷 %1 上的 FSRM 配额限制,无法删除某些文件的重复数据。跳过的文件可能是达到或接近配额限制的文件夹中的压缩或稀疏文件。请考虑提高达到或接近配额限制的文件夹的配额限制。%n%2 |
Some files could not be deduplicated because of FSRM Quota violations on volume %1. Files skipped are likely compressed or sparse files in folders which are at quota or close to their quota limit. Please consider increasing the quota limit for folders that are at their quota limit or close to it.%n%2 |
0xB000103B | 由于出现严重错误 %3,重复数据删除无法删除文件 %1“%2”的重复数据%n%4 |
Data Deduplication failed to dedup file %1 \"%2\" due to fatal error %3%n%4 |
0xB000103C | 在访问区块存储中的文件时,重复数据删除遇到损坏。%n%1 |
Data Deduplication encountered corruption while accessing a file in chunk store.%n%1 |
0xB000103D | 在访问区块存储中的文件时,重复数据删除遇到损坏。请运行清理作业以进行诊断和修复。%n%1 |
Data Deduplication encountered corruption while accessing a file in chunk store. Please run scrubbing job for diagnosis and repair.%n%1 |
0xB000103E | 在访问区块存储中的文件时,重复数据删除遇到校验和(CRC)不匹配错误。请运行清理作业以进行诊断和修复。%n%1 |
Data Deduplication encountered checksum (CRC) mismatch error while accessing a file in chunk store. Please run scrubbing job for diagnosis and repair.%n%1 |
0xB000103F | 重复数据删除无法访问文件 %1,因为文件在使用中。%n%2 |
Data Deduplication is unable to access file %1 because the file is in use.%n%2 |
0xB0001040 | 在访问区块存储中的文件时,重复数据删除遇到校验和(CRC)不匹配错误。%n%1 |
Data Deduplication encountered checksum (CRC) mismatch error while accessing a file in chunk store.%n%1 |
0xB0001041 | 重复数据删除无法运行卷 %1 上的作业,因为重复数据删除存储版本兼容性检查失败,错误为 %2。%n%3 |
Data Deduplication cannot run the job on volume %1 because the dedup store version compatiblity check failed with error %2.%n%3 |
0xB0001042 | 重复数据删除已禁用卷 %1,因为该卷发现的损坏过多。请对该卷运行深入清理。%n%2 |
Data Deduplication has disabled the volume %1 because it has discovered too many corruptions. Please run deep scrubbing on the volume.%n%2 |
0xB0001043 | 重复数据删除在 %1 存储中检测到损坏的损坏元数据文件。请对该卷运行深入清理。%n%2 |
Data Deduplication has detected a corrupt corruption metadata file on the store at %1. Please run deep scrubbing on the volume.%n%2 |
0xB0001044 | 无法为卷“%1”启用重复数据删除。重复数据删除不支持大于 64TB 的卷。 错误: %2。%n%3 |
Volume \"%1\" cannot be enabled for Data Deduplication. Data Deduplication does not support volumes larger than 64TB. Error: %2.%n%3 |
0xB0001045 | 无法在 SIS 卷“%1”上启用重复数据删除。错误: %2。%n%3 |
Data Deduplication cannot be enabled on SIS volume \"%1\". Error: %2.%n%3 |
0xB0001046 | 文件系统已配置为区分大小写的文件/文件夹名称。重复数据删除不支持区分大小写的文件系统模式。%n%1 |
File-system is configured for case-sensitive file/folder names. Data Deduplication does not support case-sensitive file-system mode.%n%1 |
0xB0001049 | 由于磁盘空间不足,重复数据删除已将清理作业转变为只读模式。%n%1 |
Data Deduplication changed scrubbing job to read-only due to insufficient disk space.%n%1 |
0xB000104B | 由于缺少容器或容器损坏,重复数据删除已禁用卷 %1。请对该卷运行深入清理。%n%2 |
Data Deduplication has disabled the volume %1 because there are missing or corrupt containers. Please run deep scrubbing on the volume.%n%2 |
0xB000104D | 重复数据删除遇到磁盘已满错误。%n%1 |
Data Deduplication encountered a disk-full error.%n%1 |
0xB000104E | 由于磁盘空间不足,无法在卷“%1”上运行重复数据删除作业。%n%2 |
Data Deduplication job cannot run on volume \"%1\" due to insufficient disk space.%n%2 |
0xB000104F | 无法在脱机卷“%1”上运行重复数据删除作业。%n%2 |
Data Deduplication job cannot run on offline volume \"%1\".%n%2 |
0xB0001050 | 数据重复删除恢复了损坏或缺少的文件。%n%1 |
Data Deduplication recovered a corrupt or missing file.%n%1 |
0xB0001051 | 数据重复删除遇到损坏的元数据文件。要纠正该问题,请使用 -Full 选项在受影响的卷上计划或手动运行垃圾回收作业。%n%1 |
Data Deduplication encountered a corrupted metadata file. To correct the problem, schedule or manually run a Garbage Collection job on the affected volume with the -Full option.%n%1 |
0xB0001052 | 在更新容器时,数据重复删除遇到标头损坏的区块 %1。损坏的区块将复制到新容器 %2。%n%3 |
Data Deduplication encountered chunk %1 with corrupted header while updating container. The corrupted chunk is replicated to the new container %2.%n%3 |
0xB0001053 | 在更新容器时,数据重复删除遇到标头暂时损坏的区块 %1。损坏的区块不会复制到新容器 %2。%n%3 |
Data Deduplication encountered chunk %1 with transient header corruption while updating container. The corrupted chunk is NOT replicated to the new container %2.%n%3 |
0xB0001054 | 重复数据删除功能无法从文件 %1 中读取区块容器重定向表,错误为 %2。%n%3 |
Data Deduplication failed to read chunk container redirection table from file %1 with error %2.%n%3 |
0xB0001055 | 重复数据删除功能无法初始化文件 %1 中用于深入清理的重分析点索引表,错误为 %2。%n%3 |
Data Deduplication failed to initialize reparse point index table for deep scrubbing from file %1 with error %2.%n%3 |
0xB0001056 | 重复数据删除功能无法在卷 %2 上深入清理容器文件 %1,错误为 %3。%n%4 |
Data Deduplication failed to deep scrub container file %1 on volume %2 with error %3.%n%4 |
0xB0001057 | 重复数据删除功能无法从文件 %1 加载用于深入清理的流映射日志,错误为 %2。%n%3 |
Data Deduplication failed to load stream map log for deep scrubbing from file %1 with error %2.%n%3 |
0xB0001058 | 重复数据删除功能在容器文件 %2 中发现一个重复的本地区块 ID %1。%n%3 |
Data Deduplication found a duplicate local chunk id %1 in container file %2.%n%3 |
0xB0001059 | 已手动取消卷“%2”上的重复数据删除作业类型“%1”。%n%3 |
Data Deduplication job type \"%1\" on volume \"%2\" was cancelled manually.%n%3 |
0xB000105A | 已取消卷“%2”上的计划重复数据删除作业类型“%1”。%n%3 |
Scheduled data Deduplication job type \"%1\" on volume \"%2\" was cancelled.%n%3 |
0xB000105D | 卷“%1”上的重复数据删除区块存储统计信息文件已损坏并且将被重置。统计信息将通过随后的作业更新,也可以通过运行 Update-DedupStatus cmdlet 来手动更新。%n%2 |
The Data Deduplication chunk store statistics file on volume \"%1\" is corrupted and will be reset. Statistics will be updated by a subsequent job and can be updated manually by running the Update-DedupStatus cmdlet.%n%2 |
0xB000105E | 卷“%1”上的重复数据删除卷统计信息文件已损坏并且将被重置。统计信息将通过随后的作业更新,也可以通过运行 Update-DedupStatus cmdlet 来手动更新。%n%2 |
The Data Deduplication volume statistics file on volume \"%1\" is corrupted and will be reset. Statistics will be updated by a subsequent job and can be updated manually by running the Update-DedupStatus cmdlet.%n%2 |
0xB000105F | 重复数据删除无法附加到深入清理日志文件 %1 中,错误为 %2。%n%3 |
Data Deduplication failed to append to deep scrubbing log file %1 with error %2.%n%3 |
0xB0001060 | 在存储 %1 上进行深入清理期间重复数据删除遇到错误,错误为 %2。%n%3 |
Data Deduplication encountered a failure during deep scrubbing on store %1 with error %2.%n%3 |
0xB0001061 | 重复数据删除取消了卷“%2”上的作业类型“%1”。该作业违反了 CSV 重复数据删除作业放置策略。%n%3 |
Data Deduplication cancelled job type \"%1\" on volume \"%2\". The job violated Csv dedup job placement policy.%n%3 |
0xB0001062 | 重复数据删除取消了卷“%2”上类型为“%1”的作业。CSV 作业监视器尚未初始化。%n%3 |
Data Deduplication cancelled job type \"%1\" on volume \"%2\". The csv job monitor has been uninitialized.%n%3 |
0xB0001063 | 访问卷上的某个文件时,“重复数据删除”遇到 IO 设备错误。这可能是由于存储子系统中出现硬件故障导致的。%n%1 |
Data Deduplication encountered a IO device error while accessing a file on the volume. This is likely a hardware fault in the storage subsystem.%n%1 |
0xB0001064 | “重复数据删除”遇到意外错误。如果这是一个群集,请验证是否已在该群集的所有节点上启用“重复数据删除”。%n%1 |
Data Deduplication encountered an unexpected error. If this is a cluster, verify Data Deduplication is enabled on all nodes of the cluster.%n%1 |
0xB0001065 | 尝试在非维护模式下对已删除重复数据的 CSV 卷“%1”禁用数据访问。只能在维护模式下对 CSV 卷禁用数据访问。请将该卷置于维护模式,然后重试。%n%2 |
Attempted to disable data access for data deduplicated CSV volume \"%1\" without maintenance mode. Data access can only be disabled for a CSV volume when in maintenance mode. Place volume into maintenance mode and retry.%n%2 |
0xB0001800 | 重复数据删除服务无法取消优化文件“%5%6%7”。错误 %8,“%9”。 |
Data Deduplication service could not unoptimize file \"%5%6%7\". Error %8, \"%9\". |
0xB0001801 | 重复数据删除服务无法在卷 %3 上取消优化过多的文件。未报告某些文件。 |
Data Deduplication service failed to unoptimize too many files %3. Some files are not reported. |
0xB0001802 | 重复数据删除服务在卷 %3 上完成了取消优化操作,未出现任何错误。 |
Data Deduplication service has finished unoptimization on volume %3 with no errors. |
0xB0001803 | 重复数据删除服务在卷 %3 上完成了取消优化操作,出现了 %4 个错误。 |
Data Deduplication service has finished unoptimization on volume %3 with %4 errors. |
0xB0001804 | %1 作业已启动。%n%n卷: %4 (%3)%n可用内存: %5 MB%n可用内核数: %6%n实例数: %7%n每个实例的读取器数: %8%n优先级: %9%nIoThrottle: %10 |
%1 job has started.%n%nVolume: %4 (%3)%nAvailable memory: %5 MB%nAvailable cores: %6%nInstances: %7%nReaders per instance: %8%nPriority: %9%nIoThrottle: %10 |
0xB0001805 | %1 作业已启动。%n%n卷: %4 (%3)%n可用内存: %5 MB%n可用内核数: %6%n优先级: %7%n完全: %8%n卷可用空间(MB): %9 |
%1 job has started.%n%nVolume: %4 (%3)%nAvailable memory: %5 MB%nAvailable cores: %6%nPriority: %7%nFull: %8%nVolume free space (MB): %9 |
0xB0001806 | %1 作业已启动。%n%n卷: %4 (%3)%n可用内存: %5 MB%n优先级: %6%n完全: %7%n只读: %8 |
%1 job has started.%n%nVolume: %4 (%3)%nAvailable memory: %5 MB%nPriority: %6%nFull: %7%nRead-only: %8 |
0xB0001807 | %1 作业已启动。%n%n卷: %4 (%3)%n可用内存: %5 MB%n优先级: %6 |
%1 job has started.%n%nVolume: %4 (%3)%nAvailable memory: %5 MB%nPriority: %6 |
0xB0001809 | %1 作业已完成。%n%n卷: %4 (%3)%n错误代码: %5%n错误消息: %6%n保存率(百分比): %7%n保存空间(MB): %8%n卷已用空间(MB): %9%n卷可用空间(MB): %10%n已优化文件计数: %11%n策略中文件计数: %12%n作业处理空间(MB): %13%n作业运行时间(秒): %18%n作业吞吐量(MB/秒): %19%n改动处理吞吐量(MB/秒): %20 |
%1 job has completed.%n%nVolume: %4 (%3)%nError code: %5%nError message: %6%nSavings rate (percent): %7%nSaved space (MB): %8%nVolume used space (MB): %9%nVolume free space (MB): %10%nOptimized file count: %11%nIn-policy file count: %12%nJob processed space (MB): %13%nJob elapsed time (seconds): %18%nJob throughput (MB/second): %19%nChurn processing throughput (MB/second): %20 |
0xB000180A | %1 作业已完成。%n%n完全: %2%n卷: %5 (%4)%n错误代码: %6%n错误消息: %7%n释放空间(MB): %8%n卷可用空间(MB): %9%n作业运行时间(秒): %10%n作业吞吐量(MB/秒): %11 |
%1 job has completed.%n%nFull: %2%nVolume: %5 (%4)%nError code: %6%nError message: %7%nFreed up space (MB): %8%nVolume free space (MB): %9%nJob elapsed time (seconds): %10%nJob throughput (MB/second): %11 |
0xB000180B | %1 作业已完成。%n%n卷: %4 (%3)%n错误代码: %5%n错误消息: %6 |
%1 job has completed.%n%nVolume: %4 (%3)%nError code: %5%nError message: %6 |
0xB000180C | %1 作业已完成。%n%n完全: %2%n只读: %3%n卷: %6 (%5)%n错误代码: %7%n错误消息: %8%n总损坏计数: %9%n可修复损坏计数: %10%n%n发现损坏时,请在“清理”事件通道中查看更多详细信息。 |
%1 job has completed.%n%nFull: %2%nRead-only: %3%nVolume: %6 (%5)%nError code: %7%nError message: %8%nTotal corruption count: %9%nFixable corruption count: %10%n%nWhen corruptions are found, check more details in Scrubbing event channel. |
0xB000180D | %1 作业已完成。%n%n卷: %4 (%3)%n错误代码: %5%n错误消息: %6%n未优化文件计数: %7%n作业处理空间(MB): %8%n作业运行时间(秒): %9%n作业吞吐量(MB/秒): %10 |
%1 job has completed.%n%nVolume: %4 (%3)%nError code: %5%nError message: %6%nUnoptimized file count: %7%nJob processed space (MB): %8%nJob elapsed time (seconds): %9%nJob throughput (MB/second): %10 |
0xB000180E | %1 作业已排入队列。%n%n卷: %4 (%3)%n系统内存百分比: %5 %n优先级: %6%n计划模式: %7 |
%1 job has been queued.%n%nVolume: %4 (%3)%nSystem memory percent: %5 %nPriority: %6%nSchedule mode: %7 |
0xB000181C | 由于出现以下错误,还原删除了重复数据的文件“%1”失败: %2,“%3”。 |
Restore of deduplicated file \"%1\" failed with the following error: %2, \"%3\". |
0xB000181D | 优先级为 %1 的作业已启动。%n%n卷: %4 (%3)%n文件 ID: %11%n可用内存: %5 MB%n可用内核数: %6%n实例数: %7%n每个实例的读取器数: %8%n优先级: %9%nIoThrottle: %10 |
Priority %1 job has started.%n%nVolume: %4 (%3)%nFile ID: %11%nAvailable memory: %5 MB%nAvailable cores: %6%nInstances: %7%nReaders per instance: %8%nPriority: %9%nIoThrottle: %10 |
0xB000181E | %1 作业已启动。%n%n卷: %4 (%3)%n可用内存: %5 MB%n可用线程: %6%n优先级: %7 |
%1 job has started.%n%nVolume: %4 (%3)%nAvailable memory: %5 MB%nAvailable threads: %6%nPriority: %7 |
0xB000181F | %1 作业已完成。%n%n卷: %4 (%3)%n错误代码: %5%n错误消息: %6%n节省率(百分比): %7%n节省空间(MB): %8%n 卷中已用空间(MB): %9%n卷中可用空间(MB): %10%n优化文件计数: %11%n区块查找计数: %12%n插入区块计数: %13%n插入区块逻辑数据(MB): %14%n插入区块物理数据(MB): %15%n提交流计数: %16%n提交流条目计数: %17%n提交流逻辑数据(MB): %18%n检索到的区块物理数据(MB): %19%n检索到的流逻辑数据(MB): %20%n数据端口时间(秒): %21%n作业已用时间(秒): %22%n入口吞吐量(MB/秒): %23%n出口吞吐量(MB/秒): %24 |
%1 job has completed.%n%nVolume: %4 (%3)%nError code: %5%nError message: %6%nSavings rate (percent): %7%nSaved space (MB): %8%nVolume used space (MB): %9%nVolume free space (MB): %10%nOptimized file count: %11%nChunk lookup count: %12%nInserted chunk count: %13%nInserted chunks logical data (MB): %14%nInserted chunks physical data (MB): %15%nCommitted stream count: %16%nCommitted stream entry count: %17%nCommitted stream logical data (MB): %18%nRetrieved chunks physical data (MB): %19%nRetrieved stream logical data (MB): %20%nDataPort time (seconds): %21%nJob elapsed time (seconds): %22%nIngress throughput (MB/second): %23%nEgress throughput (MB/second): %24 |
0xB0001821 | 重复数据删除检测到在群集部署中,为区块索引缓存卷指定了非群集卷。不推荐此配置,因为可能导致故障转移后的作业失败。%n%n卷: %3 (%2) |
Data Deduplication detected a non-clustered volume specified for the chunk index cache volume in a clustered deployment. The configuration is not recommended because it may result in job failures after failover.%n%nVolume: %3 (%2) |
0xB0002000 | 重复数据删除检测到卷“%2”上的作业类型“%1”工作集较低。提交大小比率为 %3。%n%4 |
Data Deduplication detected job type \"%1\" on volume \"%2\" working set is low. Ratio to commit size is %3.%n%4 |
0xB0002001 | 重复数据删除检测到卷“%2”上的作业类型“%1”工作集已恢复到理想的水平。%n%3 |
Data Deduplication detected job type \"%1\" on volume \"%2\" working set has recovered to desirable level.%n%3 |
0xB0002002 | 重复数据删除检测到卷“%2”上的作业类型“%1”页面错误速率较高。速率为 %3 个页面错误/秒。%n%4 |
Data Deduplication detected job type \"%1\" on volume \"%2\" page fault rate is high. The rate is %3 page faults per second.%n%4 |
0xB0002003 | 重复数据删除检测到卷“%2”上的作业类型“%1”页面错误速率已降到理想的水平。速率为 %3 个页面错误/秒。%n%4 |
Data Deduplication detected job type \"%1\" on volume \"%2\" page fault rate has lowered to desirable level. The rate is %3 page faults per second.%n%4 |
0xB0002004 | 由于出现非严重错误 %3%n%4,重复数据删除无法删除具有文件 ID %2 的文件“%1”的重复数据。%n%n注意: 你可以针对相关文件运行 FSUTIL FILE QUERYFILENAMEBYID 命令以检索文件的名称。 |
Data Deduplication failed to dedup file \"%1\" with file ID %2 due to non-fatal error %3%n%4.%n%nNote: You can retrieve the file name by running the command FSUTIL FILE QUERYFILENAMEBYID on the file in question. |
0xB000200C | 重复数据删除已中止一个组提交会话。%n%n文件计数: %1%n错误: %2%n%3 |
Data Deduplication has aborted a group commit session.%n%nFile count: %1%nError: %2%n%3 |
0xB000201C | 无法打开重复数据删除设置注册表项 |
Fail to open dedup setting registry key |
0xB000201D | 由于机会锁定中断,重复数据删除无法删除文件 ID 为 %2 的文件“%1”%n%3 |
Data Deduplication failed to dedup file \"%1\" with file ID %2 due to oplock break%n%3 |
0xB000201E | 由于出现错误 %2,重复数据删除无法从文件 %1 中加载热点表。%n%3 |
Data Deduplication failed to load hotspot table from file %1 due to error %2.%n%3 |
0xB000201F | 重复数据删除无法初始化机会锁定。%n%n文件 ID: %1%n文件名:“%2”%n错误: %3%n%4 |
Data Deduplication failed to initialize oplock.%n%nFile ID: %1%nFile name: \"%2\"%nError: %3%n%4 |
0xB0002020 | 重复数据删除在卷 %1 上运行作业时检测到无效物理扇区大小 %2。使用默认值 %3。%n%4 |
Data Deduplication while running job on volume %1 detected invalid physical sector size %2. Using default value %3.%n%4 |
0xB0002021 | 重复数据删除检测到不受支持的区块存储容器。%n%1 |
Data Deduplication detected an unsupported chunk store container.%n%1 |
0xB0002022 | 由于出现错误 %1,重复数据删除无法创建窗口接收任务计划程序停止信息。任务可能会在持续时间限制到期后停止。%n%2 |
Data Deduplication could not create window to receive task scheduler stop message due to error %1. Task(s) may not stop after duration limit.%n%2 |
0xB0002023 | 由于出现错误 %1,重复数据删除无法创建线程轮询任务计划程序停止信息。任务可能会在持续时间限制到期后停止。%n%2 |
Data Deduplication could not create thread to poll for task scheduler stop message due to error %1. Task(s) may not stop after duration limit.%n%2 |
0xB0002024 | 试图执行初始化操作,但是初始化已完成。%n%1 |
An attempt was made to perform an initialization operation when initialization has already been completed.%n%1 |
0xB0002028 | 重复数据删除已创建紧急文件 %1。%n%3 |
Data Deduplication created emergency file %1.%n%3 |
0xB0002029 | 重复数据删除无法创建紧急文件 %1,错误为 %2。%n%3 |
Data Deduplication failed to create emergency file %1 with error %2.%n%3 |
0xB000202A | 重复数据删除已删除紧急文件 %1。%n%3 |
Data Deduplication deleted emergency file %1.%n%3 |
0xB000202B | 重复数据删除无法删除紧急文件 %1,错误为 %2。%n%3 |
Data Deduplication failed to delete emergency file %1 with error %2.%n%3 |
0xB000202C | 数据重复删除检测到具有未对齐的有效数据长度的区块存储容器。%n%1 |
Data Deduplication detected a chunk store container with misaligned valid data length.%n%1 |
0xB000202D | 数据重复删除垃圾回收遇到一个删除日志条目,该条目具有流映射 ID %1 的无效流映射签名。%n%2 |
Data Deduplication Garbage Collection encountered a delete log entry with an invalid stream map signature for stream map Id %1.%n%2 |
0xB000202E | 数据重复删除无法初始化操作锁定,因为文件似乎丢失。%n%n文件 ID: %1%n文件名:“%2”%n错误: %3%n%4 |
Data Deduplication failed to initialize oplock as the file appears to be missing.%n%nFile ID: %1%nFile name: \"%2\"%nError: %3%n%4 |
0xB000202F | 重复数据删除跳过太多文件级别错误。每个作业我们最多记录 %1 个文件级别错误。%n%2 |
Data Deduplication skipped too many file-level errors. We will not log more than %1 file-level errors per job.%n%2 |
0xB0002030 | 重复数据删除诊断警告。%n%n%1%n%2 |
Data Deduplication diagnostic warning.%n%n%1%n%2 |
0xB0002031 | 重复数据删除诊断信息。%n%n%1%n%2 |
Data Deduplication diagnostic information.%n%n%1%n%2 |
0xB0002032 | 重复数据删除在标记为删除的容器文件 %3 中找到流映射 ID 为 %2 的文件 %1。%n%4 |
Data Deduplication found file %1 with a stream map id %2 in container file %3 marked for deletion.%n%4 |
0xB0002033 | 无法在卷“%2”上将类型为“%1”的作业排入队列。%n%3 |
Failed to enqueue job of type \"%1\" on volume \"%2\".%n%3 |
0xB0002034 | 在卷“%2”上终止作业类型为“%1”的作业主机进程时出错(进程 ID: %3)。%n%4 |
Error terminating job host process for job type \"%1\" on volume \"%2\" (process id: %3).%n%4 |
0xB0002035 | 更新容器时重复数据删除遇到损坏的区块 %1。无法修复的损坏数据将按原样复制到新容器 %2。%n%3 |
Data Deduplication encountered corrupted chunk %1 while updating container. Corrupted data that cannot be repaired will be copied as-is to the new container %2.%n%3 |
0xB0002036 | 卷“%2”上的重复数据删除作业类型“%1”无法正常退出。%n%3 |
Data Deduplication job type \"%1\" on volume \"%2\" failed to exit gracefully.%n%3 |
0xB0002037 | 卷“%2”上的作业类型“%1”的重复数据删除作业主机意外退出。%n%3 |
Data Deduplication job host for job type \"%1\" on volume \"%2\" exited unexpectedly.%n%3 |
0xB0002038 | 由于出现错误 %2,重复数据删除无法加载 %1 存储中的损坏元数据文件。请对该卷运行深入清理。%n%3 |
Data Deduplication has failed to load corruption metadata file on the store at %1 due to error %2. Please run deep scrubbing on the volume.%n%3 |
0xB0002039 | 在处理文件 %3 时,卷“%1”上的重复数据删除完全垃圾回收第 1 阶段遇到错误 %2。由于在出现文件错误时无法安全地继续执行与文件相关的元数据垃圾回收,因此,需要中止第 1 阶段。%n%4 |
Data Deduplication full garbage collection phase 1 on volume \"%1\" encountered an error %2 while processing file %3. Phase 1 will need to be aborted since garbage collection of file-related metadata is unsafe to continue on file errors.%n%4 |
0xB000203A | 由于出现错误 %2,重复数据删除无法处理损坏元数据文件 %1。请对该卷运行深入清理。%n%3 |
Data Deduplication has failed to process corruption metadata file %1 due to error %2. Please run deep scrubbing on the volume.%n%3 |
0xB000203B | 由于出现错误 %2,重复数据删除无法加载损坏的元数据文件 %1。正在删除该文件并继续操作。%n%3 |
Data Deduplication has failed to load a corrupted metadata file %1 due to error %2. Deleting the file and continuing.%n%3 |
0xB000203C | 由于出现错误 %2,重复数据删除无法为容器文件 %1 设置 NTFS 分配大小。%n%3 |
Data Deduplication has failed to set NTFS allocation size for container file %1 due to error %2.%n%3 |
0xB000203D | 重复数据删除配置为对哈希算法 %2 使用 BCrypt 提供程序“%1”。%n%3 |
Data Deduplication configured to use BCrypt provider '%1' for hash algorithm %2.%n%3 |
0xB000203E | 由于操作 %3 时发生错误,重复数据删除无法对哈希算法 %2 使用 BCrypt 提供程序“%1”。正在还原为 Microsoft 基元 CNG 提供程序。%n%4 |
Data Deduplication could not use BCrypt provider '%1' for hash algorithm %2 due to an error in operation %3. Reverting to the Microsoft primitive CNG provider.%n%4 |
0xB000203F | 重复数据删除无法在文件元数据分析计算中包含文件“%1”。%n%2 |
Data Deduplication failed to include file \"%1\" in file metadata analysis calculations.%n%2 |
0xB0002040 | 重复数据删除无法在文件元数据分析计算中包含流映射 %1。%n%2 |
Data Deduplication failed to include stream map %1 in file metadata analysis calculations.%n%2 |
0xB0002041 | 扫描文件和文件夹时重复数据删除遇到文件“%1”的错误。%n%2 |
Data Deduplication encountered an error for file \"%1\" while scanning files and folders.%n%2 |
0xB0002042 | 在尝试恢复处理时,重复数据删除遇到错误。有关处理的当前文件的更多详细信息,请参阅事件日志参数。%n%1 |
Data Deduplication encountered an error while attempting to resume processing. Please consult the event log parameters for more details about the current file being processed.%n%1 |
0xB0002043 | 重复数据删除在为热度范围跟踪更新扫描卷 %2 上的 USN 日志时遇到错误 %1。%n%3 |
Data Deduplication encountered an error %1 whle scanning usn journal on volume %2 for updating hot range tracking.%n%3 |
0xB0002044 | 重复数据删除无法截断已优化文件流。无需执行任何操作。错误: %1%n%n%2 |
Data Deduplication could not truncate the stream of an optimized file. No action is required. Error: %1%n%n%2 |
0xB0002800 | %1 作业内存要求。%n%n卷: %4 (%3)%n最小内存: %5 MB%n最大内存: %6 MB%n最小磁盘: %7 MB%n最大内核数: %8 |
%1 job memory requirements.%n%nVolume: %4 (%3)%nMinimum memory: %5 MB%nMaximum memory: %6 MB%nMinimum disk: %7 MB%nMaximum cores: %8 |
0xB0002801 | %1 协调已启动。%n%n卷: %4 (%3) |
%1 reconciliation has started.%n%nVolume: %4 (%3) |
0xB0002802 | %1 协调已完成。%n%n指导: 此事件预计会在协调完成时发生,不建议执行也无需执行任何操作。协调是一种内部流程,允许优化和数据端口作业在整个重复数据删除区块索引无法加载到内存中时运行。%n%n卷: %4 (%3)%n已协调的容器数: %5%n未协调的容器数: %6%n更新参考数: %7%n更新容器数: %8%n已协调的参考数: %9%n已协调的容器数: %10%n已交叉协调的参考数: %11%n已交叉协调的容器数: %12%n错误代码: %13%n错误消息: %14 |
%1 reconciliation has completed.%n%nGuidance: This event is expected when Reconciliation has completed, there is no recommended or required action. Reconciliation is an internal process that allows Optimization and DataPort jobs to run when the entire Deduplication chunk index cannot be loaded into memory. %n%nVolume: %4 (%3)%nReconciled containers: %5%nUnreconciled containers: %6%nCatchup references: %7%nCatchup containers: %8%nReconciled references: %9%nReconciled containers: %10%nCross-reconciled references: %11%nCross-reconciled containers: %12%nError code: %13%nError message: %14 |
0xB0002803 | 在卷 %4 (%3)上配置的作业 %1 内存不足。%n%n系统内存百分比: %5%n可用内存: %8 MB%n所需最小内存: %6 MB |
%1 job on volume %4 (%3) was configured with insufficient memory.%n%nSystem memory percentage: %5%nAvailable memory: %8 MB%nMinimum required memory: %6 MB |
0xB0002804 | 卷 %3 (%2)上 %1 作业的优化内存详细信息。 |
Optimization memory details for %1 job on volume %3 (%2). |
0xB0002805 | 在优化期间跳过了打开文件。无需执行任何操作。%n%nFileId: %2%n跳过原因: %1 |
An open file was skipped during optimization. No action is required.%n%nFileId: %2%nSkip Reason: %1 |
0xB0002806 | 操作在一次或多次重试后成功。操作: %1;FileId: %3;重试次数: %2 |
An operation succeeded after one or more retries. Operation: %1; FileId: %3; Number of retries: %2 |
0xB0002807 | 重复数据删除中止了优化管道。%nVolumePath: %1%nErrorCode: %2%nErrorMessage: %3详细信息: %4 |
Data Deduplication aborted the optimization pipeline.%nVolumePath: %1%nErrorCode: %2%nErrorMessage: %3Details: %4 |
0xB0002808 | 重复数据删除中止了某个文件。%nFileId: %1%nFilePath: %2%nFileSize: %3%n标志: %4%nTotalRanges: %5%nSkippedRanges: %6%nAbortedRanges: %7%nCommittedRanges: %8%nErrorCode: %9%nErrorMessage: %10详细信息: %11 |
Data Deduplication aborted a file.%nFileId: %1%nFilePath: %2%nFileSize: %3%nFlags: %4%nTotalRanges: %5%nSkippedRanges: %6%nAbortedRanges: %7%nCommittedRanges: %8%nErrorCode: %9%nErrorMessage: %10Details: %11 |
0xB0002809 | 重复数据删除中止了某个文件范围。%nFileId: %1%nFilePath: %2%nRangeOffset: %3%nRangeLength: %4%nErrorCode: %5%nErrorMessage: %6详细信息: %7 |
Data Deduplication aborted a file range.%nFileId: %1%nFilePath: %2%nRangeOffset: %3%nRangeLength: %4%nErrorCode: %5%nErrorMessage: %6Details: %7 |
0xB000280A | 重复数据删除中止了某个会话。%nMaxSize: %1%nCurrentSize: %2%nRemainingRanges: %3%nErrorCode: %4%nErrorMessage: %5详细信息: %6 |
Data Deduplication aborted a session.%nMaxSize: %1%nCurrentSize: %2%nRemainingRanges: %3%nErrorCode: %4%nErrorMessage: %5Details: %6 |
0xB000280B | 已创建 USN 日志。%n%n卷: %2 (%1)%n最大大小 %3 MB%n分配大小 %4 MB |
USN journal created.%n%nVolume: %2 (%1)%nMaximum size %3 MB%nAllocation size %4 MB |
0xB000280C | 卷 %3 (%2)上的 %1 作业的数据端口内存详细信息。 |
DataPort memory details for %1 job on volume %3 (%2). |
0xB000280D | 进行重复数据删除时,检测到某个文件的 ID 不受支持。将跳过其标识符可以解压缩为 64 位的文件。FileId: %1 文件名: %2 |
Data deduplication detected a file with an ID that is not supported. Files with identifiers unpackable into 64-bits will be skipped. FileId: %1 FileName: %2 |
0xB000280E | 应运行协调以确保达到最佳节省效果。%n%n指导: 此事件预计会在关闭协调以执行数据端口作业时发生。协调是一种内部流程,允许优化和数据端口作业在整个重复数据删除区块索引无法加载到内存中时运行。当协调需要 50% 或更多系统内存时,建议(暂时)停止在此卷上运行数据端口作业,并运行优化作业。如果协调未运行,协调前运行的优化作业需要超过 100% 的系统内存,协调将无法再次运行(除非添加更多内存)。这将导致此卷上的空间效率永久降低。%n%n卷: %2 (%1)%n所需内存百分比: %3 |
Reconciliation should be run to ensure optimal savings.%n%nGuidance: This event is expected when Reconciliation is turned off for the DataPort job. Reconciliation is an internal process that allows Optimization and DataPort jobs to run when the entire Deduplication chunk index cannot be loaded into memory. When Reconciliation would require 50% or more of the memory on the system, it is recommended that you (temporarily) cease running a DataPort job against this volume, and run an Optimization job. If Reconciliation is not run through an Optimization job before Reconciliation would require more than 100% of system memory, Reconciliation will not be able to be run again (unless more memory is added). This would result in permanent decreased space efficiency on this volume.%n%nVolume: %2 (%1)%nMemory percentage required: %3 |
0xB000280F | 由于内存不足,重复数据删除优化作业将不会运行协调步骤。%n%n指导: 请为优化作业提供更多内存,或为系统增加更多内存,否则重复数据删除节省空间的效果将不够理想。%n%n卷: %2 (%1)%n所需内存百分比: %3 |
Data Deduplication optimization job will not run the reconciliation step due to inadequate memory.%n%nGuidance: Deduplication savings will be suboptimal until the optimization job is provided more memory, or more more memory is added to the system.%n%nVolume: %2 (%1)%nMemory percentage required: %3 |
0xB0003200 | 重复数据删除服务在“%5%6%7”中检测到损坏。无法修复该损坏。 |
Data Deduplication service detected corruption in \"%5%6%7\". The corruption cannot be repaired. |
0xB0003201 | 重复数据删除服务在“%6”中检测到损坏(%7)。有关详细信息,请查看事件详细信息。 |
Data Deduplication service detected corruption (%7) in \"%6\". See the event details for more information. |
0xB0003202 | 重复数据删除服务在卷 %4 上的重复数据删除区块存储中检测到损坏的项目(%11 - %13,%8,%9,%10,%12)。有关详细信息,请查看事件详细信息。 |
Data Deduplication service detected a corrupted item (%11 - %13, %8, %9, %10, %12) in Deduplication Chunk Store on volume %4. See the event details for more information. |
0xB0003203 | 重复数据删除服务在卷 %3 上完成了清理操作,未发现自从上次清理以来的任何损坏。 |
Data Deduplication service has finished scrubbing on volume %3. It did not find any corruption since the last scrubbing. |
0xB0003204 | 重复数据删除服务在卷 %3 上发现 %4 个损坏,已修复所有损坏。 |
Data Deduplication service found %4 corruption(s) on volume %3. All corruptions are fixed. |
0xB0003205 | 重复数据删除服务在卷 %3 上发现 %4 个损坏。已修复 %5 个损坏。%6 个用户文件损坏。已修复 %7 个用户文件。有关损坏文件列表,请参阅 Microsoft/Windows/Deduplication/Scrubbing 事件。 |
Data Deduplication service found %4 corruption(s) on volume %3. %5 corruption(s) are fixed. %6 user file(s) are corrupted. %7 user file(s) are fixed. For the corrupted file list, see the Microsoft/Windows/Deduplication/Scrubbing events. |
0xB0003206 | 重复数据删除服务在卷 %3 上发现过多的损坏。未报告某些损坏。 |
Data Deduplication service found too many corruptions on volume %3. Some corruptions are not reported. |
0xB0003211 | 重复数据删除服务在卷 %3 上完成了清理操作。有关详细信息,请查看事件详细信息。 |
Data Deduplication service has finished scrubbing on volume %3. See the event details for more information. |
0xB0003212 | 在处理文件“%5%6%7”时,重复数据删除服务遇到错误。错误为 %8。 |
Data Deduplication service encountered error while processing file \"%5%6%7\". The error was %8. |
0xB0003213 | 在处理卷 %3 上的文件时,重复数据删除服务遇到的错误太多。阈值为 %4。可能未报告某些用户文件损坏。 |
Data Deduplication service encountered too many errors while processing file on volume %3. The threshold was %4. Some user file corruptions may not be reported. |
0xB0003214 | 在卷 %3 上的区块存储中检测损坏时,重复数据删除服务遇到错误。错误为 %4。将中止该作业。 |
Data Deduplication service encountered error while detecting corruptions in chunk store on volume %3. The error was %4. The job is aborted. |
0xB0003216 | 在加载卷 %3 上的损坏日志时,重复数据删除服务遇到错误。错误为 %4。该作业将继续执行。可能检测不到某些损坏。 |
Data Deduplication service encountered error while loading corruption logs on volume %3. The error was %4. The job continues. Some corruptions may not be detected. |
0xB0003217 | 在清理卷 %3 上的损坏日志时,重复数据删除服务遇到错误。错误为 %4。下次可能会再次报告某些损坏。 |
Data Deduplication service encountered error while cleaning up corruption logs on volume %3. The error was %4. Some corruptions may be reported again next time. |
0xB0003218 | 从卷 %3 上的区块存储中加载热点映射时,重复数据删除服务遇到错误。错误为 %4。可能未修复某些损坏。 |
Data Deduplication service encountered error while loading hotspots mapping from chunk store on volume %3. The error was %4. Some corruptions may not be repaired. |
0xB0003219 | 在确定卷 %3 上的损坏用户文件时,重复数据删除服务遇到错误。错误为 %4。可能未报告某些用户文件损坏。 |
Data Deduplication service encountered error while determining corrupted user files on volume %3. The error was %4. Some user file corruptions may not be reported. |
0xB000321A | 重复数据删除服务在卷 %3 上发现 %4 个损坏。%6 个用户文件损坏。%7 个用户文件可修复。请在读写模式下运行清理作业,以尝试修复报告的损坏。 |
Data Deduplication service found %4 corruption(s) on volume %3. %6 user file(s) are corrupted. %7 user file(s) are fixable. Please run scrubbing job in read-write mode to attempt fixing reported corruptions. |
0xB000321B | 重复数据删除服务已修复“%5%6%7”中的损坏。 |
Data Deduplication service fixed corruption in \"%5%6%7\". |
0xB000321C | 重复数据删除服务检测到“%5%6%7”中存在可修复损坏。请在读写模式下运行清理作业以修复此损坏。 |
Data Deduplication service detected fixable corruption in \"%5%6%7\". Please run scrubbing job in read-write mode to fix this corruption. |
0xB000321E | 在修复卷 %3 上的损坏时,数据重复删除服务遇到错误。错误为 %4。修复失败。 |
Data Deduplication service encountered error while repairing corruptions on volume %3. The error was %4. The repair is unsuccessful. |
0xB000321F | 数据重复删除服务在卷 %4 的数据重复删除区块存储中检测到损坏项目(%6、%7、%8 和 %9)。有关详细信息,请参阅事件详细信息。 |
Data Deduplication service detected a corrupted item (%6, %7, %8, %9) in Deduplication Chunk Store on volume %4. See the event details for more information. |
0xB0003220 | 容器(%8,%9)区块存储中缺少用户数据。容器数据缺失可能由还原未完成、迁移不完全或文件系统损坏造成。卷无法进行深入优化。建议先还原该卷,然后再为该卷启用深入优化。 |
Container (%8,%9) with user data is missing from the chunk store. Missing container may result from incomplete restore, incomplete migration or file-system corruption. Volume is disabled from further optimization. It is recommended to restore the volume prior to enabling the volume for further optimization. |
0xB0003221 | 扫描卷 %3 上的删除重复用户文件时重复数据删除服务遇到错误。错误为 %4。可能未报告某些用户文件损坏。 |
Data Deduplication service encountered error while scaning dedup user files on volume %3. The error was %4. Some user file corruptions may not be reported. |
0xB0003224 | 由于与文件“%8”共享重分析点,重复数据删除服务检测到“%6”中可能的数据丢失(%9)。有关详细信息,请参阅事件详细信息。 |
Data Deduplication service detected potential data loss (%9) in \"%6\" due to sharing reparse data with file \"%8\". See the event details for more information. |
0xB0003225 | 区块存储中具有用户数据的容器(%8,%9)已损坏。建议在启用该卷进行进一步优化之前还原该卷。 |
Container (%8,%9) with user data is corrupt in the chunk store. It is recommended to restore the volume prior to enabling the volume for further optimization. |
0xB0005000 | 打开流存储流(StartingChunkId %1,FileId %2) |
Open stream store stream (StartingChunkId %1, FileId %2) |
0xB0005001 | 打开流存储流已完成 %1 |
Open stream store stream completed %1 |
0xB0005002 | 准备分页 IO (流 %1,FileId %2) |
Prepare for paging IO (Stream %1, FileId %2) |
0xB0005003 | 准备分页 IO 已完成 %1 |
Prepare for paging IO completed %1 |
0xB0005005 | 读取流映射已完成 %1 |
Read stream map completed %1 |
0xB0005006 | 读取区块(流 %1,FileId %2,IoType %3,FirstRequestChunkId %4,NextRequest %5) |
Read chunks (Stream %1, FileId %2, IoType %3, FirstRequestChunkId %4, NextRequest %5) |
0xB0005007 | 读取区块已完成 %1 |
Read chunks completed %1 |
0xB0005008 | 计算校验和(ItemType %1,DataSize %2) |
Compute checksum (ItemType %1, DataSize %2) |
0xB0005009 | 计算校验和已完成 %1 |
Compute checksum completed %1 |
0xB000500A | 获取容器条目(ContainerId %1,版本 %2) |
Get container entry (ContainerId %1, Generation %2) |
0xB000500B | 获取容器条目已完成 %1 |
Get container entry completed %1 |
0xB000500C | 获取容器的最大版本(ContainerId %1,版本 %2) |
Get maximum generation for container (ContainerId %1, Generation %2) |
0xB000500D | 获取容器的最大版本已完成 %1 |
Get maximum generation for container completed %1 |
0xB000500E | 打开区块容器(ContainerId %1,版本 %2,RootPath %4) |
Open chunk container (ContainerId %1, Generation %2, RootPath %4) |
0xB000500F | 打开区块容器已完成 %1 |
Open chunk container completed %1 |
0xB0005010 | 初始化区块容器重定向表(ContainerId %1,版本 %2) |
Initialize chunk container redirection table (ContainerId %1, Generation %2) |
0xB0005011 | 初始化区块容器重定向表已完成 %1 |
Initialize chunk container redirection table completed %1 |
0xB0005012 | 验证区块容器重定向表(ContainerId %1,版本 %2) |
Validate chunk container redirection table (ContainerId %1, Generation %2) |
0xB0005013 | 验证区块容器重定向表已完成 %1 |
Validate chunk container redirection table completed %1 |
0xB0005014 | 获取区块容器有效数据长度(ContainerId %1,版本 %2) |
Get chunk container valid data length (ContainerId %1, Generation %2) |
0xB0005015 | 获取区块容器有效数据长度已完成 %1 |
Get chunk container valid data length completed %1 |
0xB0005016 | 获取区块容器重定向表偏移量(ContainerId %1,版本 %2) |
Get offset from chunk container redirection table (ContainerId %1, Generation %2) |
0xB0005017 | 获取区块容器重定向表偏移量已完成 %1 |
Get offset from chunk container redirection table completed %1 |
0xB0005018 | 读取区块容器块(ContainerId %1,版本 %2,缓冲区 %3,偏移量 %4,长度 %5,IoType %6,同步 %7) |
Read chunk container block (ContainerId %1, Generation %2, Buffer %3, Offset %4, Length %5, IoType %6, Synchronous %7) |
0xB0005019 | 读取区块容器块已完成 %1 |
Read chunk container block completed %1 |
0xB000501A | 清除区块容器块(缓冲区 %1,大小 %2,BufferType %3) |
Clear chunk container block (Buffer %1, Size %2, BufferType %3) |
0xB000501B | 清除区块容器块已完成 %1 |
Clear chunk container block completed %1 |
0xB000501C | 复制区块(缓冲区 %1,大小 %2,BufferType %3,BufferOffset %4,OutputCapacity %5) |
Copy chunk (Buffer %1, Size %2, BufferType %3, BufferOffset %4, OutputCapacity %5) |
0xB000501D | 复制区块已完成 %1 |
Copy chunk completed %1 |
0xB000501E | 初始化文件缓存(UnderlyingFileObject %1,CacheFileSize %2) |
Initialize file cache (UnderlyingFileObject %1, CacheFileSize %2) |
0xB000501F | 初始化文件缓存已完成 %1 |
Initialize file cache completed %1 |
0xB0005020 | 映射文件缓存数据(CacheFileObject %1,偏移量 %2,长度 %3) |
Map file cache data (CacheFileObject %1, Offset %2, Length %3) |
0xB0005021 | 映射文件缓存数据已完成 %1 |
Map file cache data completed %1 |
0xB0005022 | 取消固定文件缓存数据(Bcb %1) |
Unpin file cache data(Bcb %1) |
0xB0005023 | 取消固定文件缓存数据已完成 %1 |
Unpin file cache data completed %1 |
0xB0005024 | 复制文件缓存数据(CacheFileObject %1,偏移量 %2,长度 %3) |
Copy file cache data (CacheFileObject %1, Offset %2, Length %3) |
0xB0005025 | 复制文件缓存数据已完成 %1 |
Copy file cache data completed %1 |
0xB0005026 | 读取基本文件缓存数据(CacheFileObject %1,UnderlyingFileObject %2,偏移量 %3,长度 %4) |
Read underlying file cache data (CacheFileObject %1, UnderlyingFileObject %2, Offset %3, Length %4) |
0xB0005027 | 读取基本文件缓存数据已完成 %1 |
Read underlying file cache data completed %1 |
0xB0005028 | 获取区块容器文件大小(ContainerId %1,版本 %2) |
Get chunk container file size (ContainerId %1, Generation %2) |
0xB0005029 | 获取区块容器文件大小已完成 %1 |
Get chunk container file size completed %1 |
0xB000502A | 固定流映射(流 %1,FileId %2,StartIndex %3,EntryCount %4) |
Pin stream map (Stream %1, FileId %2, StartIndex %3, EntryCount %4) |
0xB000502B | 固定流映射已完成 %1 |
Pin stream map completed %1 |
0xB000502C | 固定区块容器(ContainerId %1,版本 %2) |
Pin chunk container (ContainerId %1, Generation %2) |
0xB000502D | 固定区块容器已完成 %1 |
Pin chunk container completed %1 |
0xB000502E | 固定区块(ContainerId %1,版本 %2) |
Pin chunk (ContainerId %1, Generation %2) |
0xB000502F | 固定区块已完成 %1 |
Pin chunk completed %1 |
0xB0005030 | 分配池缓冲区(ReadLength %1,PagingIo %2) |
Allocate pool buffer (ReadLength %1, PagingIo %2) |
0xB0005031 | 分配池缓冲区已完成 %1 |
Allocate pool buffer completed %1 |
0xB0005032 | 取消固定区块容器(ContainerId %1,版本 %2) |
Unpin chunk container (ContainerId %1, Generation %2) |
0xB0005033 | 取消固定区块容器已完成 %1 |
Unpin chunk container completed %1 |
0xB0005034 | 取消固定区块(ContainerId %1,版本 %2) |
Unpin chunk (ContainerId %1, Generation %2) |
0xB0005035 | 取消固定区块已完成 %1 |
Unpin chunk completed %1 |
0xB0006028 | 重复数据删除读取处理(FileObject %1,偏移量 %2,长度 %3,IoType %4) |
Dedup read processing (FileObject %1, Offset %2, Length %3, IoType %4) |
0xB0006029 | 重复数据删除读取处理已完成 %1 |
Dedup read processing completed %1 |
0xB000602A | 获取第一个流映射条目(TlCache %1,流 %2,RequestStartOffset %3,RequestEndOffset %4) |
Get first stream map entry (TlCache %1, Stream %2, RequestStartOffset %3, RequestEndOffset %4) |
0xB000602B | 获取第一个流映射条目已完成 %1 |
Get first stream map entry completed %1 |
0xB000602C | 读取区块元数据(流 %1,CurrentOffset %2,AdjustedFinalOffset %3,FirstChunkByteOffset %4,ChunkRequestsEndOffset %5,TlCache %6) |
Read chunk metadata (Stream %1, CurrentOffset %2, AdjustedFinalOffset %3, FirstChunkByteOffset %4, ChunkRequestsEndOffset %5, TlCache %6) |
0xB000602D | 读取区块元数据已完成 %1 |
Read chunk metadata completed %1 |
0xB000602E | 读取区块数据(TlCache %1,流 %2,RequestStartOffset %3,RequestEndOffset %4) |
Read chunk data (TlCache %1, Stream %2, RequestStartOffset %3, RequestEndOffset %4) |
0xB000602F | 读取区块数据已完成 %1 |
Read chunk data completed %1 |
0xB0006030 | 引用 TlCache 数据(TlCache %1,流 %2) |
Reference TlCache data (TlCache %1, Stream %2) |
0xB0006031 | 引用 TlCache 数据已完成 %1 |
Reference TlCache data completed %1 |
0xB0006032 | 从流存储中读取区块数据(流 %1) |
Read chunk data from stream store (Stream %1) |
0xB0006033 | 从流存储中读取区块数据已完成 %1 |
Read chunk data from stream store completed %1 |
0xB0006035 | 组合区块数据已完成 %1 |
Assemble chunk data completed %1 |
0xB0006037 | 解压缩区块数据已完成 %1 |
Decompress chunk data completed %1 |
0xB0006038 | 将区块数据复制到用户缓冲区(BytesCopied %1) |
Copy chunk data in to user buffer (BytesCopied %1) |
0xB0006039 | 将区块数据复制到用户缓冲区已完成 %1 |
Copy chunk data in to user buffer completed %1 |
0xB000603B | 将区块数据插入到 tlcache 已完成 %1 |
Insert chunk data in to tlcache completed %1 |
0xB000603C | 从重复数据删除重新分析点文件中读取数据(FileObject %1,偏移量 %2,长度 %3) |
Read data from dedup reparse point file (FileObject %1, Offset %2, Length %3) |
0xB000603E | 准备流映射(StreamContext %1) |
Prepare stream map (StreamContext %1) |
0xB000603F | 准备流映射已完成 %1 |
Prepare stream map completed %1 |
0xB0006040 | 修补清理范围(FileObject %1,偏移量 %2,长度 %3) |
Patch clean ranges (FileObject %1, Offset %2, Length %3) |
0xB0006041 | 修补清理范围已完成 %1 |
Patch clean ranges completed %1 |
0xB0006042 | 将数据写入到重复数据删除文件(FileObject %1,偏移量 %2,长度 %3,IoType %4) |
Writing data to dedup file (FileObject %1, Offset %2, Length %3, IoType %4) |
0xB0006043 | 将数据写入到重复数据删除文件已完成 %1 |
Writing data to dedup file completed %1 |
0xB0006044 | 将重复数据删除文件写入请求排入队列中(FileObject %1,偏移量 %2,长度 %3) |
Queue write request on dedup file (FileObject %1, Offset %2, Length %3) |
0xB0006045 | 将重复数据删除文件写入请求排入队列中已完成 %1 |
Queue write request on dedup file completed %1 |
0xB0006046 | 对重复数据删除文件执行写入时复制操作(FileObject %1,偏移量 %2,长度 %3) |
Do copy on write work on dedup file (FileObject %1, Offset %2, Length %3) |
0xB0006047 | 对重复数据删除文件执行写入时复制操作已完成 %1 |
Do copy on write work on dedup file completed %1 |
0xB0006048 | 对重复数据删除文件执行完全重新调用(FileObject %1,偏移量 %2,长度 %3) |
Do full recall on dedup file (FileObject %1, Offset %2, Length %3) |
0xB0006049 | 对重复数据删除文件执行完全重新调用已完成 %1 |
Do full recall on dedup file completed %1 |
0xB000604A | 对重复数据删除文件执行部分重新调用(FileObject %1,偏移量 %2,长度 %3) |
Do partial recall on dedup file (FileObject %1, Offset %2, Length %3) |
0xB000604B | 对重复数据删除文件执行部分重新调用已完成 %1 |
Do partial recall on dedup file completed %1 |
0xB000604C | 对重复数据删除文件执行虚拟分页读取(FileObject %1,偏移量 %2,长度 %3) |
Do dummy paging read on dedup file (FileObject %1, Offset %2, Length %3) |
0xB000604D | 对重复数据删除文件执行虚拟分页读取已完成 %1 |
Do dummy paging read on dedup file completed %1 |
0xB000604E | 读取清理数据以重新调用文件(FileObject %1,偏移量 %2,长度 %3) |
Read clean data for recalling file (FileObject %1, Offset %2, Length %3) |
0xB000604F | 读取清理数据以重新调用文件已完成 %1 |
Read clean data for recalling file completed %1 |
0xB0006050 | 将清理数据正常写入到重复数据删除文件(FileObject %1,偏移量 %2,长度 %3) |
Write clean data to dedup file normally (FileObject %1, Offset %2, Length %3) |
0xB0006051 | 将清理数据写入到重复数据删除文件已完成 %1 |
Write clean data to dedup file completed %1 |
0xB0006052 | 以分页方式将清理数据写入到重复数据删除文件(FileObject %1,偏移量 %2,长度 %3) |
Write clean data to dedup file paged (FileObject %1, Offset %2, Length %3) |
0xB0006053 | 以分页方式将清理数据写入到重复数据删除文件已完成 %1 |
Write clean data to dedup file paged completed %1 |
0xB0006054 | 使用分页 IO 重新调用重复数据删除文件(FileObject %1,偏移量 %2,长度 %3) |
Recall dedup file using paging Io (FileObject %1, Offset %2, Length %3) |
0xB0006055 | 使用分页 IO 重新调用重复数据删除文件已完成 %1 |
Recall dedup file using paging Io completed %1 |
0xB0006056 | 在重新调用后刷新重复数据删除文件(FileObject %1) |
Flush dedup file after recall (FileObject %1) |
0xB0006057 | 在重新调用后刷新重复数据删除文件已完成 %1 |
Flush dedup file after recall completed %1 |
0xB0006058 | 在重新调用重复数据删除文件后更新位图(FileObject %1,偏移量 %2,长度 %3) |
Update bitmap after recall on dedup file (FileObject %1, Offset %2, Length %3) |
0xB0006059 | 在重新调用重复数据删除文件后更新位图已完成 %1 |
Update bitmap after recall on dedup file completed %1 |
0xB000605A | 删除重复数据删除重新分析点(FileObject %1) |
Delete dedup reparse point (FileObject %1) |
0xB000605B | 删除重复数据删除重新分析点已完成 %1 |
Delete dedup reparse point completed %1 |
0xB000605C | 打开重复数据删除文件(FilePath %1) |
Open dedup file (FilePath %1) |
0xB000605D | 打开重复数据删除文件已完成 %1 |
Open dedup file completed %1 |
0xB000605F | 锁定以禁止读取用户缓冲区已完成 %1 |
Locking user buffer for read completed %1 |
0xB0006061 | 获取 MDL 系统地址已完成 %1 |
Get system address for MDL completed %1 |
0xB0006062 | 读取清理重复数据删除文件(FileObject %1,偏移量 %2,长度 %3) |
Read clean dedup file (FileObject %1, Offset %2, Length %3) |
0xB0006063 | 读取清理重复数据删除文件已完成 %1 |
Read clean dedup file completed %1 |
0xB0006064 | 获取范围状态(偏移量 %1,长度 %2) |
Get range state (Offset %1, Length %2) |
0xB0006065 | 获取范围状态已完成 %1 |
Get range state completed %1 |
0xB0006067 | 获取区块正文已完成 %1 |
Get chunk body completed %1 |
0xB0006069 | 释放区块已完成 %1 |
Release chunk completed %1 |
0xB000606A | 释放解压缩区块上下文(BufferSize %1) |
Release decompress chunk context (BufferSize %1) |
0xB000606B | 释放解压缩区块上下文已完成 %1 |
Release decompress chunk context completed %1 |
0xB000606C | 准备解压缩区块上下文(BufferSize %1) |
Prepare decompress chunk context (BufferSize %1) |
0xB000606D | 准备解压缩区块上下文已完成 %1 |
Prepare decompress chunk context completed %1 |
0xB000606E | 将数据复制到压缩的缓冲区(BufferSize %1) |
Copy data to compressed buffer (BufferSize %1) |
0xB000606F | 将数据复制到压缩的缓冲区已完成 %1 |
Copy data to compressed buffer completed %1 |
0xB0006071 | 从 TL 缓存中释放数据已完成 %1 |
Release data from TL Cache completed %1 |
0xB0006072 | 将异步读取请求排入队列(FileObject %1,偏移量 %2,长度 %3) |
Queue async read request (FileObject %1, Offset %2, Length %3) |
0xB0006073 | 将异步读取请求排入队列已完成 %1 |
Queue async read request complete %1 |
0xB0015004 | 读取流映射(流 %1,FileId %2,StartIndex %3,EntryCount %4) |
Read stream map (Stream %1, FileId %2, StartIndex %3, EntryCount %4) |
0xB1004000 | 创建区块容器(%1 - %2.%3.ccc) |
Create chunk container (%1 - %2.%3.ccc) |
0xB1004001 | 创建区块容器已完成 %1 |
Create chunk container completed %1 |
0xB1004002 | 复制区块容器(%1 - %2.%3.ccc) |
Copy chunk container (%1 - %2.%3.ccc) |
0xB1004003 | 复制区块容器已完成 %1 |
Copy chunk container completed %1 |
0xB1004004 | 删除区块容器(%1 - %2.%3.ccc) |
Delete chunk container (%1 - %2.%3.ccc) |
0xB1004005 | 删除区块容器已完成 %1 |
Delete chunk container completed %1 |
0xB1004006 | 重命名区块容器(%1 - %2.%3.ccc%4) |
Rename chunk container (%1 - %2.%3.ccc%4) |
0xB1004007 | 重命名区块容器已完成 %1 |
Rename chunk container completed %1 |
0xB1004008 | 刷新区块容器(%1 - %2.%3.ccc) |
Flush chunk container (%1 - %2.%3.ccc) |
0xB1004009 | 刷新区块容器已完成 %1 |
Flush chunk container completed %1 |
0xB100400A | 回退区块容器(%1 - %2.%3.ccc) |
Rollback chunk container (%1 - %2.%3.ccc) |
0xB100400B | 回退区块容器已完成 %1 |
Rollback chunk container completed %1 |
0xB100400C | 将区块容器(%1 - %2.%3.ccc)标记为只读 |
Mark chunk container (%1 - %2.%3.ccc) read-only |
0xB100400D | 将区块容器标记为只读已完成 %1 |
Mark chunk container read-only completed %1 |
0xB100400E | 在偏移量 %4 处写入区块容器(%1 - %2.%3.ccc)重定向表(条目: StartIndex %5,计数 %6) |
Write chunk container (%1 - %2.%3.ccc) redirection table at offset %4 (Entries: StartIndex %5, Count %6) |
0xB100400F | 写入区块容器重定向表已完成 %1 |
Write chunk container redirection table completed %1 |
0xB1004011 | 写入区块容器标头已完成 %1 |
Write chunk container header completed %1 |
0xB1004013 | 插入数据区块标头已完成 %1 |
Insert data chunk header completed %1 |
0xB1004015 | 插入数据区块正文已完成 %1,ChunkId 为 %2 |
Insert data chunk body completed %1 with ChunkId %2 |
0xB1004019 | 写入删除日志标头已完成 %1 |
Write delete log header completed %1 |
0xB100401B | 附加删除日志条目已完成 %1 |
Append delete log entries completed %1 |
0xB100401D | 删除删除日志已完成 %1 |
Delete delete log completed %1 |
0xB100401F | 重命名删除日志已完成 %1 |
Rename delete log completed %1 |
0xB1004021 | 写入区块容器位图已完成 %1 |
Write chunk container bitmap completed %1 |
0xB1004023 | 删除区块容器位图已完成 %1 |
Delete chunk container bitmap completed %1 |
0xB1004024 | 写入合并日志(%5 - %6.%7.merge.log)标题 |
Write merge log (%5 - %6.%7.merge.log) header |
0xB1004025 | 写入合并日志标头已完成 %1 |
Write merge log header completed %1 |
0xB1004027 | 插入热点区块标头已完成 %1 |
Insert hotspot chunk header completed %1 |
0xB1004029 | 插入热点区块正文已完成 %1,ChunkId 为 %2 |
Insert hotspot chunk body completed %1 with ChunkId %2 |
0xB100402B | 插入流映射区块标头已完成 %1 |
Insert stream map chunk header completed %1 |
0xB100402D | 插入流映射区块正文已完成 %1,ChunkId 为 %2 |
Insert stream map chunk body completed %1 with ChunkId %2 |
0xB100402F | 附加合并日志条目已完成 %1 |
Append merge log entries completed %1 |
0xB1004030 | 删除合并日志(%1 - %2.%3.merge.log) |
Delete merge log (%1 - %2.%3.merge.log) |
0xB1004031 | 删除合并日志已完成 %1 |
Delete merge log completed %1 |
0xB1004032 | 刷新合并日志(%1 - %2.%3.merge.log) |
Flush merge log (%1 - %2.%3.merge.log) |
0xB1004033 | 刷新合并日志已完成 %1 |
Flush merge log completed %1 |
0xB1004034 | 更新文件列表条目(删除: %1,添加: %2) |
Update file list entries (Remove: %1, Add: %2) |
0xB1004035 | 更新文件列表条目已完成 %1 |
Update file list entries completed %1 |
0xB1004036 | 在 %2 上设置重复数据删除重新分析点(FileId %1) (ReparsePoint: SizeBackedByChunkStore %3,StreamMapInfoSize %4,StreamMapInfo %5) |
Set dedup reparse point on %2 (FileId %1) (ReparsePoint: SizeBackedByChunkStore %3, StreamMapInfoSize %4, StreamMapInfo %5) |
0xB1004037 | 设置重复数据删除重新分析点已完成 %1 (%2) |
Set dedup reparse point completed %1 (%2) |
0xB1004038 | 在 %2 上设置重复数据删除零数据(FileId %1) |
Set dedup zero data on %2 (FileId %1) |
0xB1004039 | 设置重复数据删除零数据已完成 %1 |
Set dedup zero data completed %1 |
0xB100403A | 刷新重分析点文件 |
Flush reparse point files |
0xB100403B | 刷新重新分析点文件已完成 %1 |
Flush reparse point files completed %1 |
0xB100403C | 在文件 ID %1 上设置稀疏 |
Set sparse on file id %1 |
0xB100403D | 设置稀疏已完成 %1 |
Set sparse completed %1 |
0xB100403E | 在文件 ID %1 上执行 FSCTL_SET_ZERO_DATA,偏移量为 %2,BeyondFinalZero 为 %3 |
FSCTL_SET_ZERO_DATA on file id %1 at offset %2 and BeyondFinalZero %3 |
0xB100403F | FSCTL_SET_ZERO_DATA 已完成 %1 |
FSCTL_SET_ZERO_DATA completed %1 |
0xB1004040 | 重命名区块容器(%1 - %3.%4)的区块容器位图(%1 - %2) |
Rename chunk container bitmap (%1 - %2) for chunk container (%1 - %3.%4) |
0xB1004041 | 重命名区块容器位图已完成 %1 |
Rename chunk container bitmap completed %1 |
0xB1004042 | 将填充区块标头插入到区块容器(%1 - %2.%3.ccc)的偏移量 %4 处(区块: IsBatched %5,IsCorrupted %6,DataSize %7) |
Insert padding chunk header to chunk container (%1 - %2.%3.ccc) at offset %4 (Chunk: IsBatched %5 IsCorupted %6, DataSize %7) |
0xB1004043 | 插入填充区块标头已完成 %1 |
Insert padding chunk header completed %1 |
0xB1004044 | 将填充区块正文插入到区块容器(%1 - %2.%3.ccc)的偏移量 %4 处(区块: IsBatched %5,IsCorrupted %6,DataSize %7) |
Insert padding chunk body to chunk container (%1 - %2.%3.ccc) at offset %4 (Chunk: IsBatched %5 IsCorrupted %6, DataSize %7) |
0xB1004045 | 插入填充区块正文已完成 %1,ChunkId 为 %2 |
Insert padding chunk body completed %1 with ChunkId %2 |
0xB1004046 | 将一批区块插入到区块容器(%1 - %2.%3.ccc)的偏移量 %4 处(BatchChunkCount %5,BatchDataSize %6) |
Insert batch of chunks to chunk container (%1 - %2.%3.ccc) at offset %4 (BatchChunkCount %5, BatchDataSize %6) |
0xB1004047 | 插入一批区块已完成 %1 |
Insert batch of chunks completed %1 |
0xB1004049 | 写入区块容器目录已完成 %1 |
Write chunk container directory completed %1 |
0xB100404B | 删除区块容器目录已完成 %1 |
Delete chunk container directory completed %1 |
0xB100404C | 重命名区块容器(%1 - %3.%4)的区块容器目录(%1 - %2) |
Rename chunk container directory (%1 - %2) for chunk container (%1 - %3.%4) |
0xB100404D | 重命名区块容器目录已完成 %1 |
Rename chunk container directory completed %1 |
0xB1014010 | 在偏移量 %8 处写入区块容器(%5 - %6.%7.ccc)标头(标头: USN %9,VDL %10,#Chunk %11,NextLocalId %12,标志 %13,LastAppendTime %14,BackupRedirectionTableOfset %15,LastReconciliationLocalId %16) |
Write chunk container (%5 - %6.%7.ccc) header at offset %8 (Header: USN %9, VDL %10, #Chunk %11, NextLocalId %12, Flags %13, LastAppendTime %14, BackupRedirectionTableOfset %15, LastReconciliationLocalId %16) |
0xB1014012 | 将数据区块标头插入到区块容器(%1 - %2.%3.ccc)的偏移量 %4 处(区块: IsBatched %5,IsCorrupted %6,DataSize %7) |
Insert data chunk header to chunk container (%1 - %2.%3.ccc) at offset %4 (Chunk: IsBatched %5 IsCorupted %6, DataSize %7) |
0xB1014014 | 将数据区块正文插入到区块容器(%1 - %2.%3.ccc)的偏移量 %4 处(区块: IsBatched %5,IsCorrupted %6,DataSize %7) |
Insert data chunk body to chunk container (%1 - %2.%3.ccc) at offset %4 (Chunk: IsBatched %5 IsCorrupted %6, DataSize %7) |
0xB1014018 | 写入删除日志(%5 - %6.%7.delete.log)标头 |
Write delete log (%5 - %6.%7.delete.log) header |
0xB101401A | 在偏移量 %4 处附加删除日志(%1 - %2.%3.delete.log)条目(条目: StartIndex %5,计数 %6) |
Append delete log (%1 - %2.%3.delete.log) entries at offset %4 (Entries: StartIndex %5, Count %6) |
0xB101401C | 删除删除日志(%1 - %2.%3.delete.log) |
Delete delete log (%1 - %2.%3.delete.log) |
0xB101401E | 重命名删除日志(%1 - %2.%3.delete.log) |
Rename delete log (%1 - %2.%3.delete.log) |
0xB1014020 | 写入区块容器(%1 - %3.%4)的区块容器位图(%1 - %2) (位图: BitLength %5,StartIndex %6,计数 %7) |
Write chunk container bitmap (%1 - %2) for chunk container (%1 - %3.%4) (Bitmap: BitLength %5, StartIndex %6, Count %7) |
0xB1014022 | 删除区块容器(%1 - %3.%4)的区块容器位图(%1 - %2) |
Delete chunk container bitmap (%1 - %2) for chunk container (%1 - %3.%4) |
0xB1014026 | 将热点区块标头插入到区块容器(%1 - %2.%3.ccc)的偏移量 %4 处(区块: IsBatched %5,IsCorrupted %6,DataSize %7) |
Insert hotspot chunk header to chunk container (%1 - %2.%3.ccc) at offset %4 (Chunk: IsBatched %5 IsCorrupted %6, DataSize %7) |
0xB1014028 | 将热点区块正文插入到区块容器(%1 - %2.%3.ccc)的偏移量 %4 处(区块: IsBatched %5,IsCorrupted %6,DataSize %7) |
Insert hotspot chunk body to chunk container (%1 - %2.%3.ccc) at offset %4 (Chunk: IsBatched %5 IsCorrupted %6, DataSize %7) |
0xB101402A | 将流映射区块标头插入到区块容器(%1 - %2.%3.ccc)的偏移量 %4 处(区块: IsBatched %5,IsCorrupted %6,DataSize %7) |
Insert stream map chunk header to chunk container (%1 - %2.%3.ccc) at offset %4 (Chunk: IsBatched %5 IsCorrupted %6, DataSize %7) |
0xB1014048 | 写入区块容器(%1 - %3.%4)的区块容器目录(%1 - %2)(目录: EntryCount %5) |
Write chunk container directory (%1 - %2) for chunk container (%1 - %3.%4) (Directory: EntryCount %5) |
0xB101404A | 删除区块容器(%1 - %3.%4)的区块容器目录(%1 - %2) |
Delete chunk container directory (%1 - %2) for chunk container (%1 - %3.%4) |
0xB102402E | 在偏移量 %4 处附加合并日志(%1 - %2.%3.merge.log)条目(条目: StartIndex %5,计数 %6) |
Append merge log (%1 - %2.%3.merge.log) entries at offset %4 (Entries: StartIndex %5, Count %6) |
0xB103402C | 在偏移量 %4 处将流映射区块体插入区块容器(%1 - %2.%3.ccc) (区块: IsBatched %5 IsCorrupted %6,DataSize %7) (条目: StartIndex %8,计数 %9) |
Insert stream map chunk body to chunk container (%1 - %2.%3.ccc) at offset %4 (Chunk: IsBatched %5 IsCorrupted %6, DataSize %7) (Entries: StartIndex %8, Count %9) |
0xD0000001 | 区块标头 |
Chunk header |
0xD0000002 | 区块正文 |
Chunk body |
0xD0000003 | 容器标头 |
Container header |
0xD0000004 | 容器重定向表 |
Container redirection table |
0xD0000005 | 热点表 |
Hotspot table |
0xD0000006 | 删除日志标头 |
Delete log header |
0xD0000007 | 删除日志条目 |
Delete log entry |
0xD0000008 | GC 位图标头 |
GC bitmap header |
0xD0000009 | GC 位图条目 |
GC bitmap entry |
0xD000000A | 合并日志标头 |
Merge log header |
0xD000000B | 合并日志条目 |
Merge log entry |
0xD000000C | 数据 |
Data |
0xD000000E | 热点 |
Hotspot |
0xD000000F | 优化 |
Optimization |
0xD0000010 | 垃圾回收 |
Garbage Collection |
0xD0000011 | 清理 |
Scrubbing |
0xD0000012 | 取消优化 |
Unoptimization |
0xD0000013 | 分析 |
Analysis |
0xD0000014 | 低 |
Low |
0xD0000015 | 正常 |
Normal |
0xD0000016 | 高 |
High |
0xD0000017 | 缓存 |
Cache |
0xD0000018 | 非缓存 |
Non-cache |
0xD0000019 | 分页 |
Paging |
0xD000001A | 内存映射 |
Memory map |
0xD000001B | 分页内存映射 |
Paging memory map |
0xD000001C | 无 |
None |
0xD000001D | 池 |
Pool |
0xD000001E | PoolAligned |
PoolAligned |
0xD000001F | MDL |
MDL |
0xD0000020 | 映射 |
Map |
0xD0000024 | 容器文件 |
container file |
0xD0000025 | 文件列表文件 |
file list file |
0xD0000026 | 文件列表标头 |
file list header |
0xD0000027 | 文件列表条目 |
file list entry |
0xD0000028 | 主文件列表文件 |
primary file list file |
0xD0000029 | 备份文件列表文件 |
backup file list file |
0xD000002A | 计划 |
Scheduled |
0xD000002B | 手动 |
Manual |
0xD000002C | 撤回位图标头 |
recall bitmap header |
0xD000002D | 撤回位图正文 |
recall bitmap body |
0xD000002E | 缺少撤回位图 |
recall bitmap missing |
0xD000002F | 撤回位图 |
Recall bitmap |
0xD0000030 | 未知 |
Unknown |
0xD0000031 | 已关闭管道句柄 |
The pipeline handle was closed |
0xD0000032 | 该文件已被删除 |
The file was deleted |
0xD0000033 | 该文件已被覆盖 |
The file was overwritten |
0xD0000034 | 该文件已被撤回 |
The file was recalled |
0xD0000035 | 已对该文件启动事务 |
A transaction was started on the file |
0xD0000036 | 该文件已加密 |
The file was encrypted |
0xD0000037 | 该文件已压缩 |
The file was compressed |
0xD0000038 | 已对该文件调用 Set Zero Data |
Set Zero Data was called on the file |
0xD0000039 | 已在该文件上设置扩展属性 |
Extended Attributes were set on the file |
0xD000003A | 已在该文件上创建分区 |
A section was created on the file |
0xD000003B | 该文件已收缩 |
The file was shrunk |
0xD000003C | 长时间运行的 IO 操作已阻止优化 |
A long-running IO operation prevented optimization |
0xD000003D | IO 操作失败 |
An IO operation failed |
0xD000003E | 正在通知优化 |
Notifying Optimization |
0xD000003F | 正在设置重分析点 |
Setting the Reparse Point |
0xD0000040 | 正在截断文件 |
Truncating the file |
0xD0000041 | 数据端口 |
DataPort |
0xD1000002 | LZNT1 |
LZNT1 |
0xD1000003 | Xpress |
Xpress |
0xD1000004 | Xpreff Huff |
Xpreff Huff |
0xD1000006 | 标准 |
Standard |
0xD1000007 | 最大 |
Max |
0xD1000008 | 混合 |
Hybrid |
0xF0000002 | 错误校验和 |
Bad checksum |
0xF0000003 | 元数据不一致 |
Inconsistent metadata |
0xF0000004 | 头元数据无效 |
Invalid header metadata |
0xF0000005 | 文件丢失 |
Missing file |
0xF0000006 | 错误校验和(存储子系统) |
Bad checksum (storage subsystem) |
0xF0000007 | 损坏(存储子系统) |
Corruption (storage subsystem) |
0xF0000008 | 损坏(缺少元数据) |
Corruption (missing metadata) |
0xF0000009 | 可能的数据丢失(重复的重分析数据) |
Possible data loss (duplicate reparse data) |