stefan.holzwarth@zentrale.adac.de wrote:

...

After looking around i found some users using their quota for doing backups to our filer. That backups were deleted after 2 weeks and replaced by new backups. This led to a large amount of data invisible to the quota system, but wasting a lot of snapstorage.

How can i deal with that situation and especialy: how to find users/qtrees with a lot of changed data?

Hello Stefan

1) As the others already stated: For (not just ... :-) ) CIFS there is this new filefolding option. If you take a closer look at the "options" manpage explaining this new ONTAP 6.2 feature you can detect, that it will work on any file getting closed without making any difference wether it is a CIFS or NFS file close => It works for NFS, too. It was just named, CIFS option because there it is needed by this "document.xxx gets renamed to document.bak and then write document.xxx again" behaviour of MS-Applications... You usually don't need it if you have NFS Clients .... and ... if you are not having users that explicitely rewrite their data over and over again .. like your users do. :-(

Maybe NetApp can/will? change this option to a wafl-option? cifs -> wafl.snapshot_file_folding.enable

2) The command "filestats" should help you to find those "bad" users? It can also produce tables and HTML output. :-) If you modify example 3 for your wanted limitations (limitation on mod-ages) you should find the "bad" users.

Best regards from Munich/Germany. Dirk Schmiedt ... can be found as NetApp-Trainer on www.qskills.de

NAME

filestats - collect file usage statistics

SYNOPSIS

filestats [ ages ages] [ timetype {a,m,c,cr}] [ sizes sizes] snapshot snapshot_name [ style style] [ volume volume_name]

DESCRIPTION

The filestats utility provides a summary of file usage within a volume. It must be used on a snapshot, and the only required argument is the snapshot name. The volume name defaults to "vol0" if not specified. If the volume you are examining is named otherwise, specify the name explicitly.

....

EXAMPLES

1. Produce default file usage breakdowns for snapshot hourly.1 of volume vol0.

filestats volume vol0 snapshot hourly.1

2. Produce file usage breakdowns by monthly age values:

filestats volume vol0 snapshot hourly.1 ages "30D,60D,90D,120D,150D,180D"

3. Produce file usage breakdowns for inodes whose size is less than 100000 bytes and whose access time is less than a day old:

filestats volume vol0 snapshot hourly.1 expr "{size}<100000&&{atimeage}<86400)"

3. Produce a breakdown of the total number of files and their total size. You can control the set of ages and sizes that get used for this breakdown, with the "ages" and "sizes" arguments. The output also contains a breakdown of file usage by user-id and group-id.

filestats snapshot hourly.1 volume vol0

A very very simple output example without any search limitations, from an used filer, currently having only one user: root=0

filer7*> filestats snapshot 1 VOL=vol0 SNAPSHOT=1 INODES=543328 COUNTED_INODES=906 TOTAL_BYTES=317956057 TOTAL_KB=42184

FILE SIZE CUMULATIVE COUNT CUMULATIVE TOTAL KB 1K 465 1580 10K 853 3464 100K 882 4500 1M 896 8696 10M 901 24164 100M 906 42184 1G 906 42184 MAX 906 42184

AGE(ATIME) CUMULATIVE COUNT CUMULATIVE TOTAL KB 0 0 0 30D 906 42184 60D 906 42184 90D 906 42184 120D 906 42184 MAX 906 42184

UID COUNT TOTAL KB #0 906 42184

GID COUNT TOTAL KB #0 906 42184