Robert Marley
Dabbler
- Joined
- Sep 11, 2014
- Messages
- 29
config details
iSCSI target is FreeNas 3 phys 1TB drives, raidz into 1.95TB, mapped to a windows 8.1 client.
the client can see the disk, but clearly it's having issues with writes and access overall.
the crashplan archive I store on it won't progress in it's compact cycle and doesn't see it as being there most of the time.
From Win8.1 NTFS perspective the drive is 945GB full. 50% of total capacity, you'd think.
from the FreeNas side, log into scary alerts
CRITICAL: The capacity for the volume 'Raidz' is currently at 98%, while the recommended value is below 80%.
storage manager confirms Zvol is exactly 1.95TB and there are 0kb available. So FreeNas thinks it's really full, but status is 'healthy'
How do I clean up this mess without losing my data?
and what did I configure wrong?
iSCSI target is FreeNas 3 phys 1TB drives, raidz into 1.95TB, mapped to a windows 8.1 client.
the client can see the disk, but clearly it's having issues with writes and access overall.
the crashplan archive I store on it won't progress in it's compact cycle and doesn't see it as being there most of the time.
From Win8.1 NTFS perspective the drive is 945GB full. 50% of total capacity, you'd think.
from the FreeNas side, log into scary alerts
CRITICAL: The capacity for the volume 'Raidz' is currently at 98%, while the recommended value is below 80%.
storage manager confirms Zvol is exactly 1.95TB and there are 0kb available. So FreeNas thinks it's really full, but status is 'healthy'
How do I clean up this mess without losing my data?
and what did I configure wrong?