AnsweredAssumed Answered

Hnas  Preserved Space and File System Capacity Reporting

Question asked by Allen Santos Employee on Jan 12, 2016
Latest reply on Jun 22, 2016 by Ottfried Gottschalk

I have a question –

 

Customer recent ran the following command – ‘snapshot-list’ and is receiving the following output.

 

 

usporamhnasCL-2:$ snapshot-list --all --freeable-space --file-system Desi_Prod_fs_01

snapshot-list: executing on cluster node 2, though the EVS in context (1) is currently on cluster node 1

 

                        Date/Time     Created     Freeable Space     Preserved Space Name     Status

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

2016-01-12 01:45:00-08:00     By Rule 2 MB 2 MB 2016-01-12_0145-0800.Desi_Prod_fs01_snapshot     Usable

2016-01-11 01:45:00-08:00     By Rule            4.76 MB             15.1 GB     2016-01-11_0145-0800.Desi_Prod_fs01_snapshot Usable

2016-01-10 01:45:00-08:00     By Rule            4.75 MB             4.78 MB     2016-01-10_0145-0800.Desi_Prod_fs01_snapshot Usable

2016-01-09 01:45:00-08:00     By Rule            6.10 MB             6.59 MB     2016-01-09_0145-0800.Desi_Prod_fs01_snapshot Usable

2016-01-06 01:45:00-08:00     By Rule            15.5 GB             3.69 TB     2016-01-06_0145-0800.Desi_Prod_fs01_snapshot Usable

2016-01-05 01:45:00-08:00     By Rule            20.9 MB 115 MB     2016-01-05_0145-0800.Desi_Prod_fs01_snapshot Usable

 

File system is using block-based snapshots.

 

[snapshot-list took 12 s.]

 

 

The 2016-01-06 snapshot to the customer seems unusual given the ‘Preserved Space’ value was 3.69 TB, which is appox the amount of data on the file system - Desi_Prod_fs_01.

 

<df for vnode 1>

 

ID    Label           Size    Used               Snapshots    Deduped     Avail  Thin ThinSize ThinAvail                FS Type 

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

1025  Desi_Prod_fs_01 3.99 TB  3.77 TB (94%)  3.66 TB (92%)       NA  234 GB (6%) No                          4 KB,WFS-2,128 DSBs




Historically, the customer has only performed over the past year manual snapshot creation/deletion. No dedupes, replication, created.



6914 Information   2016-01-08 10:06:15 File System: A shared file system lock is being released after being held for an excessive time by "Bluestone bossock" (@0x00007F483A2A5E10, id 2507, state @): 50.8 min: this event (and similar ones) happened 3 times in the last 8 s on the MMB1

1524 Information   2016-01-08 10:27:05 PAPI housekeeping successful

                                       Cause:       PAPI housekeeping successful

1524 Information   2016-01-08 15:21:44 PAPI housekeeping successful

7160 Information   2016-01-09 01:45:00 Snapshot created ("2016-01-09_0145-0800.Desi_Prod_fs01_snapshot" on Desi_Prod_fs_01)

1524 Information   2016-01-09 10:26:27 PAPI housekeeping successful

1524 Information   2016-01-09 15:21:46 PAPI housekeeping successful

7160 Information   2016-01-10 01:45:00 Snapshot created ("2016-01-10_0145-0800.Desi_Prod_fs01_snapshot" on Desi_Prod_fs_01)

1524 Information   2016-01-10 10:25:49 PAPI housekeeping successful

1524 Information   2016-01-10 15:21:48 PAPI housekeeping successful

7160 Information   2016-01-11 01:45:00 Snapshot created ("2016-01-11_0145-0800.Desi_Prod_fs01_snapshot" on Desi_Prod_fs_01)

7161 Information   2016-01-11 01:45:00 Snapshot marked for deletion ("2016-01-04_0145-0800.Desi_Prod_fs01_snapshot" on Desi_Prod_fs_01)

7162 Information   2016-01-11 01:45:01 Snapshot deleted ("2016-01-04_0145-0800.Desi_Prod_fs01_snapshot" on Desi_Prod_fs_01)

6912 Severe        2016-01-11 04:59:18 File System: A shared file system lock has been hogged for an excessive time by "Bluestone bossock" (@0x00007F483A2A5E10, id 2507, state SW [LOCK:Desi_Prod_fs_01(shared:703360ms!)failed]): 11.7 min: this event happened once in the last 2.81 d on the MMB1


 

Is this the value one would expect to be displayed or is this another anomaly caused by the file system Desi_Prod_fs_01 being 94% capacity?

Outcomes