I am using robinhood tmpfs without lustre support.
> # robinhood --version
>
> Product:         robinhood
> Version:         2.5.3.2-1
> Build:           2014-10-29 15:55:57
>
> Compilation switches:
>     Temporary filesystem manager
>     Address entries by path
>     MDT Changelogs disabled
>
> No Lustre support
> Database binding: MySQL

I am trying to create fileclasses for use in filesystem reporting. 
However my fileclass entries appear to be ignored by robinhood.

I am testing against a small local ext4 filesystem. For each test, I 
delete the database via "rbh-config empty_db" command. Then I start a 
scan with command "robinhood --scan --once". When the scan is complete, 
I use command "rbh-report --class-info" to check results.

My tmpfs config file has no purge_polices and no Purge_Trigger sections. 
I have defined this fileclass:
> Filesets
> {
>   FileClass large_files
>   {
>     Definition {
>       type == file
>       and
>       size > 10GB
>     }
>   }
> }

However rbh-report always matches against the "ignored" class eg)
> # rbh-report --class-info
> Using config file '/etc/robinhood.d/tmpfs/fileclass.conf'.
> purge class         ,      count,   spc_used,     volume,   min_size,   
> max_size,   avg_size
> [ignored]           ,       4447,    3.43 GB,    3.42 GB,          0,    1.03 
> GB,  805.86 KB
>
> Total: 4447 entries, 3669665045 bytes (3.42 GB)

Not sure where I'm going wrong, any suggestions would be appreciated.

chris hunter
yale hpc group
[email protected]

------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
vanity: www.gigenet.com
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support

Reply via email to