This was what I found on the fs_dedupe -l  (one file system is suspended -- I'm looking into that, one shows no space saved and one shows activity).  All other file systems are currently showing they are not enabled for deduplication.

Id                                 = 72
Name                               = TEST-FS
Deduplication                      = On
Status                             = Idle
As of the last file system scan (Tue May 24 13:15:14 CDT 2011):
   Files scanned                   = 3
   Files deduped                   = 0 (0% of total files)
   File system capacity            = 303495 MB
   Original data size              = 301400 MB (99% of current file system capacity)
   Space saved                     = 0 MB (0% of original data size)

Id                                 = 73
Name                               = TEST_USR-FS
Deduplication                      = Suspended
As of the last file system scan (Wed Feb  2 14:28:38 CST 2011):
   Files scanned                   = 748194
   Files deduped                   = 171393 (20% of total files)
   File system capacity            = 426530 MB
   Original data size              = 393088 MB (92% of current file system capacity)
   Space saved                     = 25980 MB (6% of original data size)

Id                                 = 74
Name                               = TEST_DATA-FS
Deduplication                      = On
Status                             = Idle
As of the last file system scan (Wed May 25 16:57:28 CDT 2011):
   Files scanned                   = 3759
   Files deduped                   = 1924 (13% of total files)
   File system capacity            = 403349 MB
   Original data size              = 2117 MB (0% of current file system capacity)
   Space saved                     = 1408 MB (66% of original data size)

This is the result of the list for pools:

$ nas_pool -list
id      inuse   acl     name
3       y       0       clar_r5_performance
4       y       0       clar_r5_economy
10      y       0       clarata_archive

Sorry for not having a ready answer so I'm not sure how to include the root_vdm's you requested.

easy to check "fs_dedupe -l"   ..when you added space for all file systems, did you add root_vdm's as well ?

Using snapsure or replication ? Those two will consume some space.

what if you run "nas_fs -query:type==uxfs -format:'%s,%s\n' -Fields:name,sizevalues"

first column after fs name is file system capacity in MB, does that add up to your number ?

Hey thanks for a fast reply.  No neither are in use (at some point maybe replication with a VNX system) and no snapsure at this time. Is it possible one or more file systems have deduplication?

OS file systems do not reside in AVM pools, hmm ..i can't think of anything else. Let's see if EMC guys know

No all these sizes are the same I get from the Celerra Manager (which I used to determine the total amount).  Would the OS be located in this disk area possibly?

Did you account for SAVVOLs used by checkpoints or replication ?

Since they aren’t file systems you would see them in the fs list

Rainer

Good morning Rainer.   I dont have any replication going at (yet) and no checkpoints configured.

I only see this with the clar_r5_economy pool.  The clar_r5_performance is accurate.

Would this have anything to do with the economy pool having potential_mb and the performance pool not having a potential_mb space?

Is there a possibility of NDMP backup using checkpoints and that consuming some space? Also there could be savvol usage by dedupe process too. Do 'fs_ckpt fsname -list -all' for all the file systems in that pool, and look for any checkpoints.