Okay I'm not a big users of verify, but to be sure about one job I've run a Verify VolumeToCatalog
A shorter lap time after the job start I got a 02-Dec 15:09 orville-dir JobId 384: Fatal error: bsock.c:546 Packet size too big from "Client: orville-fd:orville.disney.interne:9102. Terminating connection. here the log 02-Dec 14:57 orville-dir JobId 384: Start Verify JobId=384 Level=VolumeToCatalog Job=DefaultVerify.2014-12-02_14.57.52_05 02-Dec 14:57 orville-dir JobId 384: Using Device "external_month" to read. 02-Dec 14:57 orville-sd JobId 384: Ready to read from volume "month-0106" on device "external_month" (/media/automount/MONTH/external_month/). 02-Dec 14:57 orville-sd JobId 384: Forward spacing Volume "month-0106" to file:block 50:1491145365. *m You have no messages. *m You have no messages. *m You have no messages. *m 02-Dec 15:09 orville-dir JobId 384: Fatal error: bsock.c:546 Packet size too big from "Client: orville-fd:orville.disney.interne:9102. Terminating connection. 02-Dec 15:10 orville-dir JobId 384: Warning: The following files are in the Catalog but not on the Volume(s): 02-Dec 15:10 orville-dir JobId 384: /usr/src/packages/RPMS/armv3l/ 02-Dec 15:10 orville-dir JobId 384: /usr/src/packages/RPMS/ppc64p7/ 02-Dec 15:10 orville-dir JobId 384: /usr/include/boost/type_traits/ 02-Dec 15:10 orville-dir JobId 384: /usr/share/X11/xkb/rules/base.xml 02-Dec 15:10 orville-dir JobId 384: /usr/src/linux-3.11.10-17-obj/x86_64/xen/include/config/bpf/ 02-Dec 15:10 orville-dir JobId 384: /usr/src/linux-3.11.10-17-obj/x86_64/xen/include/config/ipw2200/ 02-Dec 15:10 orville-dir JobId 384: /usr/src/linux-3.11.10-17-obj/x86_64/xen/include/config/dt3155/ Now due to the fatal error, I'm not able to determine who's wrong If I do a restore manually with jobid what the catalog present look like what I have backup on this client and no there's no /usr/src/linux-3.11.10-17-obj/x86_64/xen/include/config/dt3155/ for example. Continuing the restore from the jobid and a manual selection doesn't show any issues ? Look like I puzzled myself with the verify concept :-) Any thoughts (especially for the bsock.c error) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
