My mover is working, it moves the files fine to the correct location but then it starts throwing up errors until it fills my tmpfs 100%. So every morning I wake up and the logs are full like this. I just tested it manually and it did it now too.

 

I have attached a syslog. The mover script starts at 18:35:48

 

Thank you.

syslog-2014-02-05-1.txt.zip

Feb  5 18:26:03 Tower kernel: ata6.00: irq_stat 0x40000001

Feb  5 18:26:03 Tower kernel: ata6.00: failed command: READ DMA

Feb  5 18:26:03 Tower kernel: ata6.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in

Feb  5 18:26:03 Tower kernel:          res 61/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)

Feb  5 18:26:03 Tower kernel: ata6.00: status: { DRDY DF ERR }

Feb  5 18:26:03 Tower kernel: ata6.00: error: { ABRT }

Feb  5 18:26:03 Tower kernel: ata6.00: failed to enable AA (error_mask=0x1)

Feb  5 18:26:03 Tower kernel: ata6.00: failed to enable AA (error_mask=0x1)

Feb  5 18:26:03 Tower kernel: ata6.00: configured for UDMA/133 (device error ignored)

Feb  5 18:26:03 Tower kernel: ata6: EH complete

Feb  5 18:26:03 Tower kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Lots of these...starting at line 6 of the log.

I'd suspect a failing drive. Probably this one:

WDC_WD4001FAEX-00MJRA0_WD-WCC130202339

I'd then run SMART reports on this drives for sure.

 

If that doesn't point to the problem, then I'd run SMART on all drives.

If still nothing jumps out, I'd run Reiserfsck on all the drives.

 

 

http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

Thank you for the tips Dale, after many hours of reading and looking through the file structure, trying many different things I have solved my issue.

 

I did all that you suggested, and yes that one disk is in trouble, it wasn't part of the Array it was just connected to run some tests on it.

 

I also ran the Reiserfsck on all of the disks and all came back clean. I ran the new permissions from the settings to see if maybe it was a permission issue but the issue persisted.

 

So after reading how mnt/usr0 is the mnt that mover uses to pass files through to the array I saw an apps folder in there, where my apps folder from the cache drive is set to cache only. I tried to create a new directory in there as a test in Midnight Commander and I got the same Error 28 from my logs. I decided to delete this apps folder and try and run the mover script again, everything worked perfectly now.