# Question on Global/Parent File Policy

**URL:** <https://kopia.discourse.group/t/question-on-global-parent-file-policy/1056>\
**Category:** Support\
**Created:** [April 22, 2022, 2:58pm UTC](https://kopia.discourse.group/t/question-on-global-parent-file-policy/1056 "2022-04-22T14:58:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kopanla](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/kopanla/32/243_2.png) [@kopanla](https://kopia.discourse.group/u/kopanla)\
**Post date:** [April 23, 2022, 9:18am UTC](https://kopia.discourse.group/t/question-on-global-parent-file-policy/1056/2 "2022-04-23T09:18:27Z")

</div>

There could be a bug. At least I found one (actually two) related to noParentIgnore rules. See also

> [@"files noParentIgnore"](https://kopia.discourse.group/t/files-noparentignore/755/4):
>
> Here is small repro to demonstrate the bug: kopia repository create filesystem --path w:\parent kopia maintenance set --enable-full=false kopia maintenance set --enable-quick=false kopia cache set --content-cache-size-mb=1000 kopia cache set --metadata-cache-size-mb=1000 kopia policy set --global --ignore-cache-dirs=false kopia policy set --global --compression=zstd kopia policy set --global --log-dir-snapshotted=0 kopia policy set --global --log-dir-ignored=10 kopia policy set --global --log…

But it would save the developer quite some time (and increase his motivation to look into this…) if you created a simple reproducer with a few commands that the developer could run as well. See also my example.

---

_[View the full topic](https://kopia.discourse.group/t/question-on-global-parent-file-policy/1056)._