oztoppy Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
keith_leitch

Senior Member
Registered:
Posts: 595
Reply with quote  #1 
Hi,

I'm not 100% sure that this is the right place to post this question. It's about a phenomenon that's occurred only once, so far, in which a recording was left under a mount-point folder on the client even after the server was shut off.

To elaborate:

  1. I had several recordings of "The Big Bang Theory" on "PVR A" (which acts here as the server).
  2. I connected "PVR B" (which acts here as the client). All of PVR A's recordings appeared under the mount-point as expected.
  3. I shut down PVR A.
  4. On PVR B, the name of the mount-point did NOT disappear as expected, but there was one recording of "The Big Bang Theory" under it. This played normally as though it was stored on the local machine.
  5. I fired up PVR A, and all recordings reappared on PVR B as expected.
  6. I shut down PVR A, and the mount-point on PVR B disappeared as expected.

I wasn't paying close enough attention to whether the stray episode was somehow copied or moved to the client. It may have been deleted in step 5 or step 6 (though I don't particularly care about losing it).

If this rings a bell with anyone, please let me know if something about my practice may have caused it.

0
DeltaMikeCharlie

Mostly Harmless
Registered:
Posts: 274
Reply with quote  #2 
This can probably be explained by the convoluted combination of 'soft links' and 'mount points' required to make TMSServer/TMSClient not reboot where multiple PVRs have multiple roles.  This can be seen in the nfs script, but to summarise:

When TMSClient connects to TMSServer, it creates a directory called '/nnt/hd/MountPoints/{Server MAC Address}' and underneath that, there is one directory created for each of the shares that the server is advertising.  For example: '/nnt/hd/MountPoints/{Server MAC Address}/_mnt_hd_DataFiles/'.

Following this example, each share is individually mounted to its mountpoint directory and then there is a soft link created in the client's 'DataFiles' directory called '@{Server Name}' that points to the appropriate mountpoint directory.

If you were recording a broadcast on PVR B (client) but recording to PVR A (server) via NFS and you tried to either stop TMSClient or TMSServer.  The nfs disconnect script on PVR B would not be able to clean-up the mountpoints (because of files in use), but also, PVR B would keep recording to that mountpoint.  This would explain the file because it was actually on the local HDD.

Once the recording had stopped and TMSClient reconnected to TMSServer, the nfs mount would have effectively hidden the local files in the mountpoint and when finally TMSServer was stopped, TMSClient could now clean-up the mountpoints effectively deleting the recording file lurking within.
0
keith_leitch

Senior Member
Registered:
Posts: 595
Reply with quote  #3 
Thanks. I've never (purposely) recorded across a mount-point, but I have noticed that Automove often picks up a folder on another machine and tries to move a file to it. The way I read your explanation is that if such a move were happening at the time of a disconnect, something similar could have happened. Or, maybe I was doing a background copy during a disconnect, or something.

Anyway, I will keep an eye out. I fully expect that it won't happen again.
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.