Hi, Freenas 9.10
I have a SMB volume opened. I write alot to the dirve, gigs and gigs a day. Large 2g+ files.
Sometimes, not too often, I am seeing 'Invalid file handle' messages trying to delete files on the share from Windows 10. If I go in as root or the smb dataset owner in shell, I can delete them. If I remount the drive, the errors on Windows persist.
I am also seeing errors trying to write random files to this share from windows. I might be writing 150 files from 1k to 3g, and halfway through a message pops up saying 'Administrator access required to complete transfer'. I can mount the drive as root, the share owner etc, nothing works. It is wierd too, if I try to move one file to retest, it will write the file to the NAS, I see it in the directory, pop up the message and when I say cancel, DELETE the nas written file from the NAS.
I have been getting around this error when it happens by sftp'ing the file to the NAS to my home directory, going in shell and mv'ing it to the correct place. That gives no error, but is very slow, as sftp is not the speediest protocol.
I had a old message here saying the handle problem was due to writing using smb to an nfs fileshare, so I switched everything to cifs/smb mounts, and the problem still persists
So this is using win10 to write directly to an smb fileshare, by the fileshare owner. Neither works, but using the same acct using sftp works for the same files!
I have a SMB volume opened. I write alot to the dirve, gigs and gigs a day. Large 2g+ files.
Sometimes, not too often, I am seeing 'Invalid file handle' messages trying to delete files on the share from Windows 10. If I go in as root or the smb dataset owner in shell, I can delete them. If I remount the drive, the errors on Windows persist.
I am also seeing errors trying to write random files to this share from windows. I might be writing 150 files from 1k to 3g, and halfway through a message pops up saying 'Administrator access required to complete transfer'. I can mount the drive as root, the share owner etc, nothing works. It is wierd too, if I try to move one file to retest, it will write the file to the NAS, I see it in the directory, pop up the message and when I say cancel, DELETE the nas written file from the NAS.
I have been getting around this error when it happens by sftp'ing the file to the NAS to my home directory, going in shell and mv'ing it to the correct place. That gives no error, but is very slow, as sftp is not the speediest protocol.
I had a old message here saying the handle problem was due to writing using smb to an nfs fileshare, so I switched everything to cifs/smb mounts, and the problem still persists
So this is using win10 to write directly to an smb fileshare, by the fileshare owner. Neither works, but using the same acct using sftp works for the same files!