<li>Automatically add cross-seed torrents in a paused state. <em>Note: cross-seed now allows for torrent injections directly to qBit, making this feature obsolete.</em></li>
<li>Automatically add cross-seed torrents in a paused state. <em>Note: cross-seed now allows for torrent injections directly to qBit, making this feature obsolete.</em></li>
<li>Recheck paused torrents sorted by lowest size and resume if completed</li>
<li>Recheck paused torrents sorted by lowest size and resume if completed</li>
<li>Remove orphaned files from your root directory that are not referenced by qBittorrent</li>
<li>Remove orphaned files from your root directory that are not referenced by qBittorrent</li>
<li>Tag any torrents that have no hardlinks and allow the option to cleanup to delete these torrents and contents based on maximum ratio and/or time-seeded</li>
<li>Tag any torrents that have no hardlinks and allow the option to cleanup to delete these torrents and contents based on maximum ratio and/or time-seeded</li>
<li>RecycleBin function to move files into a RecycleBin folder instead of deleting the data directly when deleting a torrent</li>
<li>RecycleBin function to move files into a RecycleBin folder instead of deleting the data directly when deleting a torrent</li>
<li>Built-in scheduler to run the script every x minutes. (Can use --run command to run without the scheduler)</li>
<li>Built-in scheduler to run the script every x minutes. (Can use --run command to run without the scheduler)</li>
<li>Webhook notifications with Notifiarr and Apprise API integration.</li>
<li>Webhook notifications with Notifiarr and Apprise API integration.</li>
<p>Sonarr, Radarr, and Lidarr get access to everything because the download folder(s) and media folder will need to look like and be one mount, on the file system. Hard links will work properly and any moves will be atomic, rather than copying and deleting.</p>
<p>Sonarr, Radarr, and Lidarr get access to everything because the download folder(s) and media folder will need to look like and be one mount, on the file system. hardlinks will work properly and any moves will be atomic, rather than copying and deleting.</p>
<p>Windows is less flexible than some other operating systems in respect of support for hardlinks and instant (Atomic) moves. In most cases, you need to use a single disk containing both your download location and media library. However, there is an option detailed below that will allow you to make use of hardlinks and instant (Atomic) moves if you run a two-disk setup.</p>
<p>Windows is less flexible than some other operating systems in respect of support for hardlinks and instant (Atomic) moves. In most cases, you need to use a single disk containing both your download location and media library. However, there is an option detailed below that will allow you to make use of hardlinks and instant (Atomic) moves if you run a two-disk setup.</p>
<p>If you want to make extensive use of hardlinks, we would recommend switching to another operating system. For more information and suggestions on this topic, join our Discord support channel. The link can be found at the bottom of every guide page.</p>
<p>If you want to make extensive use of hardlinks, we would recommend switching to another operating system. For more information and suggestions on this topic, join our Discord support channel. The link can be found at the bottom of every guide page.</p>
<p>If moving away from using Windows with multiple disks is not an option, we suggest ignoring hardlinks and instant (Atomic) moves and using <ahref="https://stablebit.com/"rel="noopener noreferrer"target="_blank">StableBit DrivePool</a>. This will allow you to pool multiple disks to appear as one big disk, making it much easier to maintain and set up your file and folder structure.</p>
<p>If moving away from using Windows with multiple disks is not an option, we suggest ignoring hardlinks and instant (Atomic) moves and using <ahref="https://stablebit.com/"rel="noopener noreferrer"target="_blank">StableBit DrivePool</a>. This will allow you to pool multiple disks to appear as one big disk, making it much easier to maintain and set up your file and folder structure.</p>
<divclass="admonition warning">
<divclass="admonition warning">
<pclass="admonition-title">It is possible that Windows Storage Spaces supports hardlinks, but this has not been verified by the Guides team. We are unable to provide support for setups that use Storage Spaces.</p>
<pclass="admonition-title">It is possible that Windows Storage Spaces supports hardlinks, but this has not been verified by the Guides team. We are unable to provide support for setups that use Storage Spaces.</p>
<p>The <code>data</code> folder has sub-folders for <code>torrents</code> and <code>usenet</code>, and each of these has sub-folders for <code>tv</code>, <code>movie</code>, and <code>music</code> downloads to keep things organized.</p>
<p>The <code>data</code> folder has sub-folders for <code>torrents</code> and <code>usenet</code>, and each of these has sub-folders for <code>tv</code>, <code>movie</code>, and <code>music</code> downloads to keep things organized.</p>
@ -3809,7 +3809,7 @@ However, for the paths, use the info provided below depending on whether you hav
<pclass="admonition-title">Windows only allows a maximum of 1023 hardlinks per file</p>
<pclass="admonition-title">Windows only allows a maximum of 1023 hardlinks per file</p>
</div>
</div>
<divclass="admonition warning">
<divclass="admonition warning">
<pclass="admonition-title">The <code>-Q</code> or <code>--quick</code> option only reads each file once, hashes it, and performs comparisons based solely on the hashes. There is a small but significant risk of a hash collision which is the purpose of the failsafe byte-for-byte comparison that this option explicitly bypasses. Do not use it on ANY data set for which any amount of data loss is unacceptable. You have been warned!</p>
<pclass="admonition-title">The <code>-Q</code> or <code>--quick</code> option only reads each file once, hashes it, and performs comparisons based solely on the hashes. There is a small but significant risk of a hash collision which is the purpose of the failsafe byte-for-byte comparison that this option explicitly bypasses. Do not use it on ANY data set for which any amount of data loss is unacceptable. You have been warned!</p>
4 weeks ago