forked from docs/doc-exports
weihongmin1
a41a4e0331
Reviewed-by: Sabelnikov, Dmitriy <dmitriy.sabelnikov@t-systems.com> Co-authored-by: weihongmin1 <weihongmin1@huawei.com> Co-committed-by: weihongmin1 <weihongmin1@huawei.com>
17 lines
3.2 KiB
HTML
17 lines
3.2 KiB
HTML
<a name="obs_11_0057"></a><a name="obs_11_0057"></a>
|
|
|
|
<h1 class="topictitle1">Result Lists</h1>
|
|
<div id="body1554982511704"><div class="section" id="obs_11_0057__section16839141103914"><h4 class="sectiontitle">Configuring Result Lists</h4><p id="obs_11_0057__p91541514479">Result files are generated when batch tasks complete. By default, they are saved to the subfolder <strong id="obs_11_0057__b7637103982312">.obsutil_output</strong> in the home directory of the user who executes obsutil commands. You can specify another folder to save them by setting the additional parameter <strong id="obs_11_0057__b1076755452411">-o</strong> when executing a command.</p>
|
|
</div>
|
|
<div class="section" id="obs_11_0057__section14566233134617"><h4 class="sectiontitle">Viewing Result Lists</h4><p id="obs_11_0057__p397816524335">Result files are classified into success, failure, and warning files. The naming rule is as follows: <em id="obs_11_0057__i1034723213359">Operation</em><strong id="obs_11_0057__b1680134363512"> _{succeed | failed | warning}_report_ </strong><em id="obs_11_0057__i981911495353">Time</em><strong id="obs_11_0057__b98402034692"> _</strong><em id="obs_11_0057__i378016356913">TaskId</em><strong id="obs_11_0057__b108401341916">.txt</strong>. For example, the name of the result file for successfully uploading a folder is <strong id="obs_11_0057__b1374351216100">cp_succeed_report_20190417021908_fbbc83e3-98ac-4d19-b23a-64023b1e0c34.txt</strong>, among which, <strong id="obs_11_0057__b28221227141015">fbbc83e3-98ac-4d19-b23a-64023b1e0c34</strong> indicates the task ID.</p>
|
|
<div class="note" id="obs_11_0057__note146662006212"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="obs_11_0057__ul177831590915"><li id="obs_11_0057__li47841759492">If the number of successes, failures, or warnings is zero, the corresponding result file is not generated.</li><li id="obs_11_0057__li266019118108">The task ID of a result list is unique for each operation.</li><li id="obs_11_0057__li91297350411">If there are multiple folders and files and you need to confirm the details of a failed task, refer to the failure result file <strong id="obs_11_0057__obs_11_0013_b5396121718320">cp_failed_report_</strong><em id="obs_11_0057__obs_11_0013_i1639621714325">time</em><strong id="obs_11_0057__obs_11_0013_b1739631753215">_</strong><em id="obs_11_0057__obs_11_0013_i203979172328">TaskId</em><strong id="obs_11_0057__obs_11_0013_b1639718176326">.txt</strong> in the result folder and the <a href="obs_11_0056.html">log files</a> in the log path.</li><li id="obs_11_0057__li10131125115010">The maximum size of a single result file is 30 MB.</li><li id="obs_11_0057__li1516815174319">obsutil can retain a maximum of 1,024 result files and does not automatically clear these files. Once the limit is reached, the task stops running. To prevent the batch operation efficiency from being reduced by too many result files, you need to periodically archive and back up the result files in <strong id="obs_11_0057__b1069320024415">.obsutil_output</strong> to another folder.</li></ul>
|
|
</div></div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="obs_11_0054.html">Fault Locating</a></div>
|
|
</div>
|
|
</div>
|
|
|