volume size != file system size. So you may have 873GB volume with only 671GB file system inside. Check with vol status -b
if lun reservation is enabled, LUN full size is accounted as used in df output but only physically written blocks are accounted in aggr show_space output. You apparently have 300GB of LUNs and something else on the same volume (almost 200GB), but LUNs are mostly empty
He has volume of size 671G (as confirmed by vol status -b). How comes that aggr show_space shows that 873G are allocated for this volume? What consumes extra 202G? How is it related to either system volume or aggregate snap reserve?
Can you give us the "df -hr" output, which will show us the space used by the fractional reserve.
My guess is that the vol size shown by "df -h" + fractional reserve space = volume allocation in "aggr show_space". Your "df -gA" will also show a used that will be less than total space allocated as shown in "aggr show_space". Why NetApp does it this way, I don't know
Hmm ... question: does NetApp reserve space immediately or only when snapshot is created? I remember having read something on this matter but forgot where.
If space is reserved immediately, df output makes sense. aggr show_space still not
OK, answering to myself. Quoting TR-3483: Data ONTAP removes or reserves this space from the volume as soon as the first Snapshot copy is created. There are some snapshots on vol0 (as indicated by snap reserve being != 0), which explains reservation.
Hi, it's me again. I think it's still related to this question.
Today, when I try to create a LUN on vol3, it errors:
n3300> igroup create -i -t vmware ig_sgvms12 iqn.1998-01.com.vmware:sgvms12 Mon Nov 23 10:01:24 GMT [lun.igroup.tmpFileWriteFailed:error]: Failed to write to the temporary igroup metafile (Initiator group change not stored on disk; unable to write new file). igroup create: Initiator group change not stored on disk; unable to write new file Mon Nov 23 10:50:00 GMT [wafl.vol.full:notice]: file system on volume vol0 is full
I've been reading Netapp forum and found 2 possible solutions:
1. Set Fractional Reserve to zero. But it's very risky because the LUN will go offline if space is out.
But, if I keep total LUN size to be lower than the Volume size, I should be safe, right?
2. Set snapshot off, but I have turned off snapshot on aggr0, haven't I?
Is there any workaround for this situation?
Is it by increasing the size of vol0?
This is related data:
n3300> aggr status Aggr State Status Options aggr1 online raid4, aggr aggr0 online raid4, aggr root, nosnap=on
n3300> cifs shares Name Mount Point Description ---- ----------- ----------- ETC$ /etc Remote Administration ** priv access only ** HOME /vol/vol0/home Default Share everyone / Full Control C$ / Remote Administration ** priv access only **
exportfs returns nothing. I haven't used it for NFS.
I think I have CIFS license, how do I set it up so that I can access it?
I use vol0 for LUN too.. which people say it's a mistake. I know. But, the total LUN size on vol0 is still below the volume size. It should be ok right?