Jump to content
Covecube Inc.

Royce Daniel

Members
  • Content Count

    26
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    Royce Daniel got a reaction from Christopher (Drashna) in Plex Cloud and Stablebit   
    Nope. Just the same Reddit threads that Drash has already pointed out. Talk about popcorn eating entertainment...
  2. Like
    Royce Daniel got a reaction from Spider99 in Plex Cloud and Stablebit   
    I'm sure at some point there might be some kind of a "crack down" because there will be users who will abuse the service. Let's face it, if a would be Pirate wants to store and run copy protected material unencrypted... they are going to get caught. From what I've read Plex Cloud doesn't encrypt the content you upload via Plex to Amazon Cloud Drive which means Amazon has the ability to see what you have stored and examine it. If it contains embedded metadata suggesting that it was obtained illegally... your toast. If I were a rogue user I wouldn't use it.
     
     
    People talk about Amazon Cloud Drive / Plex Cloud as a private Netflix. I don't see it. Netflix has a shared video library where multiple users can view the same file. If every movie nut in the world has a private collection of 10TB or more... holy data Armageddon batman! Amazon has some amazing search algorithms they use to manage their data in various ways. With Amazon's TOS they have the ability to use those algorithms on your "private" movie libraries. Who's to say they aren't DE-duping to some extent and linking metadata among users accounts? It's a multi-tenant environment. Could easily be done. Plex's TOS allows for it too.
     
     
    I'm adding this topic to my daily news search because I think at some point there are going to be some really interesting stories that come out from this...

     
  3. Like
    Royce Daniel got a reaction from Christopher (Drashna) in Plex Cloud and Stablebit   
    I'm sure at some point there might be some kind of a "crack down" because there will be users who will abuse the service. Let's face it, if a would be Pirate wants to store and run copy protected material unencrypted... they are going to get caught. From what I've read Plex Cloud doesn't encrypt the content you upload via Plex to Amazon Cloud Drive which means Amazon has the ability to see what you have stored and examine it. If it contains embedded metadata suggesting that it was obtained illegally... your toast. If I were a rogue user I wouldn't use it.
     
     
    People talk about Amazon Cloud Drive / Plex Cloud as a private Netflix. I don't see it. Netflix has a shared video library where multiple users can view the same file. If every movie nut in the world has a private collection of 10TB or more... holy data Armageddon batman! Amazon has some amazing search algorithms they use to manage their data in various ways. With Amazon's TOS they have the ability to use those algorithms on your "private" movie libraries. Who's to say they aren't DE-duping to some extent and linking metadata among users accounts? It's a multi-tenant environment. Could easily be done. Plex's TOS allows for it too.
     
     
    I'm adding this topic to my daily news search because I think at some point there are going to be some really interesting stories that come out from this...

     
  4. Like
    Royce Daniel got a reaction from Christopher (Drashna) in Adding REFS drives with data to a pool results in no data showing in pooled volume   
    O.K. So now I understand the underlying architecture. The StableBit DrivePool is actually a "fake" volume... at least fake from the perspective of Windows Explorer and Disk Manager. It's labeled as an NTFS volume but it's really not. AND you CAN add a bunch of ReFS drives to a DrivePool with data and move that data into the DrivePool without having to re-copy any files. When you add an already formatted volume to a DrivePool it creates a hidden folder named (in my case) PoolPart.5de19635-8ccf-4b71-8cc6-e389a29406c3. Each GUID will be different on each drive that you add to the DrivePool. This PoolPart folder is your DrivePool root directory. Upon first adding a drive with data, all your data will be in the normal root directory of the hard drive (top arrow). Just move all the data into the PoolPart folder following the layout of your folder hierarchy in each drive (bottom arrow). The screenshot shows each HD mounted to a folder instead of a drive letter so your view might be different from mine. I mounted the DrivePool drive to an actual Drive Letter.
     

     
    To answer my earlier question about having an NTFS virtual volume on top of an ReFS logical volume... it's not a TRUE virtual volume it's a linked directory hierarchy made to look like a drive volume - similar to DFS? It's a true ReFS volume with all the benefits therein. Unless there are some other fancy things happening under the hood that I can't see and of course I could be totally wrong here but, I moved 12TB worth of data into a fresh DrivePool in under 5 seconds and it all showed up properly in the mounted DrivePool root. Most storage nerds will tell you that it's not really moving the files around on the storage media but more or less updating the volumes metadata; that's why it's so fast compared to copying or copying/moving to another hard drive.
     
    /cheers
×
×
  • Create New...