<br><br>
<div class="gmail_quote">On Wed, Oct 6, 2010 at 2:53 AM, Iain Buchanan <span dir="ltr"><<a href="mailto:iaindb@netspace.net.au">iaindb@netspace.net.au</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im"><br>On 10/05/2010 08:30 PM, Brian J. Murrell wrote:<br>> Let's say I have two disks/directories in a storage group and I want to<br>> prevent one of them (because it's stupid XFS and corrupting on write --<br>
> the last time I will ever use XFS) from being written to further yet I<br>> want to leave it in the storage group for reading from.<br>><br>> Can I instruct myth to use it only for reading from?<br><br></div>
why not use that bash script someone wrote? (looking...)<br>MythMediaMonitor!<br><br>Take the XFS directory out of the storage directory list, then make a<br>new partition (Ext3 or whatever) and put that in your storage directory<br>
list. Run MythMediaMonitor over the XFS directory, and it will create<br>simlinks in the ext3 directory back to your XFS directory, not touching<br>XFS at all.<br><br>So far MythMediaMonitor doesn't touch the underlying files when myth<br>
deletes the symlinks.<br><br>The second advantage of this is that any NEW recorded stuff will go in<br>your ext3 directory, again leaving XFS alone.<br><br>ooooohh, sounds like a plan!!<br><br>;)<br><font color="#888888">--</font></blockquote>
<div> </div>
<div>I second Ian's solution... however I am not sure that a MythMediaMonitor is really necessary... you could just as easily do it with a single command from the command line. (<a href="http://www.commandlinefu.com/commands/view/1225/symlink-all-files-from-a-base-directory-to-a-target-directory">http://www.commandlinefu.com/commands/view/1225/symlink-all-files-from-a-base-directory-to-a-target-directory</a>)</div>
<div> </div>
<div>Just create a new folder, point your Storage Group at it, and symlink all of the data from your old folder into it. Might be some permissions issues to resolve, but it should work. Not sure it will handle delete's right though.</div>
</div>