search for: storage4

...23:17:43.052040, 0] ../source3/nmbd/nmbd_packets.c:1174(process_lanman_packet) Jan 5 23:17:43 storage8 nmbd[21114]: process_lanman_packet: Discarding datagram from IP 192.168.100.36. Source name TRUENAS1<00> is one of our names ! " FreeNAS box on network B " Jan 5 23:17:32 storage4 nmbd[34068]: [2016/01/05 23:17:32.086480, 0] ../source3/nmbd/nmbd_packets.c:1174(process_lanman_packet) Jan 5 23:17:32 storage4 nmbd[34068]: process_lanman_packet: Discarding datagram from IP 172.21.140.17. Source name STORAGE4<00> is one of our names ! " Thanks, Torkil

On 01/06/2016 01:23 AM, Jeremy Allison wrote: >> Jan 5 23:17:32 storage4 nmbd[34068]: [2016/01/05 23:17:32.086480, >> 0] ../source3/nmbd/nmbd_packets.c:1174(process_lanman_packet) >> Jan 5 23:17:32 storage4 nmbd[34068]: process_lanman_packet: >> Discarding datagram from IP 172.21.140.17. Source name STORAGE4<00> >> is one of our names !...

Hi, I'm fairly new to samba so apologies if this is an old problem.... When I try 'net ads join -U administrator' I get the following: [2007/05/22 12:15:15, 0] libads/ldap.c:ads_add_machine_acct(1368) ads_add_machine_acct: Host account for storage4 already exists - modifying old account Using short domain name -- ABSOLUTESTUDIOS [2007/05/22 12:15:15, 0] libads/kerberos.c:get_service_ticket(335) get_service_ticket: kerberos_kinit_password STORAGE4$@ABSOLUTESTUDIOS.CO.UK@ABSOLUTESTUDIOS.CO.UK failed: Preauthentication failed Segmentation f...

.../nmbd_packets.c:1174(process_lanman_packet) > Jan 5 23:17:43 storage8 nmbd[21114]: process_lanman_packet: > Discarding datagram from IP 192.168.100.36. Source name TRUENAS1<00> > is one of our names ! > " > > FreeNAS box on network B > " > Jan 5 23:17:32 storage4 nmbd[34068]: [2016/01/05 23:17:32.086480, > 0] ../source3/nmbd/nmbd_packets.c:1174(process_lanman_packet) > Jan 5 23:17:32 storage4 nmbd[34068]: process_lanman_packet: > Discarding datagram from IP 172.21.140.17. Source name STORAGE4<00> > is one of our names ! > " Are...

...in xfs_repair) on linux 4.3.0 Anyway linux kernel is providing information about dirs and files for this filesystem. Unfortunately some data is causing rsync to fail at assertion. IMO rsync should be able to deal with anything linux kernel is providing to userspace. Thus this bugreport. cd /mnt/storage4/snapshots/blade3/ rsync -e ssh -avvvvvvvPH * root at host:/dest/snapshots/blade3/ [sender] pushing local filters for /mnt/storage4/snapshots/blade3/daily.1/usr/bin/ [sender] flist start=58089, used=2, low=0, high=0 [sender] i=58089 <NULL> daily.1/usr/bin/ mode=040755 len=12,288 uid=0 gid=0 f...

...9;/> | </source> | <target dev='vde' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage4'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdf' bus='virti...