Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Google

Our Sites

covecube.com 
community.covecube.com 
blog.covecube.com 
wiki.covecube.com 
bitflock.com 
stablebit.com 

Poll

No poll attached to this discussion.

In order to better support our growing community we've set up a new more powerful forum.


The new forum is at: http://community.covecube.com


The new forum is running IP.Board and will be our primary forum from now on.


This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.


Thank you,

Access issues with build 4039 and 4040

edited October 2011 in DrivePool
Cannot access some of the shares after upgrade. Permission reset feature fails in the middle with error "Cannot find file specified".
Some of the shares do not allow modification and getting error "The file '<%1 NULL:NameDest>' is too large for the destination file system".

Comments

  • Resident Guru
    New build out already, 4055, "Changed reset permissions to apply owner / inheritance rules in separate stages." Any luck with it?
  • Looks like its working now. Still resetting permissions on shares. 
    By any chance is there a way to reset permissions across all shares at once? Or we should reset one-by-one?
  • Looks like it's one by one only.
  • New build out already, 4055, "Changed reset permissions to apply owner / inheritance rules in separate stages." Any luck with it?
    using the beta 4055, still need to reset "permissions" on each "shared folder".
    The files in other shared is very fast to reset, only the pic folder. maybe like several hours.
  • confirmed. now it works.!
  • I've reset all my permissions and everything was fine.  But I've added a new drive to the pool and now I'm getting f"file is too large for destination file system" again.

    Drivepool is still having issues creating the root folders for the shares on the individual drives.  This seems to only happen when it needs to start using a new drive and that folder doesn't already exist.
Sign In or Register to comment.