Hi Steve,

Here’s how I look at the numbers reported by df –s:

- The first number is space used.  This is the physical space used by the active file system and snapshots to store the unique blocks in the volume.

- The second number is space saved.  This is the space that would be used by shared blocks; the blocks that have been identified as duplicate copies and freed up.

- The percentage is based on space saved divided by total disk space usage if deduplication was not used.  This non-deduplicated total space usage is the sum of the unique blocks (“used”) and the shared blocks (“saved”).  Another way to look at this total is to consider it the total amount of logical data that is being stored in the deduplicated volume.

So, 74719212/(74719212+79484444) = 48%

Does that help?

---Karl

Karl L. Konnerth

Systems Engineer

NetApp

From: steve klise [mailto:klises@caminomedical.org]
Sent: Tuesday, April 13, 2010 4:23 PM
To: toasters@mathworks.com
Subject: df -s value

Maybe I am missing something here: FAS6040 DOT 7.3.1.1 FC 500GB LUN 0 fractional reserve thin provisioned running dedupe (love it) I think there is a bug maybe in my version of DOT. I ran df-s on a volume, and this is what I am seeing. /vol/netapp_vol_vmware_DMZ_01/ 79484444 74719212 48% Should it be around 94% ? Here is the image from DFM (3.8)

---

View this message in context: df -s value
Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.