Hello -

 

Firstly, I'm running 6.7.0-rc2 but this also happened with previous stable versions.

 

I ran the extended test from "CA Fix Common Problems" by @Squid and it reported a bunch of duplicate files on disk1 and disk3.  The plugin is definitely correct as I manually verified the results.

 

To resolve this the quickest way I could think of, I backed up the share's contents, removed the share completely, verified it was gone, then recreated it.  I then verified the share was empty and only on disk3.  I did this via SSH and the unRAID GUI.

 

I'm now re-uploading files to the new share via SFTP - this is being done by uploading to /mnt/user/<share>.

 

Note 1: This share has cache set to "No".

 

Questions are as follows:

 

- I'm being asked if I want to overwrite existing files - why?  The share is definitely empty before I start uploading. I think my SFTP client had the same file in the queue more than once.  I have cleared the queue and the overwrite prompt has gone away.

- From an end-user perspective, what is /mnt/user/ vs /mnt/user0?  I found another post that says it is cache vs no cache - should I be using /mnt/user0 for the re-upload process instead of /mnt/user?

- All my shares are accessed by NFS (I don't use SAMBA, at all).  When mounting an NFS share, should I be mounting /mnt/user/<share> or /mnt/user0/<share>?

- What causes duplicates like this?  I have used the unBALANCE plugin in the past but never on this share's files.

 

Note 2: I've been using /mnt/user/<share> since I first setup unRAID and it's always worked perfectly fine.  When browsing on my clients I can only see single copies of the files, which makes sense.  No other shares showed any duplicates in the CA Fix Common Problems report.

 

Thanks

Edited January 28, 20197 yr by digitalformula
Clarify note about unBALANCE

Additional info ...

 

The original duplicates reported by CA Fix Common Problems are no longer duplicated.  Now, though, a whole lot that weren't duplicated before *ARE* duplicated.

 

Why?

Did you make sure that the share had no files on the cache before you started?    Setting Use Cache to No will leave them there and could poss9bly result in the duplicate files you are seeing as new copies are written to array disks.   When reading files Unraid always looks at all disk regardless of the Use Cache setting.    The Use Cache setting is only used to determine where a new file is to be placed.

 

BTW:   The difference between /mnt/user and /mnt/user0 is that the latter only includes array disks, while the former includes both array disks and the cache disk(s).

11 hours ago, itimpi said:

Did you make sure that the share had no files on the cache before you started?    Setting Use Cache to No will leave them there and could poss9bly result in the duplicate files you are seeing as new copies are written to array disks.   When reading files Unraid always looks at all disk regardless of the Use Cache setting.    The Use Cache setting is only used to determine where a new file is to be placed.

 

BTW:   The difference between /mnt/user and /mnt/user0 is that the latter only includes array disks, while the former includes both array disks and the cache disk(s).

 

Yes, I did check the cache before doing any of this.  That share had no files on either of the cache pool members.  This share has never been configured to use cache.

 

Thanks for clarifying the /mnt/user vs /mnt/user0 thing.  That's good to know.