<div dir="ltr"><br><br><div class="gmail_quote">On Fri, Sep 5, 2008 at 3:48 PM, Brad DerManouelian <span dir="ltr"><<a href="mailto:myth@dermanouelian.com">myth@dermanouelian.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div><div class="Ih2E3d"><div>On Sep 5, 2008, at 1:25 PM, Ryan Steffes wrote:</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_quote"><div>Been playing <a href="http://myth.find_orphans.pl" target="_blank">myth.find_orphans.pl</a>, it seems to me that I get a number of false positives for "unknown files" due to having overlapping storage groups on multiple backends. The reason is because it's pulling the list of known files for a single backend, so files attributed to another backend in the same storagegroup are seen as unknown files.<br>
<br>What I'm debating is whether it's "better" behavior to simply disable the hostname check and check for all files or to check unknown files against other backends.<br><br>Anyone have a strong opinion?</div>
</div></div></blockquote><div><br></div></div>Is "overlapping storage groups on multiple backends" a supported configuration? Seems to me like every backend should have their own storage group.</div></div></blockquote>
<div><br>I'd kinda expected it to be the most common configuration, especially since the backend can prioritize hard drive by location and fullness, at least among people who use storage groups. <br></div></div><br></div>