Unable to create snapshot of vdev: out of space

[plopplops]

Hello everyone,

I have a pool, called "fast", 1.24TB used, and 528,89GB available space. This pool contains a dataset for ISCSI volumes, the dataset is called iscsi. This dataset contains one VDEV, in use by the ISCSI service, that is called gaming. When I hit the "three dots"-icon to the right of gaming and hit "Create snapshot" nothing happens. When I go to "Storage" and then "Snapshots" and try to create a snapshot of "fast/iscsi/gaming" it results in the error I attached further down. I do not understand how the pool can be out of space with a snapshot that should not use much space as long as I have not created deviating changes (a delta) that are created when I modify or write new files after the snapshot has been taken. Maybe I am not understanding how things go together in this context.

Thank you.

Error: concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/zfs.py", line 1019, in do_create
ds.properties['freenas:vmsynced'] = libzfs.ZFSUserProperty('Y')
File "libzfs.pyx", line 392, in libzfs.ZFS.__exit__
File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/zfs.py", line 1016, in do_create
ds.snapshot(f'{dataset}@{name}', recursive=recursive, fsopts=properties)
File "libzfs.pyx", line 3774, in libzfs.ZFSDataset.snapshot
libzfs.ZFSException: out of space

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.9/concurrent/futures/process.py", line 246, in _process_worker
r = call_item.fn(*call_item.args, **call_item.kwargs)
File "/usr/local/lib/python3.9/site-packages/middlewared/worker.py", line 111, in main_worker
res = MIDDLEWARE._run(*call_args)
File "/usr/local/lib/python3.9/site-packages/middlewared/worker.py", line 45, in _run
return self._call(name, serviceobj, methodobj, args, job=job)
File "/usr/local/lib/python3.9/site-packages/middlewared/worker.py", line 39, in _call
return methodobj(*params)
File "/usr/local/lib/python3.9/site-packages/middlewared/worker.py", line 39, in _call
return methodobj(*params)
File "/usr/local/lib/python3.9/site-packages/middlewared/schema.py", line 979, in nf
return f(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/zfs.py", line 1024, in do_create
raise CallError(f'Failed to snapshot {dataset}@{name}: {err}')
middlewared.service_exception.CallError: [EFAULT] Failed to snapshot fast/iscsi/gaming@manual-2022-12-05_16-30: out of space
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 139, in call_method
result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self)
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1235, in _call
return await methodobj(*prepared_call.args)
File "/usr/local/lib/python3.9/site-packages/middlewared/service.py", line 495, in create
rv = await self.middleware._call(
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1243, in _call
return await self._call_worker(name, *prepared_call.args)
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1249, in _call_worker
return await self.run_in_proc(main_worker, name, args, job)
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1168, in run_in_proc
return await self.run_in_executor(self.__procpool, method, *args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1151, in run_in_executor
return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
middlewared.service_exception.CallError: [EFAULT] Failed to snapshot fast/iscsi/gaming@manual-2022-12-05_16-30: out of space

 

[jgreco]

Welcome to the forums.

Sorry to hear you're having trouble. Please take a few moments to review the Forum Rules, conveniently linked at the top of every page in red, and pay particular attention to the section on how to formulate a useful problem report, especially including a detailed description of your hardware, what version of TrueNAS you are using, what your pool layout is, and the configuration of the iSCSI device.

You've basically given no one anything to work with, so the responses will tend to be random guesses rather than anything useful.

 

[plopplops]

I was not the machine I was talking about so was unable to see the details. I am wondering however, am I not able to edit these posts?

Guest:
- TrueNAS-13.0-U3.1
- System is a virtual machine (KVM/QEMU, Q35, 48GB ECC RAM)
- Pool is stored on a single Samsung SSD 970 EVO Plus 2TB

Host:
- Threadripper PRO 3975WX, 256GB ECC, ASUS Pro WS WRX80E-SAGE SE WIFI

 

[plopplops]

Oh, this might be interesting as well. Same machine, different pool has a dataset iscsi once again in use by the ISCSI service, doing snapshots of the VDEVs there do work.