Hello,
Come to find out, our NAS solution has a bug where there are two
.snapshot directories with the same inode, this appears to be the
underlying cause.
Until we are able to upgrade production, is there any way to tell
robinhood to ignore the error and proceed with the FS scan?
I've tried a few different methods of excluding .snapshot if the config,
but it does not seem to make a difference.
FS_Scan {
Ignore {
name == ".snapshot"
}
Ignore {
#don't scan ".snapshot" directories
type == directory
and
name == ".snapshot"
}
Ignore {
type == symlink
}
Thanks,
Lewis
> Hello,
>
> We're using robinhood to scan a NFS export. There is a top level mount,
> and sub-directories beneath.
>
> The scan works well for the majority of directories, but we have a few
> where the scan errors with "FS_Scan | ERROR reading directory
> </top_level/directory> (Too many levels of symbolic links)". On the
> directories it errors on, it doesn't update the DB for that directory.
>
> I've tried adding the below stanza to the config, but it does not appear
> to have made a difference.
>
> FS_Scan {
> Ignore {
> #don't scan ".snapshot" directories
> type == directory
> and
> name == ".snapshot"
> }
> Ignore {
> type == symlink
> }
>
> Any suggestions would be appreciated.
>
> Thanks,
> Lewis
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support
