ONTAP Discussions
ONTAP Discussions
If I can receive any assistance in troubleshooting the issue I have. thanks
scsitarget.lun.noSpace:error]: LUN '/vol/Files_backups/Files_backups' has run out of space.
Filesystem kbytes used avail capacity Mounted on
/vol/Files_backups/ 1041213876 915798232 0 100% /vol/Files_backups/
/vol/Files_backups/.snapshot 0 20406916 0 ---% /vol/Files_backups/.snapshot
Hi,
It may be the case that fractional reserve kicked in.
What is the output of:
df -r /vol/Files_backups
?
Same problem here after aggregate was full. I reduced the snap reserve on that and delete all snapshot. (aggrX 13TB 13TB 650GB 95%)
NetApp Release 7.3.2P3: Fri Dec 11 18:10:24 PST 2009
Volume has 1550GB, LUN is thin with 1.5TB and use only 957GB...
Any idea ?
So my first guess will be as above - fractional reserve?
What's the output of
df -r /vol/your_vol_name
?
filer> vol options /vol/vol1
nosnap=on, nosnapdir=off, minra=off, no_atime_update=off, nvfail=off,
ignore_inconsistent=off, snapmirrored=off, create_ucode=off,
convert_ucode=off, maxdirsize=62914, schedsnapname=ordinal,
fs_size_fixed=off, compression=off, guarantee=volume, svo_enable=off,
svo_checksum=off, svo_allow_rman=off, svo_reject_errors=off,
no_i2p=off, fractional_reserve=0, extent=off, try_first=volume_grow,
read_realloc=off, snapshot_clone_dependency=off
---
===== vFilerX
/vol/vol1/lun1 1.5t (1610838835200) (r/w, online, mapped)
Serial#: ...X...
Share: none
Space Reservation: disabled
Multiprotocol Type: windows_gpt
Maps: ssm-backup2=0
---
filer> df -r /vol/vol1
Filesystem kbytes used avail reserved Mounted on
/vol/vol1/ 1625292800 1004440600 620852200 0 /vol/vol1/
---
sis is activated.
---
I think the following message is not true, but I don't know how I can remove it...
"Thu Feb 6 07:13:03 CET [scsitarget.lun.noSpace:error]: LUN '/vol/vol1' has run out of space."
Where is this message coming from?
There is space within volume & there should be space within LUN as well if we use simple arithmetic.
The message is from the logs (messages) and is displayed continuous on the console.
Th Volume (thick) has 1550GB, LUN is created with 1.5TB and use only 957GB on the volume.
mhh.. it is true you have nosnap on, but nevertheless, what says "snap list" ? was says sis status /vol/vol1 ? and of course the question how much space is available within the aggregate yet ?? what about the SIS Metadata? so , what is the output of aggr show_space -g of the content aggregate ?
Hi,
you have to increase your volume immediately or just delete the contained snaps.. You have taken snapshots which consumed 20406916 , this value you have to add with the consumed LUN space of 915798232 !
That's why the LUN itself has no sufficient space anymore.
change/adjust your snapshot scheduler for the future.
You have taken snapshots which consumed 20406916 , this value you have to add with the consumed LUN space of 915798232 !
Not quite. Snap reserve is set to 0% for this volume, so any space taken by snapshots is included in the first line of the output.
Thats correct for the user above, but what do you think about my similar problem ?
your problem is the not sufficient space within the aggregate ! that's why your volume is 100% full ... and with that the LUN too !
I wrote:
Same problem here after aggregate was full. I reduced the snap reserve on that and delete all snapshot. (aggrX 13TB 13TB 650GB 95%)
NetApp Release 7.3.2P3: Fri Dec 11 18:10:24 PST 2009
Volume has 1550GB, LUN is thin with 1.5TB and use only 957GB...
I have enough and more space in the aggr. And, I use a thick volume...
filer> df -r /vol/vol1
Filesystem kbytes used avail reserved Mounted on
/vol/vol1/ 1625292800 1004440600 620852200 0 /vol/vol1/
You wrote:
mhh.. it is true you have nosnap on, but nevertheless, what says "snap list" ? was says sis status /vol/vol1 ? and of course the question how much space is available within the aggregate yet ?? what about the SIS Metadata? so , what is the output of aggr show_space -g of the content aggregate ?
-> Snaps all deleted and we have enough (more as 600GB) on the aggr
-> What do you mean with "what about the SIS Metadata?" ? Dedup ist enabled on the volume. Do you think the dedup db on this volume is corrupt ?