Currently if the log file grows (perhaps through some error) to fill the flash drive, the webgui becomes unresponsive, IMHO, this is a bug.
Normally, the way this is handed is by a line in the log file that says something like >XXX lines similar to ZZZZ rather than expanding to fill all available size, alternatively, truncating part of the log file.
I don't use mover, syslog server is not mirrored to flash. I haven't tried to look at the log file when it happens, no drives or shares are shown but clients can still access shares, reboot and shutdown tabs don't work. I will try and look at the log file next time it happens.
The split level is set so that no directories are on more than one disk.
The directories already exist on these disks, so unraid should only add them into the existing directories.
It works perfectly on 15 disks but not 2 of the disks. It thinks the disks are full, which they are not.
The use case is new episodes of an existing TV series.
I am not at home, I will check in a couple of days, but I think the settings are the same on all 17 disks, only 2 behave differently.
FWIW, copying to the share where these 2 disks were involved, used to hit an error not enough space, but if you hit try again a few times, would eventually complete successfully.
Multiple XFS drives in the array
all drives circa 1TB free space
Only one share on the server containing all drives
When copying different files to the share (existing folders on two particular drives) copy cannot complete because it reports insufficient free space, but copy to the correct folder on a separately mapped drive completes successfully and other drives have no problem..
completed parity check and xfs correcting error check completed to no avail, problem persists.
Thank you to all those that helped, especially trurl
The new disk is fitted and rebuilt successfully.
I'm not sure about whether the old disk is ok or not, at some point I try and preclear it and see what happens.
I have an update.
I reseated all the drives and rebooted the server.
It saw the failed disk, I ran a parity check and it ran ok for about an hour before I went to bed, this morning the disk has been dropped again overnight sometime with 2048 disk errors, parity check hasn't yet finished.
So I will shortly be in a position where the disk is being emulated and I can add the new disk when it arrives next week.
I have attached the diagnostics. I'd be grateful for confirmation the disk is shot.
tower2-diagnostics-20210821-0646.zip