Hi, I've been experiencing this problem for a while now and its driving me nuts. Whenever I delete some files from a user share, the array starts giving me access denied on all files/folders of that user share. Only way I found to fix that problem is to stop/start the array. It seems to happen more often when I'm accessing files on the array while deleting.

 

Is this a known issue and if so, is there a permanent fix/workaround? If not, let me know which logs you'd want to see and I'll try grabbing them next time the error occurs. ( I can reproduce the problem quite easily )

 

Thx

Is this a known issue and if so, is there a permanent fix/workaround?

The user-share code was almost complete re-written to fix issues like this and to make it so it automatically updated itself when disk shares were written directly.

The permanent fix is for you to upgrade to 4.3-b6. (or 4.3-final when available, as it is long overdue and could be released at any time)

You only need to download and unzip the 4.3b6 release, then copy the bzroot and bzimage from it to your flash drive.  You can do this while your array is running if you make your flash drive visible as a share.

 

Before you stop the array, make note of all the disks and their positions in the array.  Most times the new release of linux will keep them in the same order, but on a rare occasion, it will scan the hardware in a different order and what used to be /dev/sda might end up as /dev/sdb.  This is not an issue unless the parity drive ends up in a data slot.  If this occurs, the array will not start, you will need to go to the "devices" tab on the user interface, and put the disks back where they were.

 

In any case, once you put the two new files from the 4.3 release on the flash drive, stop the array and press the reboot button.  Your server will reboot, and the issue you are describing when deleting files should be behind you.  If you wish, before copying the two upgrade release files to your flash drive you can rename the existing two files to bzroot42 and bzimage42.  That way you can undo the upgrade easily by renaming them back to their original names and rebooting the server.

 

Joe L.