This Question is Possibly Answered

1 "correct" answer available (10 pts)
200 Views 10 Replies Last post: Nov 3, 2009 1:00 PM by eric.barlier RSS
fajarpri2 Enthusiast 15 posts since
Sep 25, 2009
Currently Being Moderated

Nov 1, 2009 6:39 AM

Help interpreting available space

Hi all,

Can pls help me interprete the available space?

 

n3300> aggr show_space -h
Aggregate 'aggr0'

 

    Total space    WAFL reserve    Snap reserve    Usable space       BSR NVLOG
         4138GB           413GB           186GB          3538GB             0KB

 

Space allocated to volumes in the aggregate

 

Volume                          Allocated            Used       Guarantee
vol0                                873GB           202GB          volume
vol2                                252GB           106GB          volume

 

Aggregate                       Allocated            Used           Avail
Total space                        1126GB           309GB          2615GB
Snap reserve                        186GB            40MB           186GB
WAFL reserve                        413GB            42MB           413GB

 

--------------

n3300> lun show
    /vol/vol0/qtvms1a/lun0        60g (64424509440)   (r/w, online, mapped)
    /vol/vol0/qtvms4a/lun0       180g (193273528320)  (r/w, online, mapped)
    /vol/vol0/qtvms5a/lun0        60g (64424509440)   (r/w, online, mapped)

---------------

n3300> df -h
Filesystem               total       used      avail capacity  Mounted on
/vol/vol0/               671GB      495GB      176GB      74%  /vol/vol0/
/vol/vol0/.snapshot        0KB     4324KB        0KB     ---%  /vol/vol0/.snapshot
/vol/vol2/               250GB      249GB      486MB     100%  /vol/vol2/
/vol/vol2/.snapshot        0MB        0MB        0MB     ---%  /vol/vol2/.snapshot

 

 

---------------

1. Aggr0 has total space of 3.5TB. Correct?

2. How much space is available in vol0? I think it should be around 600GB, but why the df -h command shows only around 176GB?

 

Thank you.

Tags: allocated, available, space, aggr
aborzenkov Enthusiast 29 posts since
Apr 8, 2008
Currently Being Moderated
Nov 1, 2009 11:51 AM in response to: fajarpri2
Re: Help interpreting available space

Well, some ideas

 

  • 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
eric.barlier Master 142 posts since
Jun 20, 2009
Currently Being Moderated
Nov 1, 2009 5:17 PM in response to: fajarpri2
Re: Help interpreting available space

Hi,

 

1. You have put LUNs in the same volume as the system files, vol0. It is NetApp best practice and industry standard to NOT mix vol0 with any LUNs or other way of serving

    data.

2. You could easily reclaim some space by turning snap reserve to 0 (zero) on your aggregate and having no snapshots at aggr. level. Unless you ever think you will overwrite your entire    

    aggregate there is no need for this space to be reserved. I d recommend turning snapshots off and having no snap reserve, but its your call. You might have the option to use it.

 

Regards,

Eric

aborzenkov Enthusiast 29 posts since
Apr 8, 2008
Currently Being Moderated
Nov 1, 2009 10:37 PM in response to: eric.barlier
Re: Help interpreting available space

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?

pascalduk Master 87 posts since
Mar 10, 2008
Currently Being Moderated
Nov 2, 2009 12:15 AM in response to: aborzenkov
Re: Help interpreting available space

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

pascalduk Master 87 posts since
Mar 10, 2008
Currently Being Moderated
Nov 2, 2009 1:16 AM in response to: fajarpri2
Re: Help interpreting available space

Nice, we found the missing 200 GB in the fractional reserve space. And yes, I also don't understand why NetApp did it this way

 

Assuming vol0 is the root volume, don't put LUNs in your root volume because it is not supported.

aborzenkov Enthusiast 29 posts since
Apr 8, 2008
Currently Being Moderated
Nov 2, 2009 12:53 AM in response to: pascalduk
Re: Help interpreting available space

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.

 

Does not explain aggr show_space though

 

Message was edited by: aborzenkov

eric.barlier Master 142 posts since
Jun 20, 2009
Currently Being Moderated
Nov 3, 2009 1:00 PM in response to: aborzenkov
Re: Help interpreting available space

My posting was pretty clear, I was providing a fix rather than trying to guess without info from the controller.

 

I ll explain for you if you want: If you have got no more disk for your volumes in your aggr. you can turn aggr. snap reserve off and get more space for your volumes.

I reckon you know this though.

 

Eric

More Like This

  • Retrieving data ...

Bookmarked By (0)