All being meddled with Ubuntu 10.04 Desktop running unraid 4.7.  While moving files from one user share to another to correct a stupid mistake created about a year ago I noticed a few file move complaints from the OS.  It said it could not delete a non empty directory and offered to skip which I did.  I returned back to the empty directory tree and found no reason to keep it so I selected to delete it.  The file was moved to the Trash and then refused to allow the trash to empty the file.

 

I tried the following with no success:

sudo mv .Trash* ~/Desktop
sudo rm -rf .Trash*

rm: cannot remove directory `.Trash-1000/expunged/3561511326/Software and Drivers/Hardware Drivers & SW/External HDD Enclosures/Metal Gear HDD Enclosure Box': Directory not empty

 

The desire is to clean out the contents of the user share so that it can be removed from Unraid.  Any suggestions for file system checks to be done and how to perform them on a single user share or does it need to be applied to all disks?

What is the working directory (pwd)?

What is the working directory (pwd)?

The file systems are on individual disks.  The user-share can be considered an in-memory set of virtual links to the files.

 

You would need to perform a file system check on each file system in your server to determine their health.

 

If a file cannot be deleted, it indicates the DIRECTORY it is in is not writable by the user accessing remotely.  You can check the permissions to see if that is the cause.

 

 

There is a bug in the user share system where a .fuse... file is created and recreated upon deletion in an empty directory in the /mnt/user/ path. Try deleting the directory under the disk mount, e.g., /mnt/disk1/...

Is this the suggested method for performing a file system check on the Unraid box?  I didn't notice any "applies to this version" note and would like to know if this is the only means or if there is another approved way.  http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

There is a bug in the user share system where a .fuse... file is created and recreated upon deletion in an empty directory in the /mnt/user/ path. Try deleting the directory under the disk mount, e.g., /mnt/disk1/...

 

I unmounted the troubled user share and then deleted the directory to which it was mounted.  I created a new directory with a different name and tried again to mount the troubled share to the new directory.  The hidden .Trash folder with the problematic file still exits.

 

Could someone point me out to the proper method for doing a file check using Unraid.  I'm in need of a little reassurance the procedure I previously posted is indeed the correct one I should be following.

Is this the suggested method for performing a file system check on the Unraid box? 

yes

I ran reiserfsck --check /dev/<drive> against every drive in my unraid array except the parity drive as the instructions show.

 

Every drive returned:

No corruptions found

 

Any other suggestions?  How do I know which drive is being used with the particular faulted directory so I can focus my attempts?