<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.covecube.com/index.php?action=history&amp;feed=atom&amp;title=StableBit_DrivePool_F720</id>
	<title>StableBit DrivePool F720 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.covecube.com/index.php?action=history&amp;feed=atom&amp;title=StableBit_DrivePool_F720"/>
	<link rel="alternate" type="text/html" href="https://wiki.covecube.com/index.php?title=StableBit_DrivePool_F720&amp;action=history"/>
	<updated>2026-04-28T21:08:59Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.35.1</generator>
	<entry>
		<id>https://wiki.covecube.com/index.php?title=StableBit_DrivePool_F720&amp;diff=715&amp;oldid=prev</id>
		<title>Christopher: Created page with &quot;==Question== When I move the Plex Media Server&#039;s database to the pool, the images no longer appear in the Plex UI. Why does this happen? ==Answer== The reason for this is that Pl...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.covecube.com/index.php?title=StableBit_DrivePool_F720&amp;diff=715&amp;oldid=prev"/>
		<updated>2014-07-17T07:13:43Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;==Question== When I move the Plex Media Server&amp;#039;s database to the pool, the images no longer appear in the Plex UI. Why does this happen? ==Answer== The reason for this is that Pl...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;==Question==&lt;br /&gt;
When I move the Plex Media Server&amp;#039;s database to the pool, the images no longer appear in the Plex UI. Why does this happen?&lt;br /&gt;
==Answer==&lt;br /&gt;
The reason for this is that Plex uses Hard Links to &amp;quot;cross link&amp;quot; all their local media cache images. That means they can have the files located in multiple locations, but only one copy of the actual file. It is a rather efficient method of storing the files. The problem with this method is that hard links only work on the same volume. You can&amp;#039;t have hard links to files on other volumes. Ever. You can use symbolic links to do this, but that&amp;#039;s not Plex uses.&lt;br /&gt;
&lt;br /&gt;
Now, you&amp;#039;re asking yourself &amp;quot;Well, StableBit DrivePool creates one large volume. So that shouldn&amp;#039;t be an issue. Right?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
The problem is that the pool drive is a virtual drive. There isn&amp;#039;t an actual file system. We just pass on the requests to the actual disks in the pool. Reparse points changes how that&amp;#039;s handled a bit, but it&amp;#039;s still essentially true. More importantly, while the pool appears to have a file system, it really doesn&amp;#039;t. Hard links work inside NTFS, they depend on NTFS metadata and are a fundamental property of how NTFS works. &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;This all means that hard links do not work on the pool at all.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Since Plex uses hard links to link all of it&amp;#039;s image metadata together, rather than using a database to do this, that means that it cannot properly store the image metadata one the pool.&lt;/div&gt;</summary>
		<author><name>Christopher</name></author>
	</entry>
</feed>