"file in use" when wifi dropped

[aoaaron]

I was copying some media files to my unraid (copy via mac OSX) from my MBP over wifi when my wifi connection dropped. Therefore the transfer messed up.

 

now I cannot delete the temporary file which was made before the move (its 0kb instead of 180mb but has the same name).

what can i do to fix this problem. its very annoying since i can't copy over that file now!!

 

solutions?

[lionelhutz]

You'll likely have to log-on to the server and delete the file that way. Try using midnight commander (type mc) and then the user shares can be found in /mnt/user. You can also cd there and then use rm to remove the file.

 

Peter

[aoaaron]

I can't stop the array either.

 

this is showing:

Jul 27 03:53:20 Tower emhttp: Retry unmounting user share(s)...

Jul 27 03:53:25 Tower emhttp: shcmd (311): umount /mnt/user >/dev/null 2>&1

Jul 27 03:53:25 Tower emhttp: _shcmd: shcmd (311): exit status: 1

Jul 27 03:53:25 Tower emhttp: shcmd (312): rmdir /mnt/user >/dev/null 2>&1

Jul 27 03:53:25 Tower emhttp: _shcmd: shcmd (312): exit status: 1

Jul 27 03:53:25 Tower emhttp: Retry unmounting user share(s)...

 

The time seems off though since its 20:51 here.

 

I'll try to log on now and delete the file.

[aoaaron]

You'll likely have to log-on to the server and delete the file that way. Try using midnight commander (type mc) and then the user shares can be found in /mnt/user. You can also cd there and then use rm to remove the file.

 

Peter

 

I'm sorry I don't quite understand this. I don't even know where the file is now because I can't access it. I went onto the server management http:// and its crashed. The array says its stopping but its not.

[lionelhutz]

My guess would be that the operation running on the server side during the move has hung-up. You may have to either kill the process or just reset the server, with killing the process being the preferred option. Here's a post by Joe with some good info.

 

You can type kill xxx, where xxx = the process ID to kill the process.

 

The interface may have been killed due to the syslog taking memory. See what you can do. If you get the disks unmounted then a simple "reboot" or "shutdown -r now" on the command line will be fine. If all else fails, that will reboot it anyways.

 

Peter

[aoaaron]

I unmounted using unmenu and rebooted.

 

Thanks guys.