Jump to content
Covecube Inc.

Umfriend

Members
  • Content Count

    931
  • Joined

  • Last visited

  • Days Won

    48

Posts posted by Umfriend

  1. That last suggestion of Spider99 is what I was trying to accomplish. Instead of having Lightroom scan Z:\, try a scan on M:\ (no need to hide/unhide files). If that also results in Lightroom scanning C:\ and D:\ then it is not DP related (which I can not imagine anyway) because direct access to M:\ does not go through DP software. But, as Spider said, a real seperate USB drive would work better to show that the issue can be recreated and is not caused by DP at all.

  2. I wonder. If you were to assign a drive letter to one of those 8 drives, say T:\ and then let Lightroom scan T:\, would it then also scan C:\ and D:\? If so, then it really can't be DP related IMHO. It would be even better if you can recreate the issue with a whole other disk, perhaps some USB HDD lying around.

  3. I have never tried to use File Placement Rules but as I understand it, if you tell DP to place \movies on that 6TB HDD then it will and also spill over to other drives when the 6TB HDD is full. DP will not, I think, through a no space error. Not sure how to ensure that non other data arrives on that drive, that might need a lot of FPRs, but may be easy.

    Having said that, I would not add a drive I am suspicious about if, unlike me, you do not use duplication. Do you have Scanner? Maybe run the Seagate tool again.

  4. 8 hours ago, Spider99 said:

    if DP - does not like a file it puts it in the "other" category (box) as its not considered part of the pool

    I think this is confusing. Yes, when you remeasure, DP shows all data as Other at first until it is clear what is Pooled data (on within that, what is duplicated and unduplicated). By default however, Other relates to data on the drives comprising the Pool that resides outside of the hidden PoolPart.* folders. This is data that does occupy space on the Pooled drives but is not actually in the Pool itself. I am not convinced OP's issue has anything to do with Other.

    @OP: Have you tried to read the manual? It points to some logfiles that you can try to have a look at. It is unfortunate that the message you get is rather generic.

    Met vriendelijke groet ;)

  5. I don't know Plex but normally any application that accesses files through the Pool is neither redundancy nor phyiscal location aware. It is not Plex that needs to know what drive has the data, DrivePool does that for you.

    I think that if you have duplication then, yeah, it may read from multiple drives. Mind you, I have never really experienced a performance gain because of this but some say they have.

    I guess that when a drive gets removed/offloaded that that may impact performance somewhat but AFAIK, it is a lower priority task and should hardly interfere with regular I/O, especially if you have the option to prioritise network I/O turned on. So I am not sure what would have caused the non-performance.

  6. Not that I am aware of. Can you explain a bit more?

    What is the setup  - 1 PC local only or are we talking a server and shares?

    Get any error message?

    Can you give an example of a file that you can access one way (what is the full path and filename) but not the other (which full path and filename are you trying)?

    Any messages on the DP dashboard/GUI? What does the Pool look like (screenshot)?

  7. I am not entirely sure but I would consider:
    1. Remove F:\ and select the force or somesuch option
    2. While you're at it, remove the SSD
    3. Locate the relevant data on F:\ (in the PoolPart.* folder) and copy (my preference) or move that into the Pool. The data should spread over Disk 1, D, E and H
    4. Remove Pool L, any drives in there. If not possible, see of Pool L comes up after reboot.
    5. Format F:\
    6. Add F:\ to the Pool
    7. Pool L should be gone but if it is still there then you should be able to clean it up
    8. DP will reallocate files to F:\ once it re-balances

    That's what I would try and if step 3 succeeds then it should be rather risk free.

  8. No worries, we're all friendly here and just trying to help.

    So with default settings the new 8TB HDD would indeed be used and data would be offloaded of some other HDDs. On the SSD Cache / SSD Optimizer, I *think* you are right but I never tried it myself so I am not entirely sure. But there is documentation on the website and you can search the forums, it is a treasure for info.

     

  9. Well, duplication can be turned off easily and DP will remove excess duplicates. Not sure how you got duplication on just two drives. Some screenshots might help.

    The balancing that has occurred will be harder to revert. Why don't you want balancing?

    The only reason to uninstall I can see is if you don;t want to use the software. DP itself is able to reorganise as you want.

  10. I don't understand. At default settings, DP would already re-allocate files so that you would have an optimal distribution. Optimal in that case means that each drive has (approximately) the same amount of free space. If you have SSDs as cache and Scanner then you want to have Scanner at top, then SSD Optimizer.

    You can use the Disk Space Equalizer, I think to get all drives filled to [x]% but see no reason to do that. IMHO, with DP, default settings work very well without complicating matters.

    I think I understand you "seeded" the drives. That is perfectly fine. DP will rearrange files afterwards.

  11. Is thjat 192 read or write. I don't know. SMR drives do well on read and sequential writes. Random writes though above a certain limit though, ouch.

    If 20MB/s is a cap you experience on all drives writing through DP then there is a different issue. Time for some research, e.g. waht do you get on writing to those drives directly? You need to measure this with large, non-single file transfers I think.

  12. So on the two drives that have close to 100% other, what you may want to do is called "seeding":

    1. Stop DP service
    2. On each of these drives, move the data in the current Poolpart.* folder to the new Poolpart.* folder
    3. Start DP (or reboot)
    4. Let DP remeasure / rebalance.

    With the 12TB, if you have a precise product number you could see if, perhaps, it is a SMR drive (although AFAIK, there are no 12TB SMR HDDs by WD

     

     

×
×
  • Create New...