Freenas 81 percent

[Supersayian]

Hello all

I have been using freenas for a while now. I have it setup with two zfs pools. One is 4 seagate 3tb hard drives. I just went over 80 percent by accident. The system is setup as iscsi connected to a windows server 2016 file server. The problem is I can't access it on windows to delete some files to get it back under 80. It is only over by 1 percent and it now is locked up where I can't see any of the the data sets on either of the two pools. The hard ware is listed below. Not sure if it is needed but I will list it. Was wondering if there is a way to get it working to delete some files or will upgrading to larger disks allow it to work again?

Motherboard MSI A88X-G45 GAMING
Amd A6-7400k 3.5ghz cpu
Memory G.SKILL Ares Series 16GB
4x 5tb Seagate hard drives
4x 3TB Seagate hard drives Don't know the models of the drives

 

[toadman]

Going over 80% should not cause FreeNAS to "lock up." It's a warning threshold that suggests you need to figure out what to do before the pool capacity hits 90% and performance really tanks. (FYI - for iscsi, most recommend running no greater than 50% in a pool if you want decent performance. But that's a separate discussion.)

What exactly does "locked up" mean? Are you able to log into the FreeNAS server?

Re: the question of pool growth, yes, if you have autoexpand set to yes on the pool and you replace the disks one by one and resliver the pool will expand it's capacity once all disks are replaced.

 

[Supersayian]

The iscsi connection is not working and the windows server won't connect to it. I tried restarting it and that did not work.

 

[toadman]

Assuming you can log into the FreeNAS server and get to a shell, what does zpool status and zfs list -t filesystem show?

What version of FreeNAS are you running?

 

[Supersayian]

it is 11.1-u6

 

[Supersayian]

NAME STATE READ WRITE CKSUM
San2_Vol2 ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
gptid/0146f9eb-b159-11e8-8b78-00074306bbb5 ONLINE 0 0 0
gptid/0251a84b-b159-11e8-8b78-00074306bbb5 ONLINE 0 0 0
gptid/03796fb4-b159-11e8-8b78-00074306bbb5 ONLINE 0 0 0
gptid/04a9fb0b-b159-11e8-8b78-00074306bbb5 ONLINE 0 0 0

NAME USED AVAIL REFER MOUNTPOINT
San2_Vol1 12.7T 18.5G 128K /mnt/San2_Vol1
San2_Vol1/.system 4.76M 18.5G 140K legacy
San2_Vol1/.system/configs-b3147af497d748f98f845f65b942be53 3.55M 18.5G 3.55M legacy
San2_Vol1/.system/cores 634K 18.5G 634K legacy
San2_Vol1/.system/rrd-b3147af497d748f98f845f65b942be53 128K 18.5G 128K legacy
San2_Vol1/.system/samba4 209K 18.5G 209K legacy
San2_Vol1/.system/syslog-b3147af497d748f98f845f65b942be53 128K 18.5G 128K legacy
San2_Vol1/jails 128K 18.5G 128K /mnt/San2_Vol1/jails
San2_Vol2 7.62T 38.0G 128K /mnt/San2_Vol2
freenas-boot 2.50G 24.9G 64K none
freenas-boot/ROOT 2.48G 24.9G 29K none
freenas-boot/ROOT/11.1-U5 6.25M 24.9G 844M /
freenas-boot/ROOT/11.1-U6 2.47G 24.9G 843M /
freenas-boot/ROOT/Initial-Install 2.05M 24.9G 836M /
freenas-boot/ROOT/default 5.32M 24.9G 841M legacy
freenas-boot/grub 7.02M 24.9G 7.02M legacy

 

[Supersayian]

Yeah with my experience with windows I should have tried this first. I should have restarted the windows file server but I have two of there freenas iscsi machines and the second one was working. Which is why I didn't restart it in the first place. It is working now and thanks for all the help. I feel like such a noob.