Background
I have just installed two new 4TB HDD:s (mirror) due to insufficient free space on the old ones. The old 2TB HDD:s constitute Volume1 and the new ones Volume2. Following this I have copied all files from Volume1 to an identical structure on Volume2. I copied using command 'cp - R' in the FreeNAS shell. There is probably a prettier solution to my migration of files, via Rsync or so I guess, but that is not my principal concern at this point.
The setup is essentially:
1. UserComputer
2. RemoteComputer
3. FreeNAS
4. AirportExtreme (TimeCapsule)
Where FreeNAS and RemoteComputer is connected via ethernet cable to AirportExtreme, and UserComputer is connected via Wifi to AirportExtreme.
Problem
In addition to above I also had files on RemoteComputer which I wanted to copy to FreeNAS. From UserComputer (Wifi connected) I logged in to the FreeNAS shell in order to transfer movie files (mkv) from RemoteComputer. I used the following command:
scp -r User@RemoteComputerIP:/FileLocationOnRemotecomputer/Filename* /mnt/FreeNAS/DestinationFolder
This seems to have worked fine for the first batch of files, but for a subsequent single file the transfer went fine (on the face of it), but I am unable to open it from the FreeNAS location using Finder (OSX 10.11.2, i.e. El Capitan). File is visible, but when I double-click it and VLC tries to execute it I receive the message:
File reading failed
VLC could not open the file (No such file or directory ).
Your input can't be opened
VLC is unable to open the MRL
I AM still able to open the file from its original location on RemoteComputer (from UserComputer), so it is not a question of original sin, but rather something in the transfer or FreeNAS.
At first I was able to delete the file (via Finder) in so much that I did not receive an error message, however, the file remained. I also checked via the FreeNAS shell and the file was still there. Now, after having written this ticket, I was suddenly able to remove the file via Finder, but upon checking in the FreeNAS shell it was still there. And now it is back in Finder too.
To add to the problem picture - I yesterday mass transferred a big number of movie files (from Volume1 to Volume2 using the cp command) prior to the above operation. And I found that a few files had incorrect 'Kind' ('Type' in Windows I believe), e.g. two mpg-files where portrayed as Folder and hence unable to open with VLC. Today, those two files seem correct, i.e. portrayed as MPEG and possible to open with VLC.
Questions
As I have transferred a lot of files I am in no position to click on each file in this manner to verify the correctness. So...does anybody recognize the problem, or have a solution suggestion? Can FreeNAS act strange in this way following a mass transfer of files, but eventually stabilize?
It probably should be mentioned that following the mass transfer I cross-checked the number of files in and size of the top datasets with subfolders and they corresponded, so everything looked fine on the face of it.
Noteworthy is also that I today cleared the Finder cache in order to zero any issues with indexing (not sure that this would solve it, but that is what I have done still the same).
I tried to include all relevant info, but if something is missing, do not hesitate to ask and I will complement.
I have just installed two new 4TB HDD:s (mirror) due to insufficient free space on the old ones. The old 2TB HDD:s constitute Volume1 and the new ones Volume2. Following this I have copied all files from Volume1 to an identical structure on Volume2. I copied using command 'cp - R' in the FreeNAS shell. There is probably a prettier solution to my migration of files, via Rsync or so I guess, but that is not my principal concern at this point.
The setup is essentially:
1. UserComputer
2. RemoteComputer
3. FreeNAS
4. AirportExtreme (TimeCapsule)
Where FreeNAS and RemoteComputer is connected via ethernet cable to AirportExtreme, and UserComputer is connected via Wifi to AirportExtreme.
Problem
In addition to above I also had files on RemoteComputer which I wanted to copy to FreeNAS. From UserComputer (Wifi connected) I logged in to the FreeNAS shell in order to transfer movie files (mkv) from RemoteComputer. I used the following command:
scp -r User@RemoteComputerIP:/FileLocationOnRemotecomputer/Filename* /mnt/FreeNAS/DestinationFolder
This seems to have worked fine for the first batch of files, but for a subsequent single file the transfer went fine (on the face of it), but I am unable to open it from the FreeNAS location using Finder (OSX 10.11.2, i.e. El Capitan). File is visible, but when I double-click it and VLC tries to execute it I receive the message:
File reading failed
VLC could not open the file (No such file or directory ).
Your input can't be opened
VLC is unable to open the MRL
I AM still able to open the file from its original location on RemoteComputer (from UserComputer), so it is not a question of original sin, but rather something in the transfer or FreeNAS.
At first I was able to delete the file (via Finder) in so much that I did not receive an error message, however, the file remained. I also checked via the FreeNAS shell and the file was still there. Now, after having written this ticket, I was suddenly able to remove the file via Finder, but upon checking in the FreeNAS shell it was still there. And now it is back in Finder too.
To add to the problem picture - I yesterday mass transferred a big number of movie files (from Volume1 to Volume2 using the cp command) prior to the above operation. And I found that a few files had incorrect 'Kind' ('Type' in Windows I believe), e.g. two mpg-files where portrayed as Folder and hence unable to open with VLC. Today, those two files seem correct, i.e. portrayed as MPEG and possible to open with VLC.
Questions
As I have transferred a lot of files I am in no position to click on each file in this manner to verify the correctness. So...does anybody recognize the problem, or have a solution suggestion? Can FreeNAS act strange in this way following a mass transfer of files, but eventually stabilize?
It probably should be mentioned that following the mass transfer I cross-checked the number of files in and size of the top datasets with subfolders and they corresponded, so everything looked fine on the face of it.
Noteworthy is also that I today cleared the Finder cache in order to zero any issues with indexing (not sure that this would solve it, but that is what I have done still the same).
I tried to include all relevant info, but if something is missing, do not hesitate to ask and I will complement.