Ah, thanks!  Hope all is well, Stephane.

On Fri, May 31, 2024 at 6:22 PM Stephane Thiell <sthi...@stanford.edu>
wrote:

> Hi John,
>
> I think this is because changelogs (that are by FID) require the parent
> FID to be present in the DB. I recommend to drop the DB, scan once, enable
> changelogs, then scan again. Then you should be good to go without frequent
> scanning.
>
> Best,
> --
> Stéphane Thiell
>
> > On May 31, 2024, at 4:11 PM, John White <jwh...@lbl.gov> wrote:
> >
> > I have a new 3.1.7 install on rocky8 running ddn 2.12.9 on the client
> side and 2.12.9_ddn8 on the server side.  Changelog readers enabled on our
> 4 MDTs.I started the daemon to confirm the changelog was functioning before
> starting the initial scan.  rbh-find was full of unresolved fid paths and
> then the filename:
> > 0x5c00292d9:0x12e97:0x0/5_1_1_/rho_5_2_imag.dat
> > 0x5c00292d9:0x12e97:0x0/5_1_1_/rho_5_3_real.dat
> > 0x5c00292d9:0x12e97:0x0/5_1_1_/rho_5_3_imag.dat
> > 0x5c00292d9:0x12e97:0x0/5_1_1_/rho_5_4_real.dat
> > 0x5c00292d9:0x12e97:0x0/5_1_1_/rho_5_4_imag.dat
> > 0x5c00292d9:0x12e97:0x0/5_1_1_/rho_5_5_real.dat
> > 0x5c00292d9:0x12e97:0x0/5_1_1_/rho_5_5_imag.dat
> >
> > But once I started the initial scan, fully resolved paths came into
> being alongside the unresolved paths.
> >
> > Thoughts?
> >
> >
> >
> > _______________________________________________
> > robinhood-support mailing list
> > robinhood-support@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/robinhood-support
>
>
_______________________________________________
robinhood-support mailing list
robinhood-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/robinhood-support

Reply via email to