Hi,

 

I'm the guy who attached a drive to the eSATA port in a pre-build machine giving 16 drives (14 internal array, 1 external array, 1 parity) in total. This didn't work until 4.3.2. Now it's fixed.

 

I do have a share "Projects" defined as disk1-14. The new 16th drive (the eSATA one) was cleared, formatted and attached to the array as disk15. With mc I moved files and folders from the "Projects" share to the new 15th drive (disk15). Note: This drive is not part of the Share.

 

I received an error that the folders/files couldn't be deleted. I did it again and afterwards the folders and files (worth around 40GB) were gone.

 

It seems that the new drive is part of the Share even if it is not included.

 

Perhaps a loop/count error?

 

If you need some more information please let me know.

 

Thanks.

Harald

 

 

*EDIT*: I copied some files to disk15 and they appear in the Share that is defined as disk1-14. Definetely an error.

 

Can't reproduce this behavior, though didn't use MC.

 

Can you set up a case which fails using the command line, or using Windows Explorer?

 

If you look on your flash in the 'config/shares' directory, there is a config file for each share - I'd like to see it for your Projects share.

Can't reproduce this behavior, though didn't use MC.

 

Just a question before I  post everything:

 

I create a share named "Foo" with included disks "disk1-14". Now I create a folder named "Foo" on disk15. What is the expected behaviour? My guess is: It's included in the Share and the included disk definition is overwritten. Can this happen?

 

Thanks

Harald

 

 

I create a share named "Foo" with included disks "disk1-14". Now I create a folder named "Foo" on disk15. What is the expected behaviour? My guess is: It's included in the Share and the included disk definition is overwritten. Can this happen?

 

 

When you access the share Foo, it will include the files under Foo on all disks, regardless of included/excluded disks setting.

 

The included disks/excluded disks settings for a share only serve to define the set of disks that a new object (file or directory) can possibly be created on at the time of creation.

When you access the share Foo, it will include the files under Foo on all disks, regardless of included/excluded disks setting.

 

The included disks/excluded disks settings for a share only serve to define the set of disks that a new object (file or directory) can possibly be created on at the time of creation.

 

Ok, I see. Seems that I missed a thing. I named a folder the same on a disk, that was not included in a share, as a share itself. At that point the folder content of the not included disk became part of the share and the disk became included. So I moved my files from the share to the share. The first error of mc told me that the files are in use. I deleted again and both, the source and the target, were gone.

 

Very complicated. I did expect that the included disk field is the border around my share. At least the label "Included disks" implies that.

 

So everybody should be warned. Never ever name a folder the same as a share - even if the disk is not included.

 

Regards

Harald