Sep 8 14:11:27 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: fatal: invalid metadata block Sep 8 14:11:27 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: bh = 312738524 (magic number) Sep 8 14:11:27 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: function = gfs2_meta_indirect_buffer, file = fs/gfs2/meta_io.c, line = 334 Sep 8 14:11:27 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: about to withdraw this file system Sep 8 14:11:27 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: telling LM to withdraw Sep 8 14:11:28 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 14:11:28 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 14:11:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 14:11:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Busy Sep 8 14:11:28 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 14:11:28 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 14:11:28 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: withdrawn Sep 8 14:11:28 192.168.100.105 kernel: Sep 8 14:11:28 192.168.100.105 kernel: Call Trace: Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:gfs2_lm_withdraw+0xc1/0xd0 Sep 8 14:11:28 192.168.100.105 kernel: [] __wait_on_bit+0x60/0x6e Sep 8 14:11:28 192.168.100.105 kernel: [] sync_buffer+0x0/0x3f Sep 8 14:11:28 192.168.100.105 kernel: [] out_of_line_wait_on_bit+0x6c/0x78 Sep 8 14:11:28 192.168.100.105 kernel: [] wake_bit_function+0x0/0x23 Sep 8 14:11:28 192.168.100.105 kernel: [] submit_bh+0x10a/0x111 Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:gfs2_meta_check_ii+0x2c/0x38 Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:gfs2_meta_indirect_buffer+0x104/0x160 Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:gfs2_block_map+0x1dc/0x33e Sep 8 14:11:28 192.168.100.105 kernel: [] poll_freewait+0x29/0x6a Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:gfs2_extent_map+0x74/0xac Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:gfs2_write_alloc_required+0xfd/0x122 Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:gfs2_glock_nq+0x248/0x273 Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:gfs2_write_begin+0x99/0x36a Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:gfs2_file_buffered_write+0x14b/0x2e5 Sep 8 14:11:28 192.168.100.105 kernel: [] file_read_actor+0x0/0xfc Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:__gfs2_file_aio_write_nolock+0x29c/0x2d4 Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:gfs2_file_write_nolock+0xaa/0x10f Sep 8 14:11:28 192.168.100.105 kernel: [] __wake_up+0x38/0x4f Sep 8 14:11:28 192.168.100.105 kernel: [] autoremove_wake_function+0x0/0x2e Sep 8 14:11:28 192.168.100.105 kernel: [] pipe_readv+0x38e/0x3a2 Sep 8 14:11:28 192.168.100.105 kernel: [] lock_kernel+0x1b/0x32 Sep 8 14:11:28 192.168.100.105 kernel: [] :gfs2:gfs2_file_write+0x49/0xa7 Sep 8 14:11:28 192.168.100.105 kernel: [] vfs_write+0xce/0x174 Sep 8 14:11:28 192.168.100.105 kernel: [] sys_write+0x45/0x6e Sep 8 14:11:28 192.168.100.105 kernel: [] tracesys+0xab/0xb6 Sep 8 14:11:28 192.168.100.105 kernel: Sep 8 14:11:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 14:11:28 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 14:11:28 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 14:11:28 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 14:11:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Looking at journal... Sep 8 14:11:28 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 14:11:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Acquiring the transaction lock... Sep 8 14:11:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Replaying journal... Sep 8 14:11:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Replayed 11 of 11 blocks Sep 8 14:11:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Found 0 revoke tags Sep 8 14:11:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Journal replayed in 1s Sep 8 14:11:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Done Sep 8 14:11:29 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 14:11:29 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 14:11:29 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 14:11:29 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 14:11:29 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 14:11:29 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 14:11:29 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 14:11:29 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 14:11:30 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 14:11:30 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 14:11:30 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 14:11:30 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 14:11:30 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 14:11:30 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 14:11:30 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 14:11:30 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 14:11:31 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 14:11:31 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 14:11:31 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 14:11:31 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 14:11:31 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 14:11:31 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 14:11:31 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 14:11:31 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Looking at journal... Sep 8 14:11:32 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Done Sep 8 14:11:32 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 14:11:32 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Looking at journal... Sep 8 14:11:32 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Done Sep 8 14:11:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: fatal: filesystem consistency error Sep 8 14:11:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: function = trans_go_xmote_bh, file = fs/gfs2/glops.c, line = 401 Sep 8 14:11:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: about to withdraw this file system Sep 8 14:11:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: telling LM to withdraw Sep 8 14:24:20 192.168.100.102 kernel: device vif32.0 entered promiscuous mode Sep 8 14:24:20 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): vif32.0: link is not ready Sep 8 14:25:02 192.168.100.102 kernel: xenbr1: port 35(vif32.0) entering disabled state Sep 8 14:25:02 192.168.100.102 kernel: device vif32.0 left promiscuous mode Sep 8 14:25:02 192.168.100.102 kernel: xenbr1: port 35(vif32.0) entering disabled state Sep 8 14:25:47 192.168.100.104 kernel: xenbr1: port 10(vif12.0) entering disabled state Sep 8 14:25:47 192.168.100.104 kernel: device vif12.0 left promiscuous mode Sep 8 14:25:47 192.168.100.104 kernel: xenbr1: port 10(vif12.0) entering disabled state Sep 8 14:27:20 192.168.100.102 logger: /etc/xen/scripts/block: xenstore-read backend/vbd/32/832/node failed. Sep 8 14:27:20 192.168.100.102 logger: /etc/xen/scripts/block: /etc/xen/scripts/block failed; error detected. Sep 8 14:27:20 192.168.100.102 logger: /etc/xen/scripts/block: xenstore-read backend/vbd/32/768/node failed. Sep 8 14:27:20 192.168.100.102 logger: /etc/xen/scripts/block: /etc/xen/scripts/block failed; error detected. Sep 8 14:27:20 192.168.100.102 logger: /etc/xen/scripts/block: xenstore-read backend/vbd/32/5632/node failed. Sep 8 14:27:20 192.168.100.102 logger: /etc/xen/scripts/block: /etc/xen/scripts/block failed; error detected. Sep 8 14:40:50 pxe xinetd[16078]: START: tftp pid=26569 from=192.168.100.103 Sep 8 14:41:22 192.168.100.104 kernel: usb 2-2: USB disconnect, address 2 Sep 8 14:45:20 192.168.100.101 ccsd[3844]: Update of cluster.conf complete (version 4 -> 5). Sep 8 14:45:20 192.168.100.105 ccsd[4024]: Update of cluster.conf complete (version 4 -> 5). Sep 8 14:45:20 192.168.100.104 ccsd[19379]: Update of cluster.conf complete (version 4 -> 5). Sep 8 14:45:20 192.168.100.102 ccsd[12684]: Update of cluster.conf complete (version 4 -> 5). Sep 8 14:45:44 192.168.100.101 ccsd[3844]: Update of cluster.conf complete (version 5 -> 6). Sep 8 14:45:44 192.168.100.105 ccsd[4024]: Update of cluster.conf complete (version 5 -> 6). Sep 8 14:45:44 192.168.100.104 ccsd[19379]: Update of cluster.conf complete (version 5 -> 6). Sep 8 14:45:44 192.168.100.102 ccsd[12684]: Update of cluster.conf complete (version 5 -> 6). Sep 8 14:49:05 pxe mountd[2162]: authenticated mount request from 192.168.100.103:876 for /opt/xen_5.3/root (/opt/xen_5.3/root) Sep 8 14:49:06 pxe mountd[2162]: authenticated mount request from 192.168.100.103:878 for /opt/xen_5.3/snapshot (/opt/xen_5.3/snapshot) Sep 8 14:49:28 192.168.100.103 syslogd 1.4.1: restart. Sep 8 14:49:28 192.168.100.103 kernel: klogd 1.4.1, log source = /proc/kmsg started. Sep 8 14:49:28 192.168.100.103 kernel: Bootdata ok (command line is root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen3 ) Sep 8 14:49:28 192.168.100.103 kernel: Linux version 2.6.18-128.1.6.el5xen (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Apr 1 09:53:14 EDT 2009 Sep 8 14:49:28 192.168.100.103 kernel: BIOS-provided physical RAM map: Sep 8 14:49:28 192.168.100.103 kernel: Xen: 0000000000000000 - 00000000a0800000 (usable) Sep 8 14:49:28 192.168.100.103 kernel: DMI present. Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x04] enabled) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] enabled) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x06] enabled) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) Sep 8 14:49:28 192.168.100.103 kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 Sep 8 14:49:28 192.168.100.103 kernel: ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24]) Sep 8 14:49:28 192.168.100.103 kernel: IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47 Sep 8 14:49:28 192.168.100.103 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Sep 8 14:49:28 192.168.100.103 kernel: Setting APIC routing to xen Sep 8 14:49:28 192.168.100.103 kernel: Using ACPI (MADT) for SMP configuration information Sep 8 14:49:28 192.168.100.103 kernel: Allocating PCI resources starting at d1000000 (gap: d0000000:10000000) Sep 8 14:49:28 192.168.100.103 kernel: Built 1 zonelists. Total pages: 657408 Sep 8 14:49:28 192.168.100.103 kernel: Kernel command line: root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen3 Sep 8 14:49:28 192.168.100.103 kernel: Initializing CPU#0 Sep 8 14:49:28 192.168.100.103 kernel: PID hash table entries: 4096 (order: 12, 32768 bytes) Sep 8 14:49:28 192.168.100.103 kernel: Xen reported: 2000.068 MHz processor. Sep 8 14:49:28 192.168.100.103 kernel: Console: colour VGA+ 80x25 Sep 8 14:49:28 192.168.100.103 kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Sep 8 14:49:28 192.168.100.103 kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Sep 8 14:49:28 192.168.100.103 kernel: Software IO TLB enabled: Sep 8 14:49:28 192.168.100.103 kernel: Aperture: 64 megabytes Sep 8 14:49:28 192.168.100.103 kernel: Kernel range: 0xffff8800057c5000 - 0xffff8800097c5000 Sep 8 14:49:28 192.168.100.103 kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Sep 8 14:49:28 192.168.100.103 kernel: Memory: 2467584k/2629632k available (2447k kernel code, 153292k reserved, 1366k data, 180k init) Sep 8 14:49:28 192.168.100.103 kernel: Calibrating delay using timer specific routine.. 5003.05 BogoMIPS (lpj=10006108) Sep 8 14:49:28 192.168.100.103 kernel: Security Framework v1.0.0 initialized Sep 8 14:49:28 192.168.100.103 kernel: SELinux: Initializing. Sep 8 14:49:28 192.168.100.103 kernel: selinux_register_security: Registering secondary module capability Sep 8 14:49:28 192.168.100.103 kernel: Capability LSM initialized as secondary Sep 8 14:49:28 192.168.100.103 kernel: Mount-cache hash table entries: 256 Sep 8 14:49:28 192.168.100.103 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Sep 8 14:49:28 192.168.100.103 kernel: CPU: L2 cache: 6144K Sep 8 14:49:28 192.168.100.103 kernel: CPU: Physical Processor ID: 0 Sep 8 14:49:28 192.168.100.103 kernel: CPU: Processor Core ID: 0 Sep 8 14:49:28 192.168.100.103 kernel: (SMP-)alternatives turned off Sep 8 14:49:28 192.168.100.103 kernel: ACPI: Core revision 20060707 Sep 8 14:49:28 192.168.100.103 kernel: Initializing CPU#1 Sep 8 14:49:28 192.168.100.103 kernel: Initializing CPU#2 Sep 8 14:49:28 192.168.100.103 kernel: Initializing CPU#3 Sep 8 14:49:28 192.168.100.103 kernel: Initializing CPU#4 Sep 8 14:49:28 192.168.100.103 kernel: Initializing CPU#5 Sep 8 14:49:28 192.168.100.103 kernel: Initializing CPU#6 Sep 8 14:49:28 192.168.100.103 kernel: Brought up 8 CPUs Sep 8 14:49:28 192.168.100.103 kernel: Initializing CPU#7 Sep 8 14:49:28 192.168.100.103 kernel: migration_cost=874 Sep 8 14:49:28 192.168.100.103 kernel: checking if image is initramfs... it is Sep 8 14:49:28 192.168.100.103 kernel: Grant table initialized Sep 8 14:49:28 192.168.100.103 kernel: NET: Registered protocol family 16 Sep 8 14:49:28 192.168.100.103 kernel: No dock devices found. Sep 8 14:49:28 192.168.100.103 kernel: ACPI: bus type pci registered Sep 8 14:49:28 192.168.100.103 kernel: PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved Sep 8 14:49:28 192.168.100.103 kernel: PCI: Not using MMCONFIG. Sep 8 14:49:28 192.168.100.103 kernel: PCI: Using configuration type 1 Sep 8 14:49:28 192.168.100.103 kernel: ACPI: Interpreter enabled Sep 8 14:49:28 192.168.100.103 kernel: ACPI: Using IOAPIC for interrupt routing Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Root Bridge [PCI0] (0000:00) Sep 8 14:49:28 192.168.100.103 kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 Sep 8 14:49:28 192.168.100.103 kernel: PCI: Transparent bridge - 0000:00:1e.0 Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 *7 10 11 14 15) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 14 15) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 14 15) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 14 15) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 14:49:28 192.168.100.103 kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Sep 8 14:49:28 192.168.100.103 kernel: pnp: PnP ACPI init Sep 8 14:49:28 192.168.100.103 kernel: pnp: PnP ACPI: found 12 devices Sep 8 14:49:28 192.168.100.103 kernel: xen_mem: Initialising balloon driver. Sep 8 14:49:28 192.168.100.103 kernel: usbcore: registered new driver usbfs Sep 8 14:49:28 192.168.100.103 kernel: usbcore: registered new driver hub Sep 8 14:49:28 192.168.100.103 kernel: PCI: Using ACPI for IRQ routing Sep 8 14:49:28 192.168.100.103 kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Sep 8 14:49:28 192.168.100.103 kernel: NetLabel: Initializing Sep 8 14:49:28 192.168.100.103 kernel: NetLabel: domain hash size = 128 Sep 8 14:49:28 192.168.100.103 kernel: NetLabel: protocols = UNLABELED CIPSOv4 Sep 8 14:49:28 192.168.100.103 kernel: NetLabel: unlabeled traffic allowed by default Sep 8 14:49:28 192.168.100.103 kernel: PCI: Bridge: 0000:02:00.0 Sep 8 14:49:28 192.168.100.103 kernel: IO window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: MEM window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: PREFETCH window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: PCI: Bridge: 0000:02:01.0 Sep 8 14:49:28 192.168.100.103 kernel: IO window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: MEM window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: PREFETCH window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: PCI: Bridge: 0000:02:02.0 Sep 8 14:49:28 192.168.100.103 kernel: IO window: 2000-2fff Sep 8 14:49:28 192.168.100.103 kernel: MEM window: d8000000-d80fffff Sep 8 14:49:28 192.168.100.103 kernel: PREFETCH window: d8400000-d84fffff Sep 8 14:49:28 192.168.100.103 kernel: PCI: Bridge: 0000:01:00.0 Sep 8 14:49:28 192.168.100.103 kernel: IO window: 2000-2fff Sep 8 14:49:28 192.168.100.103 kernel: MEM window: d8000000-d80fffff Sep 8 14:49:28 192.168.100.103 kernel: PREFETCH window: d8400000-d84fffff Sep 8 14:49:28 192.168.100.103 kernel: PCI: Bridge: 0000:01:00.3 Sep 8 14:49:28 192.168.100.103 kernel: IO window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: MEM window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: PREFETCH window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: PCI: Bridge: 0000:00:02.0 Sep 8 14:49:28 192.168.100.103 kernel: IO window: 2000-2fff Sep 8 14:49:28 192.168.100.103 kernel: MEM window: d8000000-d81fffff Sep 8 14:49:28 192.168.100.103 kernel: PREFETCH window: d8400000-d84fffff Sep 8 14:49:28 192.168.100.103 kernel: PCI: Bridge: 0000:00:04.0 Sep 8 14:49:28 192.168.100.103 kernel: IO window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: MEM window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: PREFETCH window: disabled. Sep 8 14:49:28 192.168.100.103 kernel: PCI: Bridge: 0000:00:06.0 Sep 8 14:49:28 192.168.100.103 kernel: IO window: 3000-3fff Sep 8 14:49:28 192.168.100.103 kernel: MEM window: d8200000-d82fffff Sep 8 14:49:28 192.168.100.103 kernel: PREFETCH window: d8500000-d85fffff Sep 8 14:49:28 192.168.100.103 kernel: PCI: Bridge: 0000:00:1e.0 Sep 8 14:49:28 192.168.100.103 kernel: IO window: 4000-4fff Sep 8 14:49:28 192.168.100.103 kernel: MEM window: d8300000-d83fffff Sep 8 14:49:28 192.168.100.103 kernel: PREFETCH window: d0000000-d7ffffff Sep 8 14:49:28 192.168.100.103 kernel: GSI 16 sharing vector 0xA0 and IRQ 16 Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 14:49:28 192.168.100.103 kernel: GSI 17 sharing vector 0xA8 and IRQ 17 Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 14:49:28 192.168.100.103 kernel: GSI 18 sharing vector 0xB0 and IRQ 18 Sep 8 14:49:28 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 14:49:28 192.168.100.103 kernel: NET: Registered protocol family 2 Sep 8 14:49:28 192.168.100.103 kernel: IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) Sep 8 14:49:28 192.168.100.103 kernel: TCP established hash table entries: 262144 (order: 10, 4194304 bytes) Sep 8 14:49:28 192.168.100.103 kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) Sep 8 14:49:28 192.168.100.103 kernel: TCP: Hash tables configured (established 262144 bind 65536) Sep 8 14:49:28 192.168.100.103 kernel: TCP reno registered Sep 8 14:49:28 192.168.100.103 kernel: Simple Boot Flag at 0x38 set to 0x1 Sep 8 14:49:28 192.168.100.103 kernel: audit: initializing netlink socket (disabled) Sep 8 14:49:28 192.168.100.103 kernel: type=2000 audit(1252421336.816:1): initialized Sep 8 14:49:28 192.168.100.103 kernel: VFS: Disk quotas dquot_6.5.1 Sep 8 14:49:28 192.168.100.103 kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Sep 8 14:49:28 192.168.100.103 kernel: Initializing Cryptographic API Sep 8 14:49:28 192.168.100.103 kernel: alg: No test for crc32c (crc32c-generic) Sep 8 14:49:28 192.168.100.103 kernel: ksign: Installing public key data Sep 8 14:49:28 192.168.100.103 kernel: Loading keyring Sep 8 14:49:28 192.168.100.103 kernel: - Added public key 5535842996BF3A42 Sep 8 14:49:28 192.168.100.103 kernel: - User ID: CentOS (Kernel Module GPG key) Sep 8 14:49:28 192.168.100.103 kernel: io scheduler noop registered Sep 8 14:49:28 192.168.100.103 kernel: io scheduler anticipatory registered Sep 8 14:49:28 192.168.100.103 kernel: io scheduler deadline registered Sep 8 14:49:28 192.168.100.103 kernel: io scheduler cfq registered (default) Sep 8 14:49:28 192.168.100.103 kernel: assign_interrupt_mode Found MSI capability Sep 8 14:49:28 192.168.100.103 kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5 Sep 8 14:49:28 192.168.100.103 kernel: ACPI: Processor [CPU0] (supports 8 throttling states) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: Processor [CPU1] (supports 8 throttling states) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: Processor [CPU2] (supports 8 throttling states) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: Processor [CPU3] (supports 8 throttling states) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: Processor [CPU4] (supports 8 throttling states) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: Processor [CPU5] (supports 8 throttling states) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: Processor [CPU6] (supports 8 throttling states) Sep 8 14:49:28 192.168.100.103 kernel: ACPI: Processor [CPU7] (supports 8 throttling states) Sep 8 14:49:28 192.168.100.103 kernel: Real Time Clock Driver v1.12ac Sep 8 14:49:29 192.168.100.103 kernel: Non-volatile memory driver v1.2 Sep 8 14:49:29 192.168.100.103 kernel: Linux agpgart interface v0.101 (c) Dave Jones Sep 8 14:49:29 192.168.100.103 kernel: RAMDISK driver initialized: 16 RAM disks of 26403K size 4096 blocksize Sep 8 14:49:29 192.168.100.103 kernel: Xen virtual console successfully installed as ttyS0 Sep 8 14:49:29 192.168.100.103 kernel: Event-channel device installed. Sep 8 14:49:29 192.168.100.103 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Sep 8 14:49:29 192.168.100.103 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Sep 8 14:49:29 192.168.100.103 kernel: ESB2: IDE controller at PCI slot 0000:00:1f.1 Sep 8 14:49:29 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 14:49:29 192.168.100.103 kernel: ESB2: chipset revision 9 Sep 8 14:49:29 192.168.100.103 kernel: ESB2: not 100% native mode: will probe irqs later Sep 8 14:49:29 192.168.100.103 kernel: ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:pio, hdb:DMA Sep 8 14:49:29 192.168.100.103 kernel: hdb: DVD-ROM UJDA780, ATAPI CD/DVD-ROM drive Sep 8 14:49:29 192.168.100.103 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Sep 8 14:49:29 192.168.100.103 kernel: ide-floppy driver 0.99.newide Sep 8 14:49:29 192.168.100.103 kernel: usbcore: registered new driver hiddev Sep 8 14:49:29 192.168.100.103 kernel: usbcore: registered new driver usbhid Sep 8 14:49:29 192.168.100.103 kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver Sep 8 14:49:29 192.168.100.103 kernel: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12 Sep 8 14:49:29 192.168.100.103 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Sep 8 14:49:29 192.168.100.103 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Sep 8 14:49:29 192.168.100.103 kernel: mice: PS/2 mouse device common for all mice Sep 8 14:49:29 192.168.100.103 kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 Sep 8 14:49:29 192.168.100.103 kernel: md: bitmap version 4.39 Sep 8 14:49:29 192.168.100.103 kernel: TCP bic registered Sep 8 14:49:29 192.168.100.103 kernel: Initializing IPsec netlink socket Sep 8 14:49:29 192.168.100.103 kernel: NET: Registered protocol family 1 Sep 8 14:49:29 192.168.100.103 kernel: NET: Registered protocol family 17 Sep 8 14:49:29 192.168.100.103 kernel: Write protecting the kernel read-only data: 467k Sep 8 14:49:29 192.168.100.103 kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 Sep 8 14:49:29 192.168.100.103 kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation. Sep 8 14:49:29 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 14:49:29 192.168.100.103 kernel: 0000:05:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 14:49:29 192.168.100.103 kernel: eth0: (PCI Express:2.5GB/s:Width x4) 00:30:48:c5:4a:d0 Sep 8 14:49:29 192.168.100.103 kernel: eth0: Intel(R) PRO/1000 Network Connection Sep 8 14:49:29 192.168.100.103 kernel: eth0: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 14:49:29 192.168.100.103 kernel: GSI 19 sharing vector 0xB8 and IRQ 19 Sep 8 14:49:29 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:05:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 14:49:29 192.168.100.103 kernel: 0000:05:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 14:49:29 192.168.100.103 kernel: eth1: (PCI Express:2.5GB/s:Width x4) 00:30:48:c5:4a:d1 Sep 8 14:49:29 192.168.100.103 kernel: eth1: Intel(R) PRO/1000 Network Connection Sep 8 14:49:29 192.168.100.103 kernel: eth1: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 14:49:29 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:08:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 14:49:29 192.168.100.103 kernel: 0000:08:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 14:49:29 192.168.100.103 kernel: eth2: (PCI Express:2.5GB/s:Width x4) 00:15:17:c3:c1:68 Sep 8 14:49:29 192.168.100.103 kernel: eth2: Intel(R) PRO/1000 Network Connection Sep 8 14:49:29 192.168.100.103 kernel: eth2: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 14:49:29 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:08:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 14:49:29 192.168.100.103 kernel: 0000:08:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 14:49:29 192.168.100.103 kernel: eth3: (PCI Express:2.5GB/s:Width x4) 00:15:17:c3:c1:69 Sep 8 14:49:29 192.168.100.103 kernel: eth3: Intel(R) PRO/1000 Network Connection Sep 8 14:49:29 192.168.100.103 kernel: eth3: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 14:49:29 192.168.100.103 kernel: FS-Cache: Loaded Sep 8 14:49:29 192.168.100.103 kernel: eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 8 14:49:29 192.168.100.103 kernel: NET: Registered protocol family 10 Sep 8 14:49:29 192.168.100.103 kernel: lo: Disabled Privacy Extensions Sep 8 14:49:29 192.168.100.103 kernel: IPv6 over IPv4 tunneling driver Sep 8 14:49:29 192.168.100.103 kernel: SELinux: Disabled at runtime. Sep 8 14:49:29 192.168.100.103 kernel: type=1404 audit(1252421348.008:2): selinux=0 auid=4294967295 ses=4294967295 Sep 8 14:49:29 192.168.100.103 kernel: hdb: ATAPI 24X DVD-ROM drive, 2048kB Cache, UDMA(33) Sep 8 14:49:29 192.168.100.103 kernel: Uniform CD-ROM driver Revision: 3.20 Sep 8 14:49:29 192.168.100.103 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Sep 8 14:49:29 192.168.100.103 kernel: 8250_pnp: Unknown symbol serial8250_unregister_port Sep 8 14:49:29 192.168.100.103 kernel: 8250_pnp: Unknown symbol serial8250_register_port Sep 8 14:49:29 192.168.100.103 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Sep 8 14:49:29 192.168.100.103 kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Sep 8 14:49:29 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 14:49:29 192.168.100.103 kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller Sep 8 14:49:29 192.168.100.103 kernel: ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 Sep 8 14:49:29 192.168.100.103 kernel: ehci_hcd 0000:00:1d.7: debug port 1 Sep 8 14:49:29 192.168.100.103 kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller Sep 8 14:49:29 192.168.100.103 rpc.statd[3209]: Version 1.0.9 Starting Sep 8 14:49:30 192.168.100.103 kernel: Bridge firewalling registered Sep 8 14:49:30 192.168.100.103 kernel: xenbr1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. Sep 8 14:49:31 192.168.100.103 kernel: device vif0.0 entered promiscuous mode Sep 8 14:49:31 192.168.100.103 kernel: xenbr1: topology change detected, propagating Sep 8 14:49:31 192.168.100.103 kernel: xenbr1: port 1(vif0.0) entering forwarding state Sep 8 14:49:31 192.168.100.103 kernel: ADDRCONF(NETDEV_UP): peth1: link is not ready Sep 8 14:49:32 192.168.100.103 kernel: peth1: Link is Up 100 Mbps Full Duplex, Flow Control: None Sep 8 14:49:32 192.168.100.103 kernel: peth1: 10/100 speed: disabling TSO Sep 8 14:49:32 192.168.100.103 kernel: ADDRCONF(NETDEV_CHANGE): peth1: link becomes ready Sep 8 14:49:33 192.168.100.103 kernel: device peth1 entered promiscuous mode Sep 8 14:49:33 192.168.100.103 kernel: xenbr1: topology change detected, propagating Sep 8 14:49:33 192.168.100.103 kernel: xenbr1: port 2(peth1) entering forwarding state Sep 8 14:49:33 192.168.100.103 kernel: DLM (built Apr 1 2009 09:54:52) installed Sep 8 14:49:33 192.168.100.103 kernel: GFS2 (built Apr 1 2009 09:56:12) installed Sep 8 14:49:33 192.168.100.103 kernel: Lock_DLM (built Apr 1 2009 09:56:21) installed Sep 8 14:49:33 192.168.100.103 ccsd[3845]: Starting ccsd 2.0.98: Sep 8 14:49:33 192.168.100.103 ccsd[3845]: Built: Jan 21 2009 05:40:28 Sep 8 14:49:33 192.168.100.103 ccsd[3845]: Copyright (C) Red Hat, Inc. 2004 All rights reserved. Sep 8 14:49:33 192.168.100.103 ccsd[3845]: cluster.conf (cluster name = xencluster1, version = 4) found. Sep 8 14:49:33 192.168.100.103 ccsd[3845]: Remote copy of cluster.conf is from quorate node. Sep 8 14:49:33 192.168.100.103 ccsd[3845]: Local version # : 4 Sep 8 14:49:33 192.168.100.103 ccsd[3845]: Remote version #: 6 Sep 8 14:49:33 192.168.100.103 ccsd[3845]: Switching to remote copy. Sep 8 14:49:34 192.168.100.103 ccsd[3845]: Remote copy of cluster.conf is from quorate node. Sep 8 14:49:34 192.168.100.103 ccsd[3845]: Local version # : 6 Sep 8 14:49:34 192.168.100.103 ccsd[3845]: Remote version #: 6 Sep 8 14:49:34 192.168.100.103 ccsd[3845]: Remote copy of cluster.conf is from quorate node. Sep 8 14:49:34 192.168.100.103 ccsd[3845]: Local version # : 6 Sep 8 14:49:34 192.168.100.103 ccsd[3845]: Remote version #: 6 Sep 8 14:49:34 192.168.100.103 ccsd[3845]: Remote copy of cluster.conf is from quorate node. Sep 8 14:49:34 192.168.100.103 ccsd[3845]: Local version # : 6 Sep 8 14:49:34 192.168.100.103 ccsd[3845]: Remote version #: 6 Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] AIS Executive Service RELEASE 'subrev 1358 version 0.80.3' Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Copyright (C) 2002-2006 MontaVista Software, Inc and contributors. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Copyright (C) 2006 Red Hat, Inc. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] AIS Executive Service: started and ready to provide service. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] openais component openais_cpg loaded. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Registering service handler 'openais cluster closed process group service v1.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] openais component openais_cfg loaded. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Registering service handler 'openais configuration service' Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] openais component openais_msg loaded. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Registering service handler 'openais message service B.01.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] openais component openais_lck loaded. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Registering service handler 'openais distributed locking service B.01.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] openais component openais_evt loaded. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Registering service handler 'openais event service B.01.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] openais component openais_ckpt loaded. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Registering service handler 'openais checkpoint service B.01.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] openais component openais_amf loaded. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Registering service handler 'openais availability management framework B.01.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] openais component openais_clm loaded. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Registering service handler 'openais cluster membership service B.01.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] openais component openais_evs loaded. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Registering service handler 'openais extended virtual synchrony service' Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] openais component openais_cman loaded. Sep 8 14:49:34 192.168.100.103 openais[3851]: [MAIN ] Registering service handler 'openais CMAN membership service 2.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] Token Timeout (10000 ms) retransmit timeout (495 ms) Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] token hold (386 ms) retransmits before loss (20 retrans) Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] join (60 ms) send_join (0 ms) consensus (4800 ms) merge (200 ms) Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] downcheck (1000 ms) fail to recv const (50 msgs) Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] seqno unchanged const (30 rotations) Maximum network MTU 1500 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] window size per rotation (50 messages) maximum messages per rotation (17 messages) Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] send threads (0 threads) Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] RRP token expired timeout (495 ms) Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] RRP token problem counter (2000 ms) Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] RRP threshold (10 problem count) Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] RRP mode set to none. Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] heartbeat_failures_allowed (0) Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] max_network_delay (50 ms) Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] HeartBeat is Disabled. To enable set heartbeat_failures_allowed > 0 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] Receive multicast socket recv buffer size (262142 bytes). Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] Transmit multicast socket send buffer size (262142 bytes). Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] The network interface [10.103.103.103] is now up. Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] Created or loaded sequence id 0.10.103.103.103 for this ring. Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] entering GATHER state from 15. Sep 8 14:49:34 192.168.100.103 openais[3851]: [SERV ] Initialising service handler 'openais extended virtual synchrony service' Sep 8 14:49:34 192.168.100.103 openais[3851]: [SERV ] Initialising service handler 'openais cluster membership service B.01.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [SERV ] Initialising service handler 'openais availability management framework B.01.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [SERV ] Initialising service handler 'openais checkpoint service B.01.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [SERV ] Initialising service handler 'openais event service B.01.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [SERV ] Initialising service handler 'openais distributed locking service B.01.01' Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] entering GATHER state from 11. Sep 8 14:49:34 192.168.100.103 openais[3851]: [SERV ] Initialising service handler 'openais message service B.01.01' Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] entering GATHER state from 11. Sep 8 14:49:34 192.168.100.103 openais[3851]: [SERV ] Initialising service handler 'openais configuration service' Sep 8 14:49:34 192.168.100.103 openais[3851]: [SERV ] Initialising service handler 'openais cluster closed process group service v1.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [SERV ] Initialising service handler 'openais CMAN membership service 2.01' Sep 8 14:49:34 192.168.100.103 openais[3851]: [CMAN ] CMAN 2.0.98 (built Jan 21 2009 05:40:32) started Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] entering GATHER state from 11. Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] entering GATHER state from 11. Sep 8 14:49:34 192.168.100.103 openais[3851]: [SYNC ] Not using a virtual synchrony filter. Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] entering GATHER state from 10. Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] entering GATHER state from 11. Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] Creating commit token because I am the rep. Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] Saving state aru d7 high seq received d7 Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] Storing new sequence id for ring 6c Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] entering COMMIT state. Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] Saving state aru d7 high seq received d7 Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] Storing new sequence id for ring 6c Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] entering COMMIT state. Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] Saving state aru 0 high seq received 0 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] Storing new sequence id for ring 6c Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] entering COMMIT state. Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] Saving state aru d7 high seq received d7 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] Storing new sequence id for ring 6c Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] entering COMMIT state. Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] Saving state aru d7 high seq received d7 Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] Storing new sequence id for ring 6c Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] entering COMMIT state. Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] entering RECOVERY state. Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 0 rep 10.103.103.103 Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] aru 0 high delivered 0 received flag 1 Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] entering RECOVERY state. Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] position [4] member 10.103.103.105: Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] entering RECOVERY state. Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 0 rep 10.103.103.103 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] aru 0 high delivered 0 received flag 1 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 0 rep 10.103.103.103 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] aru 0 high delivered 0 received flag 1 Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] entering RECOVERY state. Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] position [4] member 10.103.103.105: Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] position [4] member 10.103.103.105: Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 0 rep 10.103.103.103 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] aru 0 high delivered 0 received flag 1 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] entering RECOVERY state. Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] position [4] member 10.103.103.105: Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] previous ring seq 0 rep 10.103.103.103 Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] aru 0 high delivered 0 received flag 1 Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] Sending initial ORF token Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] position [4] member 10.103.103.105: Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] previous ring seq 104 rep 10.103.103.101 Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] aru d7 high delivered d7 received flag 1 Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] New Configuration: Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] New Configuration: Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] Members Left: Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] Members Left: Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] Members Joined: Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] Members Joined: Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] New Configuration: Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] New Configuration: Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] New Configuration: Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] Members Left: Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] Members Joined: Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] Members Left: Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] Members Joined: Sep 8 14:49:34 192.168.100.103 openais[3851]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] Members Left: Sep 8 14:49:34 192.168.100.103 openais[3851]: [TOTEM] entering OPERATIONAL state. Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] Members Joined: Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:49:34 192.168.100.102 openais[12690]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] New Configuration: Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:49:34 192.168.100.102 openais[12690]: [TOTEM] entering OPERATIONAL state. Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] New Configuration: Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] Members Left: Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] Members Joined: Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:49:34 192.168.100.104 openais[19385]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:49:34 192.168.100.104 openais[19385]: [TOTEM] entering OPERATIONAL state. Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] Members Left: Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] Members Joined: Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] New Configuration: Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] Members Left: Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] Members Joined: Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:49:34 192.168.100.105 openais[4033]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:49:34 192.168.100.105 openais[4033]: [TOTEM] entering OPERATIONAL state. Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:49:34 192.168.100.101 openais[3853]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:49:34 192.168.100.101 openais[3853]: [TOTEM] entering OPERATIONAL state. Sep 8 14:49:34 192.168.100.103 openais[3851]: [CMAN ] quorum regained, resuming activity Sep 8 14:49:34 192.168.100.103 openais[3851]: [CMAN ] quorum lost, blocking activity Sep 8 14:49:34 192.168.100.103 openais[3851]: [CMAN ] quorum regained, resuming activity Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:49:34 192.168.100.105 openais[4033]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:49:34 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 14:49:34 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 14:49:34 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 14:49:34 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 14:49:34 192.168.100.105 openais[4033]: [CPG ] got joinlist message from node 5 Sep 8 14:49:34 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 5 Sep 8 14:49:34 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 5 Sep 8 14:49:34 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 5 Sep 8 14:49:34 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 5 Sep 8 14:49:34 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 1 Sep 8 14:49:34 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 1 Sep 8 14:49:34 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 1 Sep 8 14:49:34 192.168.100.105 openais[4033]: [CPG ] got joinlist message from node 1 Sep 8 14:49:34 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 1 Sep 8 14:49:34 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 2 Sep 8 14:49:34 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 2 Sep 8 14:49:34 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 2 Sep 8 14:49:34 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 2 Sep 8 14:49:34 192.168.100.105 openais[4033]: [CPG ] got joinlist message from node 2 Sep 8 14:49:34 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 4 Sep 8 14:49:34 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 4 Sep 8 14:49:34 192.168.100.105 openais[4033]: [CPG ] got joinlist message from node 4 Sep 8 14:49:34 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 4 Sep 8 14:49:34 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 4 Sep 8 14:49:34 192.168.100.103 ccsd[3845]: Initial status:: Quorate Sep 8 14:49:38 pxe mountd[2162]: authenticated mount request from 192.168.100.103:723 for /opt/xenxml (/opt/xenxml) Sep 8 14:49:39 192.168.100.103 gpm[4062]: *** info [startup.c(95)]: Sep 8 14:49:39 192.168.100.103 gpm[4062]: Started gpm successfully. Entered daemon mode. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70). Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Successfully dropped root privileges. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: avahi-daemon 0.6.16 starting up. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Successfully called chroot(). Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Successfully dropped remaining capabilities. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Loading service file /services/sftp-ssh.service. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: New relevant interface eth3.IPv6 for mDNS. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Joining mDNS multicast group on interface eth3.IPv6 with address fe80::215:17ff:fec3:c169. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: New relevant interface eth3.IPv4 for mDNS. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Joining mDNS multicast group on interface eth3.IPv4 with address 10.103.103.103. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: New relevant interface eth2.IPv6 for mDNS. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Joining mDNS multicast group on interface eth2.IPv6 with address fe80::215:17ff:fec3:c168. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: New relevant interface eth2.IPv4 for mDNS. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.102.102.103. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: New relevant interface eth0.IPv6 for mDNS. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::230:48ff:fec5:4ad0. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: New relevant interface eth0.IPv4 for mDNS. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.100.103. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Network interface enumeration completed. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Registering new address record for fe80::215:17ff:fec3:c169 on eth3. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Registering new address record for 10.103.103.103 on eth3. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Registering new address record for fe80::215:17ff:fec3:c168 on eth2. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Registering new address record for 10.102.102.103 on eth2. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Registering new address record for fe80::230:48ff:fec5:4ad0 on eth0. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Registering new address record for 192.168.100.103 on eth0. Sep 8 14:49:42 192.168.100.103 avahi-daemon[4266]: Registering HINFO record with values 'X86_64'/'LINUX'. Sep 8 14:49:43 192.168.100.103 avahi-daemon[4266]: Server startup complete. Host name is xen3.local. Local service cookie is 3960991670. Sep 8 14:49:43 192.168.100.103 avahi-daemon[4266]: Service "SFTP File Transfer on xen3" (/services/sftp-ssh.service) successfully established. Sep 8 14:49:44 192.168.100.103 xenstored: Checking store ... Sep 8 14:49:44 192.168.100.103 xenstored: Checking store complete. Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 14 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 271 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 272 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 273 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 18 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 277 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 278 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 279 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 19 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 274 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 275 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 276 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 268 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 269 Sep 8 14:49:45 192.168.100.103 kernel: Breaking affinity for irq 270 Sep 8 14:49:46 192.168.100.103 smartd[4590]: smartd version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Sep 8 14:49:46 192.168.100.103 smartd[4590]: Home page is http://smartmontools.sourceforge.net/ Sep 8 14:49:46 192.168.100.103 smartd[4590]: Opened configuration file /etc/smartd.conf Sep 8 14:49:46 192.168.100.103 smartd[4590]: Configuration file /etc/smartd.conf parsed. Sep 8 14:49:46 192.168.100.103 smartd[4590]: Device: /dev/sda, No such device, open() failed Sep 8 14:49:46 192.168.100.103 smartd[4590]: Unable to register ATA device /dev/sda at line 32 of file /etc/smartd.conf Sep 8 14:49:46 192.168.100.103 smartd[4590]: Device /dev/sda not available Sep 8 14:49:46 192.168.100.103 smartd[4590]: Monitoring 0 ATA and 0 SCSI devices Sep 8 14:49:46 192.168.100.103 smartd[4592]: smartd has fork()ed into background mode. New PID=4592. Sep 8 14:52:09 192.168.100.103 iscsid: iscsid shutting down. Sep 8 14:52:09 192.168.100.103 kernel: Loading iSCSI transport class v2.0-724. Sep 8 14:52:09 192.168.100.103 kernel: iscsi: registered transport (tcp) Sep 8 14:52:09 192.168.100.103 kernel: iscsi: registered transport (iser) Sep 8 14:52:09 192.168.100.103 iscsid: iSCSI logger with pid=5409 started! Sep 8 14:52:10 192.168.100.103 iscsid: transport class version 2.0-724. iscsid version 2.0-868 Sep 8 14:52:10 192.168.100.103 iscsid: iSCSI daemon with pid=5410 started! Sep 8 14:53:27 192.168.100.103 iscsid: iscsid shutting down. Sep 8 14:53:27 192.168.100.103 kernel: Loading iSCSI transport class v2.0-724. Sep 8 14:53:27 192.168.100.103 kernel: iscsi: registered transport (tcp) Sep 8 14:53:27 192.168.100.103 kernel: iscsi: registered transport (iser) Sep 8 14:53:27 192.168.100.103 iscsid: iSCSI logger with pid=5657 started! Sep 8 14:53:27 192.168.100.103 kernel: scsi0 : iSCSI Initiator over TCP/IP Sep 8 14:53:27 192.168.100.103 kernel: scsi1 : iSCSI Initiator over TCP/IP Sep 8 14:53:28 192.168.100.103 iscsid: transport class version 2.0-724. iscsid version 2.0-868 Sep 8 14:53:28 192.168.100.103 iscsid: iSCSI daemon with pid=5658 started! Sep 8 14:53:28 192.168.100.103 kernel: Vendor: Promise Model: VTrak M610i Rev: 021C Sep 8 14:53:28 192.168.100.103 kernel: Type: Direct-Access ANSI SCSI revision: 05 Sep 8 14:53:28 192.168.100.103 kernel: Vendor: Promise Model: VTrak M610i Rev: 021C Sep 8 14:53:28 192.168.100.103 kernel: Type: Direct-Access ANSI SCSI revision: 05 Sep 8 14:53:29 192.168.100.103 kernel: scsi 0:0:0:0: Attached scsi generic sg0 type 0 Sep 8 14:53:29 192.168.100.103 kernel: scsi 1:0:0:0: Attached scsi generic sg1 type 0 Sep 8 14:53:29 192.168.100.103 kernel: sda : very big device. try to use READ CAPACITY(16). Sep 8 14:53:29 192.168.100.103 kernel: SCSI device sda: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 14:53:29 192.168.100.103 kernel: sda: Write Protect is off Sep 8 14:53:29 192.168.100.103 kernel: SCSI device sda: drive cache: write back w/ FUA Sep 8 14:53:29 192.168.100.103 kernel: sda : very big device. try to use READ CAPACITY(16). Sep 8 14:53:29 192.168.100.103 kernel: SCSI device sda: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 14:53:29 192.168.100.103 kernel: sda: Write Protect is off Sep 8 14:53:29 192.168.100.103 kernel: SCSI device sda: drive cache: write back w/ FUA Sep 8 14:53:29 192.168.100.103 kernel: sda: sda1 Sep 8 14:53:29 192.168.100.103 kernel: sd 0:0:0:0: Attached scsi disk sda Sep 8 14:53:29 192.168.100.103 multipathd: sda: add path (uevent) Sep 8 14:53:29 192.168.100.103 kernel: sdb : very big device. try to use READ CAPACITY(16). Sep 8 14:53:29 192.168.100.103 kernel: SCSI device sdb: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 14:53:29 192.168.100.103 kernel: sdb: Write Protect is off Sep 8 14:53:29 192.168.100.103 kernel: SCSI device sdb: drive cache: write back w/ FUA Sep 8 14:53:29 192.168.100.103 kernel: sdb : very big device. try to use READ CAPACITY(16). Sep 8 14:53:29 192.168.100.103 kernel: SCSI device sdb: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 14:53:29 192.168.100.103 kernel: sdb: Write Protect is off Sep 8 14:53:29 192.168.100.103 kernel: SCSI device sdb: drive cache: write back w/ FUA Sep 8 14:53:29 192.168.100.103 kernel: sdb: sdb1 Sep 8 14:53:29 192.168.100.103 kernel: sd 1:0:0:0: Attached scsi disk sdb Sep 8 14:53:29 192.168.100.103 iscsid: received iferror -38 Sep 8 14:53:29 192.168.100.103 iscsid: connection1:0 is operational now Sep 8 14:53:29 192.168.100.103 iscsid: received iferror -38 Sep 8 14:53:29 192.168.100.103 iscsid: connection2:0 is operational now Sep 8 14:53:29 192.168.100.103 kernel: device-mapper: multipath round-robin: version 1.0.0 loaded Sep 8 14:53:29 192.168.100.103 multipathd: xen: failed in domap for addition of new path sda Sep 8 14:53:29 192.168.100.103 multipathd: uevent trigger error Sep 8 14:53:29 192.168.100.103 multipathd: sdb: add path (uevent) Sep 8 14:53:29 192.168.100.103 multipathd: xen: failed in domap for addition of new path sdb Sep 8 14:53:29 192.168.100.103 multipathd: uevent trigger error Sep 8 14:53:29 192.168.100.103 multipathd: dm-0: add map (uevent) Sep 8 14:53:29 192.168.100.103 multipathd: xen: event checker started Sep 8 14:53:51 192.168.100.103 kernel: GFS2: fsid=: Trying to join cluster "lock_dlm", "xencluster1:xenclusterfs1" Sep 8 14:53:51 192.168.100.103 kernel: dlm: Using TCP for communications Sep 8 14:53:51 192.168.100.103 kernel: dlm: connecting to 1 Sep 8 14:53:51 192.168.100.104 kernel: dlm: connecting to 3 Sep 8 14:53:51 192.168.100.101 kernel: dlm: connecting to 3 Sep 8 14:53:51 192.168.100.102 kernel: dlm: connecting to 3 Sep 8 14:53:51 192.168.100.103 kernel: dlm: got connection from 4 Sep 8 14:53:51 192.168.100.103 kernel: dlm: got connection from 1 Sep 8 14:53:51 192.168.100.103 kernel: dlm: got connection from 2 Sep 8 14:53:51 192.168.100.101 kernel: dlm: got connection from 3 Sep 8 14:53:51 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: Joined cluster. Now mounting FS... Sep 8 14:53:52 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: jid=1, already locked for use Sep 8 14:53:52 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: jid=1: Looking at journal... Sep 8 14:53:52 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: jid=1: Done Sep 8 14:55:41 192.168.100.105 shutdown[27577]: shutting down for system halt Sep 8 14:55:55 192.168.100.101 openais[3853]: [TOTEM] The token was lost in the OPERATIONAL state. Sep 8 14:55:55 192.168.100.101 openais[3853]: [TOTEM] Receive multicast socket recv buffer size (288000 bytes). Sep 8 14:55:55 192.168.100.101 openais[3853]: [TOTEM] Transmit multicast socket send buffer size (262142 bytes). Sep 8 14:55:55 192.168.100.101 openais[3853]: [TOTEM] entering GATHER state from 2. Sep 8 14:55:55 192.168.100.104 openais[19385]: [TOTEM] entering GATHER state from 12. Sep 8 14:55:55 192.168.100.103 openais[3851]: [TOTEM] entering GATHER state from 12. Sep 8 14:55:55 192.168.100.102 openais[12690]: [TOTEM] entering GATHER state from 12. Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] entering GATHER state from 0. Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] entering GATHER state from 0. Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] entering GATHER state from 0. Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] entering GATHER state from 0. Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] Creating commit token because I am the rep. Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] Saving state aru 69 high seq received 69 Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] Storing new sequence id for ring 70 Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] entering COMMIT state. Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] Saving state aru 69 high seq received 69 Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] Storing new sequence id for ring 70 Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] entering COMMIT state. Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] Saving state aru 69 high seq received 69 Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] Storing new sequence id for ring 70 Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] entering COMMIT state. Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] Saving state aru 69 high seq received 69 Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] Storing new sequence id for ring 70 Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] entering COMMIT state. Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] entering RECOVERY state. Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] entering RECOVERY state. Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] entering RECOVERY state. Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] entering RECOVERY state. Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] Sending initial ORF token Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 108 rep 10.103.103.101 Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] aru 69 high delivered 69 received flag 1 Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] New Configuration: Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] Members Left: Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] Members Joined: Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] New Configuration: Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:56:00 192.168.100.102 kernel: dlm: closing connection to node 5 Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] Members Left: Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] Members Joined: Sep 8 14:56:00 192.168.100.103 openais[3851]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] New Configuration: Sep 8 14:56:00 192.168.100.103 openais[3851]: [TOTEM] entering OPERATIONAL state. Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] New Configuration: Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] Members Left: Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] Members Joined: Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] New Configuration: Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] Members Left: Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:56:00 192.168.100.103 kernel: dlm: closing connection to node 5 Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] Members Left: Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] Members Joined: Sep 8 14:56:00 192.168.100.104 openais[19385]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:56:00 192.168.100.104 openais[19385]: [TOTEM] entering OPERATIONAL state. Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 14:56:00 192.168.100.104 kernel: dlm: closing connection to node 5 Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 14:56:00 192.168.100.101 openais[3853]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:56:00 192.168.100.101 openais[3853]: [TOTEM] entering OPERATIONAL state. Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] Members Joined: Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] New Configuration: Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] Members Left: Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] Members Joined: Sep 8 14:56:00 192.168.100.102 openais[12690]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:56:00 192.168.100.102 openais[12690]: [TOTEM] entering OPERATIONAL state. Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:56:00 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:56:00 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:56:00 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:56:00 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:56:00 192.168.100.101 kernel: dlm: closing connection to node 5 Sep 8 14:56:00 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 3 Sep 8 14:56:00 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 3 Sep 8 14:56:00 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 3 Sep 8 14:56:00 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 4 Sep 8 14:56:00 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 4 Sep 8 14:56:00 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 4 Sep 8 14:56:00 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 1 Sep 8 14:56:00 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 1 Sep 8 14:56:00 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 1 Sep 8 14:56:00 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 2 Sep 8 14:56:00 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 2 Sep 8 14:56:00 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 2 Sep 8 14:56:00 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 3 Sep 8 14:56:00 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 4 Sep 8 14:56:00 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 1 Sep 8 14:56:00 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 2 Sep 8 14:56:00 192.168.100.104 fenced[19405]: fencing deferred to xen1-cluster-if Sep 8 14:56:00 192.168.100.103 fenced[3871]: fencing deferred to xen1-cluster-if Sep 8 14:56:00 192.168.100.102 fenced[12710]: fencing deferred to xen1-cluster-if Sep 8 14:56:05 192.168.100.101 fenced[3873]: xen5-cluster-if not a cluster member after 5 sec post_fail_delay Sep 8 14:56:05 192.168.100.101 fenced[3873]: fencing node "xen5-cluster-if" Sep 8 14:56:05 192.168.100.101 fence_fibernet_cgi: http://pixie.fiber.net/cgi-bin/router-configurator.cgi?action=shutdown&router=bdr5.fbp.ore.fiber.net&port_ifDescr=GigabitEthernet9/35&redirect=no Sep 8 14:56:20 192.168.100.101 fence_fibernet_cgi: Fencing successful! Sep 8 14:56:20 192.168.100.101 fenced[3873]: fence "xen5-cluster-if" success Sep 8 14:57:11 pxe mountd[2162]: authenticated mount request from 192.168.100.105:876 for /opt/xen_5.3/root (/opt/xen_5.3/root) Sep 8 14:57:14 pxe mountd[2162]: authenticated mount request from 192.168.100.105:878 for /opt/xen_5.3/snapshot (/opt/xen_5.3/snapshot) Sep 8 14:57:33 192.168.100.105 syslogd 1.4.1: restart. Sep 8 14:57:33 192.168.100.105 kernel: klogd 1.4.1, log source = /proc/kmsg started. Sep 8 14:57:33 192.168.100.105 kernel: Bootdata ok (command line is root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen5 ) Sep 8 14:57:33 192.168.100.105 kernel: Linux version 2.6.18-128.1.6.el5xen (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Apr 1 09:53:14 EDT 2009 Sep 8 14:57:33 192.168.100.105 kernel: BIOS-provided physical RAM map: Sep 8 14:57:33 192.168.100.105 kernel: Xen: 0000000000000000 - 00000000a0800000 (usable) Sep 8 14:57:33 192.168.100.105 kernel: DMI present. Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x04] enabled) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] enabled) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x06] enabled) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) Sep 8 14:57:33 192.168.100.105 kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24]) Sep 8 14:57:33 192.168.100.105 kernel: IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Sep 8 14:57:33 192.168.100.105 kernel: Setting APIC routing to xen Sep 8 14:57:33 192.168.100.105 kernel: Using ACPI (MADT) for SMP configuration information Sep 8 14:57:33 192.168.100.105 kernel: Allocating PCI resources starting at d1000000 (gap: d0000000:10000000) Sep 8 14:57:33 192.168.100.105 kernel: Built 1 zonelists. Total pages: 657408 Sep 8 14:57:33 192.168.100.105 kernel: Kernel command line: root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen5 Sep 8 14:57:33 192.168.100.105 kernel: Initializing CPU#0 Sep 8 14:57:33 192.168.100.105 kernel: PID hash table entries: 4096 (order: 12, 32768 bytes) Sep 8 14:57:33 192.168.100.105 kernel: Xen reported: 2000.068 MHz processor. Sep 8 14:57:33 192.168.100.105 kernel: Console: colour VGA+ 80x25 Sep 8 14:57:33 192.168.100.105 kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Sep 8 14:57:33 192.168.100.105 kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Sep 8 14:57:33 192.168.100.105 kernel: Software IO TLB enabled: Sep 8 14:57:33 192.168.100.105 kernel: Aperture: 64 megabytes Sep 8 14:57:33 192.168.100.105 kernel: Kernel range: 0xffff8800057c5000 - 0xffff8800097c5000 Sep 8 14:57:33 192.168.100.105 kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Sep 8 14:57:33 192.168.100.105 kernel: Memory: 2467584k/2629632k available (2447k kernel code, 153292k reserved, 1366k data, 180k init) Sep 8 14:57:33 192.168.100.105 kernel: Calibrating delay using timer specific routine.. 5003.03 BogoMIPS (lpj=10006065) Sep 8 14:57:33 192.168.100.105 kernel: Security Framework v1.0.0 initialized Sep 8 14:57:33 192.168.100.105 kernel: SELinux: Initializing. Sep 8 14:57:33 192.168.100.105 kernel: selinux_register_security: Registering secondary module capability Sep 8 14:57:33 192.168.100.105 kernel: Capability LSM initialized as secondary Sep 8 14:57:33 192.168.100.105 kernel: Mount-cache hash table entries: 256 Sep 8 14:57:33 192.168.100.105 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Sep 8 14:57:33 192.168.100.105 kernel: CPU: L2 cache: 6144K Sep 8 14:57:33 192.168.100.105 kernel: CPU: Physical Processor ID: 0 Sep 8 14:57:33 192.168.100.105 kernel: CPU: Processor Core ID: 0 Sep 8 14:57:33 192.168.100.105 kernel: (SMP-)alternatives turned off Sep 8 14:57:33 192.168.100.105 kernel: ACPI: Core revision 20060707 Sep 8 14:57:33 192.168.100.105 kernel: Initializing CPU#1 Sep 8 14:57:33 192.168.100.105 kernel: Initializing CPU#2 Sep 8 14:57:33 192.168.100.105 kernel: Initializing CPU#3 Sep 8 14:57:33 192.168.100.105 kernel: Initializing CPU#4 Sep 8 14:57:33 192.168.100.105 kernel: Initializing CPU#5 Sep 8 14:57:33 192.168.100.105 kernel: Initializing CPU#6 Sep 8 14:57:33 192.168.100.105 kernel: Brought up 8 CPUs Sep 8 14:57:33 192.168.100.105 kernel: Initializing CPU#7 Sep 8 14:57:33 192.168.100.105 kernel: migration_cost=14264 Sep 8 14:57:33 192.168.100.105 kernel: checking if image is initramfs... it is Sep 8 14:57:33 192.168.100.105 kernel: Grant table initialized Sep 8 14:57:33 192.168.100.105 kernel: NET: Registered protocol family 16 Sep 8 14:57:33 192.168.100.105 kernel: No dock devices found. Sep 8 14:57:33 192.168.100.105 kernel: ACPI: bus type pci registered Sep 8 14:57:33 192.168.100.105 kernel: PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved Sep 8 14:57:33 192.168.100.105 kernel: PCI: Not using MMCONFIG. Sep 8 14:57:33 192.168.100.105 kernel: PCI: Using configuration type 1 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: Interpreter enabled Sep 8 14:57:33 192.168.100.105 kernel: ACPI: Using IOAPIC for interrupt routing Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Root Bridge [PCI0] (0000:00) Sep 8 14:57:33 192.168.100.105 kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 Sep 8 14:57:33 192.168.100.105 kernel: PCI: Transparent bridge - 0000:00:1e.0 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 *7 10 11 14 15) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 14 15) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 14 15) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 14 15) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 14:57:33 192.168.100.105 kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Sep 8 14:57:33 192.168.100.105 kernel: pnp: PnP ACPI init Sep 8 14:57:33 192.168.100.105 kernel: pnp: PnP ACPI: found 12 devices Sep 8 14:57:33 192.168.100.105 kernel: xen_mem: Initialising balloon driver. Sep 8 14:57:33 192.168.100.105 kernel: usbcore: registered new driver usbfs Sep 8 14:57:33 192.168.100.105 kernel: usbcore: registered new driver hub Sep 8 14:57:33 192.168.100.105 kernel: PCI: Using ACPI for IRQ routing Sep 8 14:57:33 192.168.100.105 kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Sep 8 14:57:33 192.168.100.105 kernel: NetLabel: Initializing Sep 8 14:57:33 192.168.100.105 kernel: NetLabel: domain hash size = 128 Sep 8 14:57:33 192.168.100.105 kernel: NetLabel: protocols = UNLABELED CIPSOv4 Sep 8 14:57:33 192.168.100.105 kernel: NetLabel: unlabeled traffic allowed by default Sep 8 14:57:33 192.168.100.105 kernel: PCI: Bridge: 0000:02:00.0 Sep 8 14:57:33 192.168.100.105 kernel: IO window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: MEM window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: PREFETCH window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: PCI: Bridge: 0000:02:01.0 Sep 8 14:57:33 192.168.100.105 kernel: IO window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: MEM window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: PREFETCH window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: PCI: Bridge: 0000:02:02.0 Sep 8 14:57:33 192.168.100.105 kernel: IO window: 2000-2fff Sep 8 14:57:33 192.168.100.105 kernel: MEM window: d8000000-d80fffff Sep 8 14:57:33 192.168.100.105 kernel: PREFETCH window: d8400000-d84fffff Sep 8 14:57:33 192.168.100.105 kernel: PCI: Bridge: 0000:01:00.0 Sep 8 14:57:33 192.168.100.105 kernel: IO window: 2000-2fff Sep 8 14:57:33 192.168.100.105 kernel: MEM window: d8000000-d80fffff Sep 8 14:57:33 192.168.100.105 kernel: PREFETCH window: d8400000-d84fffff Sep 8 14:57:33 192.168.100.105 kernel: PCI: Bridge: 0000:01:00.3 Sep 8 14:57:33 192.168.100.105 kernel: IO window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: MEM window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: PREFETCH window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: PCI: Bridge: 0000:00:02.0 Sep 8 14:57:33 192.168.100.105 kernel: IO window: 2000-2fff Sep 8 14:57:33 192.168.100.105 kernel: MEM window: d8000000-d81fffff Sep 8 14:57:33 192.168.100.105 kernel: PREFETCH window: d8400000-d84fffff Sep 8 14:57:33 192.168.100.105 kernel: PCI: Bridge: 0000:00:04.0 Sep 8 14:57:33 192.168.100.105 kernel: IO window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: MEM window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: PREFETCH window: disabled. Sep 8 14:57:33 192.168.100.105 kernel: PCI: Bridge: 0000:00:06.0 Sep 8 14:57:33 192.168.100.105 kernel: IO window: 3000-3fff Sep 8 14:57:33 192.168.100.105 kernel: MEM window: d8200000-d82fffff Sep 8 14:57:33 192.168.100.105 kernel: PREFETCH window: d8500000-d85fffff Sep 8 14:57:33 192.168.100.105 kernel: PCI: Bridge: 0000:00:1e.0 Sep 8 14:57:33 192.168.100.105 kernel: IO window: 4000-4fff Sep 8 14:57:33 192.168.100.105 kernel: MEM window: d8300000-d83fffff Sep 8 14:57:33 192.168.100.105 kernel: PREFETCH window: d0000000-d7ffffff Sep 8 14:57:33 192.168.100.105 kernel: GSI 16 sharing vector 0xA0 and IRQ 16 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 14:57:33 192.168.100.105 kernel: GSI 17 sharing vector 0xA8 and IRQ 17 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 14:57:33 192.168.100.105 kernel: GSI 18 sharing vector 0xB0 and IRQ 18 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 14:57:33 192.168.100.105 kernel: NET: Registered protocol family 2 Sep 8 14:57:33 192.168.100.105 kernel: IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) Sep 8 14:57:33 192.168.100.105 kernel: TCP established hash table entries: 262144 (order: 10, 4194304 bytes) Sep 8 14:57:33 192.168.100.105 kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) Sep 8 14:57:33 192.168.100.105 kernel: TCP: Hash tables configured (established 262144 bind 65536) Sep 8 14:57:33 192.168.100.105 kernel: TCP reno registered Sep 8 14:57:33 192.168.100.105 kernel: Simple Boot Flag at 0x38 set to 0x1 Sep 8 14:57:33 192.168.100.105 kernel: audit: initializing netlink socket (disabled) Sep 8 14:57:33 192.168.100.105 kernel: type=2000 audit(1252421820.056:1): initialized Sep 8 14:57:33 192.168.100.105 kernel: VFS: Disk quotas dquot_6.5.1 Sep 8 14:57:33 192.168.100.105 kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Sep 8 14:57:33 192.168.100.105 kernel: Initializing Cryptographic API Sep 8 14:57:33 192.168.100.105 kernel: alg: No test for crc32c (crc32c-generic) Sep 8 14:57:33 192.168.100.105 kernel: ksign: Installing public key data Sep 8 14:57:33 192.168.100.105 kernel: Loading keyring Sep 8 14:57:33 192.168.100.105 kernel: - Added public key 5535842996BF3A42 Sep 8 14:57:33 192.168.100.105 kernel: - User ID: CentOS (Kernel Module GPG key) Sep 8 14:57:33 192.168.100.105 kernel: io scheduler noop registered Sep 8 14:57:33 192.168.100.105 kernel: io scheduler anticipatory registered Sep 8 14:57:33 192.168.100.105 kernel: io scheduler deadline registered Sep 8 14:57:33 192.168.100.105 kernel: io scheduler cfq registered (default) Sep 8 14:57:33 192.168.100.105 kernel: assign_interrupt_mode Found MSI capability Sep 8 14:57:33 192.168.100.105 kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: Processor [CPU0] (supports 8 throttling states) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: Processor [CPU1] (supports 8 throttling states) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: Processor [CPU2] (supports 8 throttling states) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: Processor [CPU3] (supports 8 throttling states) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: Processor [CPU4] (supports 8 throttling states) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: Processor [CPU5] (supports 8 throttling states) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: Processor [CPU6] (supports 8 throttling states) Sep 8 14:57:33 192.168.100.105 kernel: ACPI: Processor [CPU7] (supports 8 throttling states) Sep 8 14:57:33 192.168.100.105 kernel: Real Time Clock Driver v1.12ac Sep 8 14:57:33 192.168.100.105 kernel: Non-volatile memory driver v1.2 Sep 8 14:57:33 192.168.100.105 kernel: Linux agpgart interface v0.101 (c) Dave Jones Sep 8 14:57:33 192.168.100.105 kernel: RAMDISK driver initialized: 16 RAM disks of 26403K size 4096 blocksize Sep 8 14:57:33 192.168.100.105 kernel: Xen virtual console successfully installed as ttyS0 Sep 8 14:57:33 192.168.100.105 kernel: Event-channel device installed. Sep 8 14:57:33 192.168.100.105 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Sep 8 14:57:33 192.168.100.105 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Sep 8 14:57:33 192.168.100.105 kernel: ESB2: IDE controller at PCI slot 0000:00:1f.1 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 14:57:33 192.168.100.105 kernel: ESB2: chipset revision 9 Sep 8 14:57:33 192.168.100.105 kernel: ESB2: not 100% native mode: will probe irqs later Sep 8 14:57:33 192.168.100.105 kernel: ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:pio, hdb:DMA Sep 8 14:57:33 192.168.100.105 kernel: hdb: DVD-ROM UJDA780, ATAPI CD/DVD-ROM drive Sep 8 14:57:33 192.168.100.105 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Sep 8 14:57:33 192.168.100.105 kernel: ide-floppy driver 0.99.newide Sep 8 14:57:33 192.168.100.105 kernel: usbcore: registered new driver hiddev Sep 8 14:57:33 192.168.100.105 kernel: usbcore: registered new driver usbhid Sep 8 14:57:33 192.168.100.105 kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver Sep 8 14:57:33 192.168.100.105 kernel: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12 Sep 8 14:57:33 192.168.100.105 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Sep 8 14:57:33 192.168.100.105 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Sep 8 14:57:33 192.168.100.105 kernel: mice: PS/2 mouse device common for all mice Sep 8 14:57:33 192.168.100.105 kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 Sep 8 14:57:33 192.168.100.105 kernel: md: bitmap version 4.39 Sep 8 14:57:33 192.168.100.105 kernel: TCP bic registered Sep 8 14:57:33 192.168.100.105 kernel: Initializing IPsec netlink socket Sep 8 14:57:33 192.168.100.105 kernel: NET: Registered protocol family 1 Sep 8 14:57:33 192.168.100.105 kernel: NET: Registered protocol family 17 Sep 8 14:57:33 192.168.100.105 kernel: Write protecting the kernel read-only data: 467k Sep 8 14:57:33 192.168.100.105 kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 Sep 8 14:57:33 192.168.100.105 kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation. Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 14:57:33 192.168.100.105 kernel: 0000:05:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 14:57:33 192.168.100.105 kernel: eth0: (PCI Express:2.5GB/s:Width x4) 00:30:48:c5:8d:50 Sep 8 14:57:33 192.168.100.105 kernel: eth0: Intel(R) PRO/1000 Network Connection Sep 8 14:57:33 192.168.100.105 kernel: eth0: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 14:57:33 192.168.100.105 kernel: GSI 19 sharing vector 0xB8 and IRQ 19 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:05:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 14:57:33 192.168.100.105 kernel: 0000:05:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 14:57:33 192.168.100.105 kernel: eth1: (PCI Express:2.5GB/s:Width x4) 00:30:48:c5:8d:51 Sep 8 14:57:33 192.168.100.105 kernel: eth1: Intel(R) PRO/1000 Network Connection Sep 8 14:57:33 192.168.100.105 kernel: eth1: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:08:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 14:57:33 192.168.100.105 kernel: 0000:08:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 14:57:33 192.168.100.105 kernel: eth2: (PCI Express:2.5GB/s:Width x4) 00:15:17:b9:94:00 Sep 8 14:57:33 192.168.100.105 kernel: eth2: Intel(R) PRO/1000 Network Connection Sep 8 14:57:33 192.168.100.105 kernel: eth2: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:08:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 14:57:33 192.168.100.105 kernel: 0000:08:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 14:57:33 192.168.100.105 kernel: eth3: (PCI Express:2.5GB/s:Width x4) 00:15:17:b9:94:01 Sep 8 14:57:33 192.168.100.105 kernel: eth3: Intel(R) PRO/1000 Network Connection Sep 8 14:57:33 192.168.100.105 kernel: eth3: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 14:57:33 192.168.100.105 kernel: FS-Cache: Loaded Sep 8 14:57:33 192.168.100.105 kernel: eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 8 14:57:33 192.168.100.105 kernel: NET: Registered protocol family 10 Sep 8 14:57:33 192.168.100.105 kernel: lo: Disabled Privacy Extensions Sep 8 14:57:33 192.168.100.105 kernel: IPv6 over IPv4 tunneling driver Sep 8 14:57:33 192.168.100.105 kernel: SELinux: Disabled at runtime. Sep 8 14:57:33 192.168.100.105 kernel: type=1404 audit(1252421843.049:2): selinux=0 auid=4294967295 ses=4294967295 Sep 8 14:57:33 192.168.100.105 kernel: hdb: ATAPI 24X DVD-ROM drive, 2048kB Cache, UDMA(33) Sep 8 14:57:33 192.168.100.105 kernel: Uniform CD-ROM driver Revision: 3.20 Sep 8 14:57:33 192.168.100.105 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Sep 8 14:57:33 192.168.100.105 kernel: 8250_pnp: Unknown symbol serial8250_unregister_port Sep 8 14:57:33 192.168.100.105 kernel: 8250_pnp: Unknown symbol serial8250_register_port Sep 8 14:57:33 192.168.100.105 kernel: USB Universal Host Controller Interface driver v3.0 Sep 8 14:57:33 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 14:57:33 192.168.100.105 kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller Sep 8 14:57:34 192.168.100.105 kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 Sep 8 14:57:34 192.168.100.105 kernel: uhci_hcd 0000:00:1d.0: irq 17, io base 0x00001800 Sep 8 14:57:34 192.168.100.105 kernel: usb usb1: configuration #1 chosen from 1 choice Sep 8 14:57:34 192.168.100.105 kernel: hub 1-0:1.0: USB hub found Sep 8 14:57:34 192.168.100.105 kernel: hub 1-0:1.0: 2 ports detected Sep 8 14:57:34 192.168.100.105 kernel: intel_rng: FWH not detected Sep 8 14:57:34 192.168.100.105 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Sep 8 14:57:34 192.168.100.105 kernel: 8250_pnp: Unknown symbol serial8250_unregister_port Sep 8 14:57:34 192.168.100.105 kernel: 8250_pnp: Unknown symbol serial8250_register_port Sep 8 14:57:34 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 14:57:34 192.168.100.105 kernel: hub 2-0:1.0: USB hub found Sep 8 14:57:34 192.168.100.105 kernel: hub 2-0:1.0: 2 ports detected Sep 8 14:57:34 192.168.100.105 kernel: FDC 0 is a post-1991 82077 Sep 8 14:57:34 192.168.100.105 kernel: md: autorun ... Sep 8 14:57:34 192.168.100.105 kernel: md: ... autorun DONE. Sep 8 14:57:34 192.168.100.105 kernel: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready Sep 8 14:57:37 192.168.100.105 iscsid: connect failed (113) Sep 8 14:57:40 192.168.100.105 iscsid: connect failed (113) Sep 8 14:57:43 192.168.100.105 kernel: eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 8 14:57:43 192.168.100.105 kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready Sep 8 14:57:44 192.168.100.105 iscsid: connect failed (113) Sep 8 14:57:47 192.168.100.105 iscsid: connect failed (113) Sep 8 14:57:47 192.168.100.105 kernel: scsi0 : iSCSI Initiator over TCP/IP Sep 8 14:57:47 192.168.100.105 kernel: scsi1 : iSCSI Initiator over TCP/IP Sep 8 14:57:48 192.168.100.105 kernel: Vendor: Promise Model: VTrak M610i Rev: 021C Sep 8 14:57:48 192.168.100.105 kernel: Type: Direct-Access ANSI SCSI revision: 05 Sep 8 14:57:48 192.168.100.105 kernel: Vendor: Promise Model: VTrak M610i Rev: 021C Sep 8 14:57:48 192.168.100.105 kernel: Type: Direct-Access ANSI SCSI revision: 05 Sep 8 14:57:48 192.168.100.105 rpc.statd[3265]: Version 1.0.9 Starting Sep 8 14:57:48 192.168.100.105 kernel: scsi 0:0:0:0: Attached scsi generic sg0 type 0 Sep 8 14:57:48 192.168.100.105 kernel: scsi 1:0:0:0: Attached scsi generic sg1 type 0 Sep 8 14:57:48 192.168.100.105 kernel: sda : very big device. try to use READ CAPACITY(16). Sep 8 14:57:48 192.168.100.105 kernel: SCSI device sda: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 14:57:48 192.168.100.105 kernel: sda: Write Protect is off Sep 8 14:57:48 192.168.100.105 kernel: SCSI device sda: drive cache: write back w/ FUA Sep 8 14:57:48 192.168.100.105 kernel: sda : very big device. try to use READ CAPACITY(16). Sep 8 14:57:48 192.168.100.105 kernel: SCSI device sda: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 14:57:48 192.168.100.105 kernel: sda: Write Protect is off Sep 8 14:57:48 192.168.100.105 kernel: SCSI device sda: drive cache: write back w/ FUA Sep 8 14:57:48 192.168.100.105 kernel: sda: sda1 Sep 8 14:57:48 192.168.100.105 multipathd: sda: add path (uevent) Sep 8 14:57:48 192.168.100.105 kernel: sd 0:0:0:0: Attached scsi disk sda Sep 8 14:57:48 192.168.100.105 kernel: sdb : very big device. try to use READ CAPACITY(16). Sep 8 14:57:48 192.168.100.105 kernel: SCSI device sdb: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 14:57:48 192.168.100.105 kernel: sdb: Write Protect is off Sep 8 14:57:48 192.168.100.105 kernel: SCSI device sdb: drive cache: write back w/ FUA Sep 8 14:57:48 192.168.100.105 kernel: sdb : very big device. try to use READ CAPACITY(16). Sep 8 14:57:48 192.168.100.105 kernel: SCSI device sdb: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 14:57:48 192.168.100.105 kernel: sdb: Write Protect is off Sep 8 14:57:48 192.168.100.105 kernel: SCSI device sdb: drive cache: write back w/ FUA Sep 8 14:57:48 192.168.100.105 kernel: sdb: sdb1 Sep 8 14:57:48 192.168.100.105 kernel: sd 1:0:0:0: Attached scsi disk sdb Sep 8 14:57:49 192.168.100.105 multipathd: xen: failed in domap for addition of new path sda Sep 8 14:57:49 192.168.100.105 multipathd: uevent trigger error Sep 8 14:57:49 192.168.100.105 multipathd: sdb: add path (uevent) Sep 8 14:57:49 192.168.100.105 multipathd: xen: failed in domap for addition of new path sdb Sep 8 14:57:49 192.168.100.105 multipathd: uevent trigger error Sep 8 14:57:49 192.168.100.105 kernel: device-mapper: multipath round-robin: version 1.0.0 loaded Sep 8 14:57:49 192.168.100.105 multipathd: dm-0: add map (uevent) Sep 8 14:57:49 192.168.100.105 multipathd: xen: event checker started Sep 8 14:57:49 192.168.100.105 iscsid: received iferror -38 Sep 8 14:57:49 192.168.100.105 iscsid: connection1:0 is operational now Sep 8 14:57:49 192.168.100.105 iscsid: received iferror -38 Sep 8 14:57:49 192.168.100.105 iscsid: connection2:0 is operational now Sep 8 14:57:49 192.168.100.105 kernel: Bridge firewalling registered Sep 8 14:57:49 192.168.100.105 kernel: xenbr1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. Sep 8 14:57:50 192.168.100.105 kernel: device vif0.0 entered promiscuous mode Sep 8 14:57:50 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 14:57:50 192.168.100.105 kernel: xenbr1: port 1(vif0.0) entering forwarding state Sep 8 14:57:50 192.168.100.105 multipathd: dm-1: add map (uevent) Sep 8 14:57:50 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): peth1: link is not ready Sep 8 14:57:52 192.168.100.105 kernel: peth1: Link is Up 100 Mbps Full Duplex, Flow Control: None Sep 8 14:57:52 192.168.100.105 kernel: peth1: 10/100 speed: disabling TSO Sep 8 14:57:52 192.168.100.105 kernel: ADDRCONF(NETDEV_CHANGE): peth1: link becomes ready Sep 8 14:57:52 192.168.100.105 kernel: device peth1 entered promiscuous mode Sep 8 14:57:52 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 14:57:52 192.168.100.105 kernel: xenbr1: port 2(peth1) entering forwarding state Sep 8 14:57:52 192.168.100.105 kernel: DLM (built Apr 1 2009 09:54:52) installed Sep 8 14:57:52 192.168.100.105 kernel: GFS2 (built Apr 1 2009 09:56:12) installed Sep 8 14:57:52 192.168.100.105 kernel: Lock_DLM (built Apr 1 2009 09:56:21) installed Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Starting ccsd 2.0.98: Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Built: Jan 21 2009 05:40:28 Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Copyright (C) Red Hat, Inc. 2004 All rights reserved. Sep 8 14:57:52 192.168.100.105 ccsd[4046]: cluster.conf (cluster name = xencluster1, version = 6) found. Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Remote copy of cluster.conf is from quorate node. Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Local version # : 6 Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Remote version #: 6 Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Remote copy of cluster.conf is from quorate node. Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Local version # : 6 Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Remote version #: 6 Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Remote copy of cluster.conf is from quorate node. Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Local version # : 6 Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Remote version #: 6 Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Remote copy of cluster.conf is from quorate node. Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Local version # : 6 Sep 8 14:57:52 192.168.100.105 ccsd[4046]: Remote version #: 6 Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] AIS Executive Service RELEASE 'subrev 1358 version 0.80.3' Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Copyright (C) 2002-2006 MontaVista Software, Inc and contributors. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Copyright (C) 2006 Red Hat, Inc. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] AIS Executive Service: started and ready to provide service. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] openais component openais_cpg loaded. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Registering service handler 'openais cluster closed process group service v1.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] openais component openais_cfg loaded. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Registering service handler 'openais configuration service' Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] openais component openais_msg loaded. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Registering service handler 'openais message service B.01.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] openais component openais_lck loaded. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Registering service handler 'openais distributed locking service B.01.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] openais component openais_evt loaded. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Registering service handler 'openais event service B.01.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] openais component openais_ckpt loaded. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Registering service handler 'openais checkpoint service B.01.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] openais component openais_amf loaded. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Registering service handler 'openais availability management framework B.01.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] openais component openais_clm loaded. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Registering service handler 'openais cluster membership service B.01.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] openais component openais_evs loaded. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Registering service handler 'openais extended virtual synchrony service' Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] openais component openais_cman loaded. Sep 8 14:57:52 192.168.100.105 openais[4052]: [MAIN ] Registering service handler 'openais CMAN membership service 2.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] Token Timeout (10000 ms) retransmit timeout (495 ms) Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] token hold (386 ms) retransmits before loss (20 retrans) Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] join (60 ms) send_join (0 ms) consensus (4800 ms) merge (200 ms) Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] downcheck (1000 ms) fail to recv const (50 msgs) Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] seqno unchanged const (30 rotations) Maximum network MTU 1500 Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] window size per rotation (50 messages) maximum messages per rotation (17 messages) Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] send threads (0 threads) Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] RRP token expired timeout (495 ms) Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] RRP token problem counter (2000 ms) Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] RRP threshold (10 problem count) Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] RRP mode set to none. Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] heartbeat_failures_allowed (0) Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] max_network_delay (50 ms) Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] HeartBeat is Disabled. To enable set heartbeat_failures_allowed > 0 Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] Receive multicast socket recv buffer size (262142 bytes). Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] Transmit multicast socket send buffer size (262142 bytes). Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] The network interface [10.103.103.105] is now up. Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] Created or loaded sequence id 108.10.103.103.105 for this ring. Sep 8 14:57:52 192.168.100.105 openais[4052]: [TOTEM] entering GATHER state from 15. Sep 8 14:57:52 192.168.100.105 openais[4052]: [SERV ] Initialising service handler 'openais extended virtual synchrony service' Sep 8 14:57:52 192.168.100.105 openais[4052]: [SERV ] Initialising service handler 'openais cluster membership service B.01.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [SERV ] Initialising service handler 'openais availability management framework B.01.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [SERV ] Initialising service handler 'openais checkpoint service B.01.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [SERV ] Initialising service handler 'openais event service B.01.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [SERV ] Initialising service handler 'openais distributed locking service B.01.01' Sep 8 14:57:52 192.168.100.103 openais[3851]: [TOTEM] entering GATHER state from 11. Sep 8 14:57:52 192.168.100.105 openais[4052]: [SERV ] Initialising service handler 'openais message service B.01.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [SERV ] Initialising service handler 'openais configuration service' Sep 8 14:57:52 192.168.100.105 openais[4052]: [SERV ] Initialising service handler 'openais cluster closed process group service v1.01' Sep 8 14:57:52 192.168.100.105 openais[4052]: [SERV ] Initialising service handler 'openais CMAN membership service 2.01' Sep 8 14:57:52 192.168.100.104 openais[19385]: [TOTEM] entering GATHER state from 11. Sep 8 14:57:52 192.168.100.105 openais[4052]: [CMAN ] CMAN 2.0.98 (built Jan 21 2009 05:40:32) started Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] entering GATHER state from 11. Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] entering GATHER state from 11. Sep 8 14:57:53 192.168.100.105 openais[4052]: [SYNC ] Not using a virtual synchrony filter. Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] Creating commit token because I am the rep. Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] Saving state aru 0 high seq received 0 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] Storing new sequence id for ring 70 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] entering COMMIT state. Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] entering RECOVERY state. Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] position [0] member 10.103.103.105: Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 108 rep 10.103.103.105 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] aru 0 high delivered 0 received flag 1 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] Sending initial ORF token Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.105 openais[4052]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] entering OPERATIONAL state. Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] entering GATHER state from 11. Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] Creating commit token because I am the rep. Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] Saving state aru 42 high seq received 42 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] Storing new sequence id for ring 74 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] entering COMMIT state. Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] Saving state aru 42 high seq received 42 Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] Storing new sequence id for ring 74 Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] entering COMMIT state. Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] Saving state aru 42 high seq received 42 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] Storing new sequence id for ring 74 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] entering COMMIT state. Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] Saving state aru 42 high seq received 42 Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] Storing new sequence id for ring 74 Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] entering COMMIT state. Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] Saving state aru a high seq received a Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] Storing new sequence id for ring 74 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] entering COMMIT state. Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] entering RECOVERY state. Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] position [4] member 10.103.103.105: Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 112 rep 10.103.103.105 Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] entering RECOVERY state. Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] aru a high delivered a received flag 1 Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] entering RECOVERY state. Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] entering RECOVERY state. Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] position [4] member 10.103.103.105: Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] position [4] member 10.103.103.105: Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 112 rep 10.103.103.105 Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] aru a high delivered a received flag 1 Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 112 rep 10.103.103.105 Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] aru a high delivered a received flag 1 Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] entering RECOVERY state. Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] position [0] member 10.103.103.101: Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] position [4] member 10.103.103.105: Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] previous ring seq 112 rep 10.103.103.105 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] aru a high delivered a received flag 1 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] position [1] member 10.103.103.102: Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] position [2] member 10.103.103.103: Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] position [3] member 10.103.103.104: Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] Sending initial ORF token Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 112 rep 10.103.103.101 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] aru 42 high delivered 42 received flag 1 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] position [4] member 10.103.103.105: Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 112 rep 10.103.103.105 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] aru a high delivered a received flag 1 Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.103 openais[3851]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:57:53 192.168.100.103 openais[3851]: [TOTEM] entering OPERATIONAL state. Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:57:53 192.168.100.102 openais[12690]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.102 openais[12690]: [TOTEM] entering OPERATIONAL state. Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.104 openais[19385]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.104 openais[19385]: [TOTEM] entering OPERATIONAL state. Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:57:53 192.168.100.105 openais[4052]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:57:53 192.168.100.105 openais[4052]: [TOTEM] entering OPERATIONAL state. Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 14:57:53 192.168.100.101 openais[3853]: [SYNC ] This node is within the primary component and will provide service. Sep 8 14:57:53 192.168.100.101 openais[3853]: [TOTEM] entering OPERATIONAL state. Sep 8 14:57:53 192.168.100.105 openais[4052]: [CMAN ] quorum regained, resuming activity Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:57:53 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 14:57:53 192.168.100.104 openais[19385]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 14:57:53 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 14:57:53 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 14:57:53 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 14:57:53 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 4 Sep 8 14:57:53 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 4 Sep 8 14:57:53 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 4 Sep 8 14:57:53 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 4 Sep 8 14:57:53 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 4 Sep 8 14:57:53 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 1 Sep 8 14:57:53 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 1 Sep 8 14:57:53 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 1 Sep 8 14:57:53 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 1 Sep 8 14:57:53 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 2 Sep 8 14:57:53 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 1 Sep 8 14:57:53 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 2 Sep 8 14:57:53 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 2 Sep 8 14:57:53 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 2 Sep 8 14:57:53 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 2 Sep 8 14:57:53 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 3 Sep 8 14:57:53 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 3 Sep 8 14:57:53 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 3 Sep 8 14:57:53 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 3 Sep 8 14:57:53 192.168.100.104 openais[19385]: [CPG ] got joinlist message from node 3 Sep 8 14:57:53 192.168.100.105 ccsd[4046]: Initial status:: Quorate Sep 8 14:57:56 pxe mountd[2162]: authenticated mount request from 192.168.100.105:927 for /opt/xenxml (/opt/xenxml) Sep 8 14:57:56 192.168.100.105 kernel: GFS2: fsid=: Trying to join cluster "lock_dlm", "xencluster1:xenclusterfs1" Sep 8 14:57:56 192.168.100.105 kernel: dlm: Using TCP for communications Sep 8 14:57:56 192.168.100.105 kernel: dlm: connecting to 1 Sep 8 14:57:56 192.168.100.101 kernel: dlm: got connection from 5 Sep 8 14:57:56 192.168.100.105 kernel: dlm: connecting to 2 Sep 8 14:57:56 192.168.100.103 kernel: dlm: connecting to 5 Sep 8 14:57:56 192.168.100.104 kernel: dlm: connecting to 5 Sep 8 14:57:56 192.168.100.102 kernel: dlm: connecting to 5 Sep 8 14:57:56 192.168.100.102 kernel: dlm: got connection from 5 Sep 8 14:57:56 192.168.100.105 kernel: dlm: got connection from 2 Sep 8 14:57:56 192.168.100.105 kernel: dlm: connecting to 3 Sep 8 14:57:56 192.168.100.105 kernel: dlm: got connection from 3 Sep 8 14:57:56 192.168.100.105 kernel: dlm: got connection from 4 Sep 8 14:57:56 192.168.100.103 kernel: dlm: got connection from 5 Sep 8 14:57:56 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: Joined cluster. Now mounting FS... Sep 8 14:57:57 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=4, already locked for use Sep 8 14:57:57 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=4: Looking at journal... Sep 8 14:57:57 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=4: Done Sep 8 14:57:58 192.168.100.105 gpm[4296]: *** info [startup.c(95)]: Sep 8 14:57:58 192.168.100.105 gpm[4296]: Started gpm successfully. Entered daemon mode. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70). Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Successfully dropped root privileges. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: avahi-daemon 0.6.16 starting up. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Successfully called chroot(). Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Successfully dropped remaining capabilities. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Loading service file /services/sftp-ssh.service. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: New relevant interface eth3.IPv6 for mDNS. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface eth3.IPv6 with address fe80::215:17ff:feb9:9401. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: New relevant interface eth3.IPv4 for mDNS. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface eth3.IPv4 with address 10.103.103.105. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: New relevant interface eth2.IPv6 for mDNS. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface eth2.IPv6 with address fe80::215:17ff:feb9:9400. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: New relevant interface eth2.IPv4 for mDNS. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.102.102.105. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: New relevant interface eth0.IPv6 for mDNS. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::230:48ff:fec5:8d50. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: New relevant interface eth0.IPv4 for mDNS. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.100.105. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Network interface enumeration completed. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::215:17ff:feb9:9401 on eth3. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Registering new address record for 10.103.103.105 on eth3. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::215:17ff:feb9:9400 on eth2. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Registering new address record for 10.102.102.105 on eth2. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::230:48ff:fec5:8d50 on eth0. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Registering new address record for 192.168.100.105 on eth0. Sep 8 14:58:00 192.168.100.105 avahi-daemon[4535]: Registering HINFO record with values 'X86_64'/'LINUX'. Sep 8 14:58:01 192.168.100.105 avahi-daemon[4535]: Server startup complete. Host name is xen5.local. Local service cookie is 1941331816. Sep 8 14:58:02 192.168.100.105 avahi-daemon[4535]: Service "SFTP File Transfer on xen5" (/services/sftp-ssh.service) successfully established. Sep 8 14:58:04 192.168.100.105 xenstored: Checking store ... Sep 8 14:58:04 192.168.100.105 xenstored: Checking store complete. Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 14 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 271 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 272 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 273 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 18 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 277 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 278 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 279 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 19 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 274 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 275 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 276 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 268 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 269 Sep 8 14:58:04 192.168.100.105 kernel: Breaking affinity for irq 270 Sep 8 14:58:05 192.168.100.105 smartd[4788]: smartd version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Sep 8 14:58:05 192.168.100.105 smartd[4788]: Home page is http://smartmontools.sourceforge.net/ Sep 8 14:58:05 192.168.100.105 smartd[4788]: Opened configuration file /etc/smartd.conf Sep 8 14:58:05 192.168.100.105 smartd[4788]: Configuration file /etc/smartd.conf parsed. Sep 8 14:58:05 192.168.100.105 smartd[4788]: Device: /dev/sda, opened Sep 8 14:58:05 192.168.100.105 smartd[4788]: Device: /dev/sda, not ATA, no IDENTIFY DEVICE Structure Sep 8 14:58:05 192.168.100.105 smartd[4788]: Unable to register ATA device /dev/sda at line 32 of file /etc/smartd.conf Sep 8 14:58:05 192.168.100.105 smartd[4788]: Device /dev/sda not available Sep 8 14:58:05 192.168.100.105 smartd[4788]: Monitoring 0 ATA and 0 SCSI devices Sep 8 14:58:05 192.168.100.105 smartd[4790]: smartd has fork()ed into background mode. New PID=4790. Sep 8 14:58:08 192.168.100.105 kernel: loop: loaded (max 150 devices) Sep 8 14:58:08 192.168.100.105 kernel: tun: Universal TUN/TAP device driver, 1.6 Sep 8 14:58:08 192.168.100.105 kernel: tun: (C) 1999-2004 Max Krasnyansky Sep 8 14:58:10 192.168.100.105 kernel: device tap0 entered promiscuous mode Sep 8 14:58:10 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 14:58:10 192.168.100.105 kernel: xenbr1: port 3(tap0) entering forwarding state Sep 8 14:58:11 192.168.100.105 kernel: device vif1.0 entered promiscuous mode Sep 8 14:58:11 192.168.100.105 avahi-daemon[4535]: New relevant interface tap0.IPv6 for mDNS. Sep 8 14:58:11 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap0.IPv6 with address fe80::34e8:94ff:fe4e:ab32. Sep 8 14:58:11 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::34e8:94ff:fe4e:ab32 on tap0. Sep 8 14:58:11 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif1.0: link is not ready Sep 8 14:58:12 192.168.100.105 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team Sep 8 14:58:21 192.168.100.105 kernel: device tap1 entered promiscuous mode Sep 8 14:58:21 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 14:58:21 192.168.100.105 kernel: xenbr1: port 5(tap1) entering forwarding state Sep 8 14:58:21 192.168.100.105 kernel: device vif2.0 entered promiscuous mode Sep 8 14:58:21 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif2.0: link is not ready Sep 8 14:58:22 192.168.100.105 avahi-daemon[4535]: New relevant interface tap1.IPv6 for mDNS. Sep 8 14:58:22 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap1.IPv6 with address fe80::1816:41ff:fe2d:5040. Sep 8 14:58:22 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::1816:41ff:fe2d:5040 on tap1. Sep 8 14:58:32 192.168.100.105 kernel: device tap2 entered promiscuous mode Sep 8 14:58:32 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 14:58:32 192.168.100.105 kernel: xenbr1: port 7(tap2) entering forwarding state Sep 8 14:58:32 192.168.100.105 kernel: device vif3.0 entered promiscuous mode Sep 8 14:58:32 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif3.0: link is not ready Sep 8 14:58:33 192.168.100.105 avahi-daemon[4535]: New relevant interface tap2.IPv6 for mDNS. Sep 8 14:58:33 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap2.IPv6 with address fe80::dcaf:dfff:fe09:2d84. Sep 8 14:58:33 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::dcaf:dfff:fe09:2d84 on tap2. Sep 8 14:58:41 192.168.100.105 kernel: device tap3 entered promiscuous mode Sep 8 14:58:41 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 14:58:41 192.168.100.105 kernel: xenbr1: port 9(tap3) entering forwarding state Sep 8 14:58:41 192.168.100.105 kernel: device vif4.0 entered promiscuous mode Sep 8 14:58:41 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif4.0: link is not ready Sep 8 14:58:42 192.168.100.105 avahi-daemon[4535]: New relevant interface tap3.IPv6 for mDNS. Sep 8 14:58:42 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap3.IPv6 with address fe80::c085:7aff:feeb:4a63. Sep 8 14:58:42 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::c085:7aff:feeb:4a63 on tap3. Sep 8 14:58:52 192.168.100.105 kernel: device tap4 entered promiscuous mode Sep 8 14:58:52 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 14:58:52 192.168.100.105 kernel: xenbr1: port 11(tap4) entering forwarding state Sep 8 14:58:52 192.168.100.105 kernel: device vif5.0 entered promiscuous mode Sep 8 14:58:52 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif5.0: link is not ready Sep 8 14:58:53 192.168.100.105 avahi-daemon[4535]: New relevant interface tap4.IPv6 for mDNS. Sep 8 14:58:53 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap4.IPv6 with address fe80::bc75:8dff:fead:50ae. Sep 8 14:58:53 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::bc75:8dff:fead:50ae on tap4. Sep 8 14:59:55 192.168.100.105 kernel: blkback: ring-ref 8, event-channel 4, protocol 1 (x86_64-abi) Sep 8 14:59:55 192.168.100.105 kernel: blkback: ring-ref 9, event-channel 5, protocol 1 (x86_64-abi) Sep 8 14:59:55 192.168.100.105 kernel: blkback: ring-ref 10, event-channel 6, protocol 1 (x86_64-abi) Sep 8 15:01:18 192.168.100.104 shutdown[1648]: shutting down for system halt Sep 8 15:01:32 192.168.100.105 openais[4052]: [TOTEM] The token was lost in the OPERATIONAL state. Sep 8 15:01:32 192.168.100.105 openais[4052]: [TOTEM] Receive multicast socket recv buffer size (288000 bytes). Sep 8 15:01:32 192.168.100.105 openais[4052]: [TOTEM] Transmit multicast socket send buffer size (262142 bytes). Sep 8 15:01:32 192.168.100.105 openais[4052]: [TOTEM] entering GATHER state from 2. Sep 8 15:01:32 192.168.100.103 openais[3851]: [TOTEM] entering GATHER state from 12. Sep 8 15:01:32 192.168.100.101 openais[3853]: [TOTEM] entering GATHER state from 12. Sep 8 15:01:32 192.168.100.102 openais[12690]: [TOTEM] entering GATHER state from 12. Sep 8 15:01:37 192.168.100.103 kernel: usb 2-2: USB disconnect, address 2 Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] entering GATHER state from 0. Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] entering GATHER state from 11. Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] entering GATHER state from 11. Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] entering GATHER state from 11. Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] Creating commit token because I am the rep. Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] Saving state aru 75 high seq received 75 Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] Storing new sequence id for ring 78 Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] entering COMMIT state. Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] Saving state aru 75 high seq received 75 Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] Storing new sequence id for ring 78 Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] entering COMMIT state. Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] Saving state aru 75 high seq received 75 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] Storing new sequence id for ring 78 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] entering COMMIT state. Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] Saving state aru 75 high seq received 75 Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] Storing new sequence id for ring 78 Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] entering COMMIT state. Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] entering RECOVERY state. Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] position [0] member 10.103.103.101: Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] position [1] member 10.103.103.102: Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] position [2] member 10.103.103.103: Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] position [3] member 10.103.103.105: Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] entering RECOVERY state. Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] position [0] member 10.103.103.101: Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] entering RECOVERY state. Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] position [0] member 10.103.103.101: Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] position [1] member 10.103.103.102: Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] position [1] member 10.103.103.102: Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] position [2] member 10.103.103.103: Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] position [2] member 10.103.103.103: Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] position [3] member 10.103.103.105: Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] position [3] member 10.103.103.105: Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] entering RECOVERY state. Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] position [0] member 10.103.103.101: Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] position [1] member 10.103.103.102: Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] position [2] member 10.103.103.103: Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] Sending initial ORF token Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] position [3] member 10.103.103.105: Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 116 rep 10.103.103.101 Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] aru 75 high delivered 75 received flag 1 Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] New Configuration: Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] Members Left: Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] Members Joined: Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] New Configuration: Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] Members Left: Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] Members Joined: Sep 8 15:01:37 192.168.100.103 openais[3851]: [SYNC ] This node is within the primary component and will provide service. Sep 8 15:01:37 192.168.100.103 openais[3851]: [TOTEM] entering OPERATIONAL state. Sep 8 15:01:37 192.168.100.102 kernel: dlm: closing connection to node 4 Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] New Configuration: Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] Members Left: Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] Members Joined: Sep 8 15:01:37 192.168.100.103 kernel: dlm: closing connection to node 4 Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:01:37 192.168.100.105 kernel: dlm: closing connection to node 4 Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] New Configuration: Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 15:01:37 192.168.100.101 openais[3853]: [SYNC ] This node is within the primary component and will provide service. Sep 8 15:01:37 192.168.100.101 openais[3853]: [TOTEM] entering OPERATIONAL state. Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:01:37 192.168.100.101 kernel: dlm: closing connection to node 4 Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 15:01:37 192.168.100.105 openais[4052]: [SYNC ] This node is within the primary component and will provide service. Sep 8 15:01:37 192.168.100.105 openais[4052]: [TOTEM] entering OPERATIONAL state. Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] Members Left: Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] Members Joined: Sep 8 15:01:37 192.168.100.102 openais[12690]: [SYNC ] This node is within the primary component and will provide service. Sep 8 15:01:37 192.168.100.102 openais[12690]: [TOTEM] entering OPERATIONAL state. Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 15:01:37 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 15:01:37 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 15:01:37 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 15:01:37 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 15:01:37 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 3 Sep 8 15:01:37 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 3 Sep 8 15:01:37 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 3 Sep 8 15:01:37 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 5 Sep 8 15:01:37 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 3 Sep 8 15:01:37 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 5 Sep 8 15:01:37 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 5 Sep 8 15:01:37 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 1 Sep 8 15:01:37 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 5 Sep 8 15:01:37 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 1 Sep 8 15:01:37 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 1 Sep 8 15:01:37 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 2 Sep 8 15:01:37 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 1 Sep 8 15:01:37 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 2 Sep 8 15:01:37 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 2 Sep 8 15:01:37 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 2 Sep 8 15:01:37 192.168.100.102 fenced[12710]: fencing deferred to xen1-cluster-if Sep 8 15:01:37 192.168.100.105 fenced[4075]: fencing deferred to xen1-cluster-if Sep 8 15:01:37 192.168.100.103 fenced[3871]: fencing deferred to xen1-cluster-if Sep 8 15:01:42 192.168.100.101 fenced[3873]: xen4-cluster-if not a cluster member after 5 sec post_fail_delay Sep 8 15:01:42 192.168.100.101 fenced[3873]: fencing node "xen4-cluster-if" Sep 8 15:01:42 192.168.100.101 fence_fibernet_cgi: http://pixie.fiber.net/cgi-bin/router-configurator.cgi?action=shutdown&router=bdr5.fbp.ore.fiber.net&port_ifDescr=GigabitEthernet9/36&redirect=no Sep 8 15:01:56 192.168.100.101 fence_fibernet_cgi: Fencing successful! Sep 8 15:01:56 192.168.100.101 fenced[3873]: fence "xen4-cluster-if" success Sep 8 15:01:56 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: jid=0: Trying to acquire journal lock... Sep 8 15:01:56 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=0: Trying to acquire journal lock... Sep 8 15:01:56 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=0: Trying to acquire journal lock... Sep 8 15:01:56 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=0: Trying to acquire journal lock... Sep 8 15:01:57 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: jid=0: Busy Sep 8 15:01:57 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=0: Busy Sep 8 15:01:57 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=0: Busy Sep 8 15:01:57 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=0: Looking at journal... Sep 8 15:01:57 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=0: Acquiring the transaction lock... Sep 8 15:01:57 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=0: Replaying journal... Sep 8 15:01:57 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=0: Replayed 30 of 30 blocks Sep 8 15:01:57 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=0: Found 0 revoke tags Sep 8 15:01:57 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=0: Journal replayed in 1s Sep 8 15:01:57 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=0: Done Sep 8 15:02:03 192.168.100.102 kernel: device tap16 entered promiscuous mode Sep 8 15:02:03 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 15:02:03 192.168.100.102 kernel: xenbr1: port 35(tap16) entering forwarding state Sep 8 15:02:03 192.168.100.102 kernel: device vif33.0 entered promiscuous mode Sep 8 15:02:03 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): vif33.0: link is not ready Sep 8 15:02:04 192.168.100.102 avahi-daemon[4486]: New relevant interface tap16.IPv6 for mDNS. Sep 8 15:02:04 192.168.100.102 avahi-daemon[4486]: Joining mDNS multicast group on interface tap16.IPv6 with address fe80::1c90:55ff:fe96:2f91. Sep 8 15:02:04 192.168.100.102 avahi-daemon[4486]: Registering new address record for fe80::1c90:55ff:fe96:2f91 on tap16. Sep 8 15:02:16 192.168.100.102 kernel: device tap17 entered promiscuous mode Sep 8 15:02:16 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 15:02:16 192.168.100.102 kernel: xenbr1: port 37(tap17) entering forwarding state Sep 8 15:02:17 192.168.100.102 kernel: device vif34.0 entered promiscuous mode Sep 8 15:02:17 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): vif34.0: link is not ready Sep 8 15:02:17 192.168.100.105 kernel: device tap5 entered promiscuous mode Sep 8 15:02:17 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:02:17 192.168.100.105 kernel: xenbr1: port 13(tap5) entering forwarding state Sep 8 15:02:18 192.168.100.105 kernel: device vif6.0 entered promiscuous mode Sep 8 15:02:18 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif6.0: link is not ready Sep 8 15:02:18 192.168.100.102 avahi-daemon[4486]: New relevant interface tap17.IPv6 for mDNS. Sep 8 15:02:18 192.168.100.102 avahi-daemon[4486]: Joining mDNS multicast group on interface tap17.IPv6 with address fe80::fce9:3aff:fe0f:5685. Sep 8 15:02:18 192.168.100.102 avahi-daemon[4486]: Registering new address record for fe80::fce9:3aff:fe0f:5685 on tap17. Sep 8 15:02:19 192.168.100.105 avahi-daemon[4535]: New relevant interface tap5.IPv6 for mDNS. Sep 8 15:02:19 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap5.IPv6 with address fe80::6492:46ff:fe7e:38dd. Sep 8 15:02:19 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::6492:46ff:fe7e:38dd on tap5. Sep 8 15:02:34 pxe mountd[2162]: authenticated mount request from 192.168.100.104:877 for /opt/xen_5.3/root (/opt/xen_5.3/root) Sep 8 15:02:34 pxe mountd[2162]: authenticated mount request from 192.168.100.104:879 for /opt/xen_5.3/snapshot (/opt/xen_5.3/snapshot) Sep 8 15:02:39 192.168.100.105 kernel: device tap6 entered promiscuous mode Sep 8 15:02:39 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:02:39 192.168.100.105 kernel: xenbr1: port 15(tap6) entering forwarding state Sep 8 15:02:39 192.168.100.105 kernel: device vif7.0 entered promiscuous mode Sep 8 15:02:39 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif7.0: link is not ready Sep 8 15:02:41 192.168.100.105 avahi-daemon[4535]: New relevant interface tap6.IPv6 for mDNS. Sep 8 15:02:41 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap6.IPv6 with address fe80::9cc7:5eff:fe09:bb9b. Sep 8 15:02:41 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::9cc7:5eff:fe09:bb9b on tap6. Sep 8 15:02:54 192.168.100.104 syslogd 1.4.1: restart. Sep 8 15:02:54 192.168.100.104 kernel: klogd 1.4.1, log source = /proc/kmsg started. Sep 8 15:02:54 192.168.100.104 kernel: Bootdata ok (command line is root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen4 ) Sep 8 15:02:54 192.168.100.104 kernel: Linux version 2.6.18-128.1.6.el5xen (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Apr 1 09:53:14 EDT 2009 Sep 8 15:02:54 192.168.100.104 kernel: BIOS-provided physical RAM map: Sep 8 15:02:54 192.168.100.104 kernel: Xen: 0000000000000000 - 00000000a0800000 (usable) Sep 8 15:02:54 192.168.100.104 kernel: DMI present. Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x04] enabled) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] enabled) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x06] enabled) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) Sep 8 15:02:54 192.168.100.104 kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24]) Sep 8 15:02:54 192.168.100.104 kernel: IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Sep 8 15:02:54 192.168.100.104 kernel: Setting APIC routing to xen Sep 8 15:02:54 192.168.100.104 kernel: Using ACPI (MADT) for SMP configuration information Sep 8 15:02:54 192.168.100.104 kernel: Allocating PCI resources starting at d1000000 (gap: d0000000:10000000) Sep 8 15:02:54 192.168.100.104 kernel: Built 1 zonelists. Total pages: 657408 Sep 8 15:02:54 192.168.100.104 kernel: Kernel command line: root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen4 Sep 8 15:02:54 192.168.100.104 kernel: Initializing CPU#0 Sep 8 15:02:54 192.168.100.104 kernel: PID hash table entries: 4096 (order: 12, 32768 bytes) Sep 8 15:02:54 192.168.100.104 kernel: Xen reported: 2000.070 MHz processor. Sep 8 15:02:54 192.168.100.104 kernel: Console: colour VGA+ 80x25 Sep 8 15:02:54 192.168.100.104 kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Sep 8 15:02:54 192.168.100.104 kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Sep 8 15:02:54 192.168.100.104 kernel: Software IO TLB enabled: Sep 8 15:02:54 192.168.100.104 kernel: Aperture: 64 megabytes Sep 8 15:02:54 192.168.100.104 kernel: Kernel range: 0xffff8800057c5000 - 0xffff8800097c5000 Sep 8 15:02:54 192.168.100.104 kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Sep 8 15:02:54 192.168.100.104 kernel: Memory: 2467584k/2629632k available (2447k kernel code, 153292k reserved, 1366k data, 180k init) Sep 8 15:02:54 192.168.100.104 kernel: Calibrating delay using timer specific routine.. 5003.13 BogoMIPS (lpj=10006275) Sep 8 15:02:54 192.168.100.104 kernel: Security Framework v1.0.0 initialized Sep 8 15:02:54 192.168.100.104 kernel: SELinux: Initializing. Sep 8 15:02:54 192.168.100.104 kernel: selinux_register_security: Registering secondary module capability Sep 8 15:02:54 192.168.100.104 kernel: Capability LSM initialized as secondary Sep 8 15:02:54 192.168.100.104 kernel: Mount-cache hash table entries: 256 Sep 8 15:02:54 192.168.100.104 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Sep 8 15:02:54 192.168.100.104 kernel: CPU: L2 cache: 6144K Sep 8 15:02:54 192.168.100.104 kernel: CPU: Physical Processor ID: 0 Sep 8 15:02:54 192.168.100.104 kernel: CPU: Processor Core ID: 0 Sep 8 15:02:54 192.168.100.104 kernel: (SMP-)alternatives turned off Sep 8 15:02:54 192.168.100.104 kernel: ACPI: Core revision 20060707 Sep 8 15:02:54 192.168.100.104 kernel: Initializing CPU#1 Sep 8 15:02:54 192.168.100.104 kernel: Initializing CPU#2 Sep 8 15:02:54 192.168.100.104 kernel: Initializing CPU#3 Sep 8 15:02:54 192.168.100.104 kernel: Initializing CPU#4 Sep 8 15:02:54 192.168.100.104 kernel: Initializing CPU#5 Sep 8 15:02:54 192.168.100.104 kernel: Initializing CPU#6 Sep 8 15:02:54 192.168.100.104 kernel: Brought up 8 CPUs Sep 8 15:02:54 192.168.100.104 kernel: Initializing CPU#7 Sep 8 15:02:54 192.168.100.104 kernel: migration_cost=1476 Sep 8 15:02:54 192.168.100.104 kernel: checking if image is initramfs... it is Sep 8 15:02:54 192.168.100.104 kernel: Grant table initialized Sep 8 15:02:54 192.168.100.104 kernel: NET: Registered protocol family 16 Sep 8 15:02:54 192.168.100.104 kernel: No dock devices found. Sep 8 15:02:54 192.168.100.104 kernel: ACPI: bus type pci registered Sep 8 15:02:54 192.168.100.104 kernel: PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved Sep 8 15:02:54 192.168.100.104 kernel: PCI: Not using MMCONFIG. Sep 8 15:02:54 192.168.100.104 kernel: PCI: Using configuration type 1 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: Interpreter enabled Sep 8 15:02:54 192.168.100.104 kernel: ACPI: Using IOAPIC for interrupt routing Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Root Bridge [PCI0] (0000:00) Sep 8 15:02:54 192.168.100.104 kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 Sep 8 15:02:54 192.168.100.104 kernel: PCI: Transparent bridge - 0000:00:1e.0 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 *7 10 11 14 15) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 14 15) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 14 15) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 14 15) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 15:02:54 192.168.100.104 kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Sep 8 15:02:54 192.168.100.104 kernel: pnp: PnP ACPI init Sep 8 15:02:54 192.168.100.104 kernel: pnp: PnP ACPI: found 12 devices Sep 8 15:02:54 192.168.100.104 kernel: xen_mem: Initialising balloon driver. Sep 8 15:02:54 192.168.100.104 kernel: usbcore: registered new driver usbfs Sep 8 15:02:54 192.168.100.104 kernel: usbcore: registered new driver hub Sep 8 15:02:54 192.168.100.104 kernel: PCI: Using ACPI for IRQ routing Sep 8 15:02:54 192.168.100.104 kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Sep 8 15:02:54 192.168.100.104 kernel: NetLabel: Initializing Sep 8 15:02:54 192.168.100.104 kernel: NetLabel: domain hash size = 128 Sep 8 15:02:54 192.168.100.104 kernel: NetLabel: protocols = UNLABELED CIPSOv4 Sep 8 15:02:54 192.168.100.104 kernel: NetLabel: unlabeled traffic allowed by default Sep 8 15:02:54 192.168.100.104 kernel: PCI: Bridge: 0000:02:00.0 Sep 8 15:02:54 192.168.100.104 kernel: IO window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: MEM window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: PREFETCH window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: PCI: Bridge: 0000:02:01.0 Sep 8 15:02:54 192.168.100.104 kernel: IO window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: MEM window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: PREFETCH window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: PCI: Bridge: 0000:02:02.0 Sep 8 15:02:54 192.168.100.104 kernel: IO window: 2000-2fff Sep 8 15:02:54 192.168.100.104 kernel: MEM window: d8000000-d80fffff Sep 8 15:02:54 192.168.100.104 kernel: PREFETCH window: d8400000-d84fffff Sep 8 15:02:54 192.168.100.104 kernel: PCI: Bridge: 0000:01:00.0 Sep 8 15:02:54 192.168.100.104 kernel: IO window: 2000-2fff Sep 8 15:02:54 192.168.100.104 kernel: MEM window: d8000000-d80fffff Sep 8 15:02:54 192.168.100.104 kernel: PREFETCH window: d8400000-d84fffff Sep 8 15:02:54 192.168.100.104 kernel: PCI: Bridge: 0000:01:00.3 Sep 8 15:02:54 192.168.100.104 kernel: IO window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: MEM window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: PREFETCH window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: PCI: Bridge: 0000:00:02.0 Sep 8 15:02:54 192.168.100.104 kernel: IO window: 2000-2fff Sep 8 15:02:54 192.168.100.104 kernel: MEM window: d8000000-d81fffff Sep 8 15:02:54 192.168.100.104 kernel: PREFETCH window: d8400000-d84fffff Sep 8 15:02:54 192.168.100.104 kernel: PCI: Bridge: 0000:00:04.0 Sep 8 15:02:54 192.168.100.104 kernel: IO window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: MEM window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: PREFETCH window: disabled. Sep 8 15:02:54 192.168.100.104 kernel: PCI: Bridge: 0000:00:06.0 Sep 8 15:02:54 192.168.100.104 kernel: IO window: 3000-3fff Sep 8 15:02:54 192.168.100.104 kernel: MEM window: d8200000-d82fffff Sep 8 15:02:54 192.168.100.104 kernel: PREFETCH window: d8500000-d85fffff Sep 8 15:02:54 192.168.100.104 kernel: PCI: Bridge: 0000:00:1e.0 Sep 8 15:02:54 192.168.100.104 kernel: IO window: 4000-4fff Sep 8 15:02:54 192.168.100.104 kernel: MEM window: d8300000-d83fffff Sep 8 15:02:54 192.168.100.104 kernel: PREFETCH window: d0000000-d7ffffff Sep 8 15:02:54 192.168.100.104 kernel: GSI 16 sharing vector 0xA0 and IRQ 16 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 15:02:54 192.168.100.104 kernel: GSI 17 sharing vector 0xA8 and IRQ 17 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 15:02:54 192.168.100.104 kernel: GSI 18 sharing vector 0xB0 and IRQ 18 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 15:02:54 192.168.100.104 kernel: NET: Registered protocol family 2 Sep 8 15:02:54 192.168.100.104 kernel: IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) Sep 8 15:02:54 192.168.100.104 kernel: TCP established hash table entries: 262144 (order: 10, 4194304 bytes) Sep 8 15:02:54 192.168.100.104 kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) Sep 8 15:02:54 192.168.100.104 kernel: TCP: Hash tables configured (established 262144 bind 65536) Sep 8 15:02:54 192.168.100.104 kernel: TCP reno registered Sep 8 15:02:54 192.168.100.104 kernel: Simple Boot Flag at 0x38 set to 0x1 Sep 8 15:02:54 192.168.100.104 kernel: audit: initializing netlink socket (disabled) Sep 8 15:02:54 192.168.100.104 kernel: type=2000 audit(1252422136.272:1): initialized Sep 8 15:02:54 192.168.100.104 kernel: VFS: Disk quotas dquot_6.5.1 Sep 8 15:02:54 192.168.100.104 kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Sep 8 15:02:54 192.168.100.104 kernel: Initializing Cryptographic API Sep 8 15:02:54 192.168.100.104 kernel: alg: No test for crc32c (crc32c-generic) Sep 8 15:02:54 192.168.100.104 kernel: ksign: Installing public key data Sep 8 15:02:54 192.168.100.104 kernel: Loading keyring Sep 8 15:02:54 192.168.100.104 kernel: - Added public key 5535842996BF3A42 Sep 8 15:02:54 192.168.100.104 kernel: - User ID: CentOS (Kernel Module GPG key) Sep 8 15:02:54 192.168.100.104 kernel: io scheduler noop registered Sep 8 15:02:54 192.168.100.104 kernel: io scheduler anticipatory registered Sep 8 15:02:54 192.168.100.104 kernel: io scheduler deadline registered Sep 8 15:02:54 192.168.100.104 kernel: io scheduler cfq registered (default) Sep 8 15:02:54 192.168.100.104 kernel: assign_interrupt_mode Found MSI capability Sep 8 15:02:54 192.168.100.104 kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: Processor [CPU0] (supports 8 throttling states) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: Processor [CPU1] (supports 8 throttling states) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: Processor [CPU2] (supports 8 throttling states) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: Processor [CPU3] (supports 8 throttling states) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: Processor [CPU4] (supports 8 throttling states) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: Processor [CPU5] (supports 8 throttling states) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: Processor [CPU6] (supports 8 throttling states) Sep 8 15:02:54 192.168.100.104 kernel: ACPI: Processor [CPU7] (supports 8 throttling states) Sep 8 15:02:54 192.168.100.104 kernel: Real Time Clock Driver v1.12ac Sep 8 15:02:54 192.168.100.104 kernel: Non-volatile memory driver v1.2 Sep 8 15:02:54 192.168.100.104 kernel: Linux agpgart interface v0.101 (c) Dave Jones Sep 8 15:02:54 192.168.100.104 kernel: RAMDISK driver initialized: 16 RAM disks of 26403K size 4096 blocksize Sep 8 15:02:54 192.168.100.104 kernel: Xen virtual console successfully installed as ttyS0 Sep 8 15:02:54 192.168.100.104 kernel: Event-channel device installed. Sep 8 15:02:54 192.168.100.104 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Sep 8 15:02:54 192.168.100.104 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Sep 8 15:02:54 192.168.100.104 kernel: ESB2: IDE controller at PCI slot 0000:00:1f.1 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 15:02:54 192.168.100.104 kernel: ESB2: chipset revision 9 Sep 8 15:02:54 192.168.100.104 kernel: ESB2: not 100% native mode: will probe irqs later Sep 8 15:02:54 192.168.100.104 kernel: ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:pio, hdb:DMA Sep 8 15:02:54 192.168.100.104 kernel: hdb: DVD-ROM UJDA780, ATAPI CD/DVD-ROM drive Sep 8 15:02:54 192.168.100.104 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Sep 8 15:02:54 192.168.100.104 kernel: ide-floppy driver 0.99.newide Sep 8 15:02:54 192.168.100.104 kernel: usbcore: registered new driver hiddev Sep 8 15:02:54 192.168.100.104 kernel: usbcore: registered new driver usbhid Sep 8 15:02:54 192.168.100.104 kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver Sep 8 15:02:54 192.168.100.104 kernel: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12 Sep 8 15:02:54 192.168.100.104 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Sep 8 15:02:54 192.168.100.104 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Sep 8 15:02:54 192.168.100.104 kernel: mice: PS/2 mouse device common for all mice Sep 8 15:02:54 192.168.100.104 kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 Sep 8 15:02:54 192.168.100.104 kernel: md: bitmap version 4.39 Sep 8 15:02:54 192.168.100.104 kernel: TCP bic registered Sep 8 15:02:54 192.168.100.104 kernel: Initializing IPsec netlink socket Sep 8 15:02:54 192.168.100.104 kernel: NET: Registered protocol family 1 Sep 8 15:02:54 192.168.100.104 kernel: NET: Registered protocol family 17 Sep 8 15:02:54 192.168.100.104 kernel: Write protecting the kernel read-only data: 467k Sep 8 15:02:54 192.168.100.104 kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 Sep 8 15:02:54 192.168.100.104 kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation. Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 15:02:54 192.168.100.104 kernel: 0000:05:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 15:02:54 192.168.100.104 kernel: eth0: (PCI Express:2.5GB/s:Width x4) 00:30:48:c5:8d:5a Sep 8 15:02:54 192.168.100.104 kernel: eth0: Intel(R) PRO/1000 Network Connection Sep 8 15:02:54 192.168.100.104 kernel: eth0: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 15:02:54 192.168.100.104 kernel: GSI 19 sharing vector 0xB8 and IRQ 19 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt 0000:05:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 15:02:54 192.168.100.104 kernel: 0000:05:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 15:02:54 192.168.100.104 kernel: eth1: (PCI Express:2.5GB/s:Width x4) 00:30:48:c5:8d:5b Sep 8 15:02:54 192.168.100.104 kernel: eth1: Intel(R) PRO/1000 Network Connection Sep 8 15:02:54 192.168.100.104 kernel: eth1: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt 0000:08:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 15:02:54 192.168.100.104 kernel: 0000:08:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 15:02:54 192.168.100.104 kernel: eth2: (PCI Express:2.5GB/s:Width x4) 00:15:17:b9:91:90 Sep 8 15:02:54 192.168.100.104 kernel: eth2: Intel(R) PRO/1000 Network Connection Sep 8 15:02:54 192.168.100.104 kernel: eth2: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt 0000:08:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 15:02:54 192.168.100.104 kernel: 0000:08:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 15:02:54 192.168.100.104 kernel: eth3: (PCI Express:2.5GB/s:Width x4) 00:15:17:b9:91:91 Sep 8 15:02:54 192.168.100.104 kernel: eth3: Intel(R) PRO/1000 Network Connection Sep 8 15:02:54 192.168.100.104 kernel: eth3: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 15:02:54 192.168.100.104 kernel: FS-Cache: Loaded Sep 8 15:02:54 192.168.100.104 kernel: eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 8 15:02:54 192.168.100.104 kernel: NET: Registered protocol family 10 Sep 8 15:02:54 192.168.100.104 kernel: lo: Disabled Privacy Extensions Sep 8 15:02:54 192.168.100.104 kernel: IPv6 over IPv4 tunneling driver Sep 8 15:02:54 192.168.100.104 kernel: SELinux: Disabled at runtime. Sep 8 15:02:54 192.168.100.104 kernel: type=1404 audit(1252422145.832:2): selinux=0 auid=4294967295 ses=4294967295 Sep 8 15:02:54 192.168.100.104 kernel: hdb: ATAPI 24X DVD-ROM drive, 2048kB Cache, UDMA(33) Sep 8 15:02:54 192.168.100.104 kernel: Uniform CD-ROM driver Revision: 3.20 Sep 8 15:02:54 192.168.100.104 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Sep 8 15:02:54 192.168.100.104 kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Sep 8 15:02:54 192.168.100.104 kernel: 8250_pnp: Unknown symbol serial8250_unregister_port Sep 8 15:02:54 192.168.100.104 kernel: 8250_pnp: Unknown symbol serial8250_register_port Sep 8 15:02:54 192.168.100.104 kernel: USB Universal Host Controller Interface driver v3.0 Sep 8 15:02:54 192.168.100.104 kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 15:02:57 192.168.100.104 kernel: eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 8 15:02:57 192.168.100.104 kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready Sep 8 15:02:57 192.168.100.104 iscsid: connect failed (113) Sep 8 15:02:58 192.168.100.104 iscsid: connect failed (113) Sep 8 15:02:58 192.168.100.104 kernel: eth2: Link is Down Sep 8 15:03:01 192.168.100.104 kernel: eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 8 15:03:03 192.168.100.104 iscsid: connect failed (113) Sep 8 15:03:07 192.168.100.104 iscsid: connect failed (113) Sep 8 15:03:07 192.168.100.104 kernel: scsi2 : iSCSI Initiator over TCP/IP Sep 8 15:03:07 192.168.100.104 kernel: scsi3 : iSCSI Initiator over TCP/IP Sep 8 15:03:08 192.168.100.104 kernel: Vendor: Promise Model: VTrak M610i Rev: 021C Sep 8 15:03:08 192.168.100.104 kernel: Type: Direct-Access ANSI SCSI revision: 05 Sep 8 15:03:08 192.168.100.104 kernel: Vendor: Promise Model: VTrak M610i Rev: 021C Sep 8 15:03:08 192.168.100.104 kernel: Type: Direct-Access ANSI SCSI revision: 05 Sep 8 15:03:08 192.168.100.104 rpc.statd[3279]: Version 1.0.9 Starting Sep 8 15:03:08 192.168.100.104 kernel: scsi 2:0:0:0: Attached scsi generic sg0 type 0 Sep 8 15:03:08 192.168.100.104 kernel: scsi 3:0:0:0: Attached scsi generic sg1 type 0 Sep 8 15:03:08 192.168.100.104 kernel: sda : very big device. try to use READ CAPACITY(16). Sep 8 15:03:08 192.168.100.104 kernel: SCSI device sda: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 15:03:08 192.168.100.104 kernel: sda: Write Protect is off Sep 8 15:03:08 192.168.100.104 kernel: SCSI device sda: drive cache: write back w/ FUA Sep 8 15:03:08 192.168.100.104 kernel: sda : very big device. try to use READ CAPACITY(16). Sep 8 15:03:08 192.168.100.104 kernel: SCSI device sda: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 15:03:08 192.168.100.104 kernel: sda: Write Protect is off Sep 8 15:03:08 192.168.100.104 kernel: SCSI device sda: drive cache: write back w/ FUA Sep 8 15:03:08 192.168.100.104 kernel: sda: sda1 Sep 8 15:03:08 192.168.100.104 kernel: sd 2:0:0:0: Attached scsi disk sda Sep 8 15:03:08 192.168.100.104 multipathd: sda: add path (uevent) Sep 8 15:03:08 192.168.100.104 kernel: sdb : very big device. try to use READ CAPACITY(16). Sep 8 15:03:08 192.168.100.104 kernel: SCSI device sdb: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 15:03:08 192.168.100.104 kernel: sdb: Write Protect is off Sep 8 15:03:08 192.168.100.104 kernel: SCSI device sdb: drive cache: write back w/ FUA Sep 8 15:03:08 192.168.100.104 kernel: sdb : very big device. try to use READ CAPACITY(16). Sep 8 15:03:08 192.168.100.104 kernel: SCSI device sdb: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 15:03:08 192.168.100.104 kernel: sdb: Write Protect is off Sep 8 15:03:08 192.168.100.104 kernel: SCSI device sdb: drive cache: write back w/ FUA Sep 8 15:03:08 192.168.100.104 iscsid: received iferror -38 Sep 8 15:03:08 192.168.100.104 iscsid: connection1:0 is operational now Sep 8 15:03:08 192.168.100.104 iscsid: received iferror -38 Sep 8 15:03:08 192.168.100.104 iscsid: connection2:0 is operational now Sep 8 15:03:08 192.168.100.104 kernel: sdb: sdb1 Sep 8 15:03:08 192.168.100.104 kernel: sd 3:0:0:0: Attached scsi disk sdb Sep 8 15:03:09 192.168.100.104 kernel: device-mapper: multipath round-robin: version 1.0.0 loaded Sep 8 15:03:09 192.168.100.104 multipathd: xen: failed in domap for addition of new path sda Sep 8 15:03:09 192.168.100.104 multipathd: uevent trigger error Sep 8 15:03:09 192.168.100.104 multipathd: sdb: add path (uevent) Sep 8 15:03:09 192.168.100.104 multipathd: xen: failed in domap for addition of new path sdb Sep 8 15:03:09 192.168.100.104 multipathd: uevent trigger error Sep 8 15:03:09 192.168.100.104 multipathd: dm-0: add map (uevent) Sep 8 15:03:09 192.168.100.104 multipathd: xen: event checker started Sep 8 15:03:09 192.168.100.104 multipathd: dm-0: add map (uevent) Sep 8 15:03:09 192.168.100.104 multipathd: dm-0: devmap already registered Sep 8 15:03:09 192.168.100.104 multipathd: dm-1: add map (uevent) Sep 8 15:03:09 192.168.100.104 kernel: Bridge firewalling registered Sep 8 15:03:09 192.168.100.104 kernel: xenbr1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. Sep 8 15:03:09 192.168.100.104 kernel: device vif0.0 entered promiscuous mode Sep 8 15:03:09 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:03:09 192.168.100.104 kernel: xenbr1: port 1(vif0.0) entering forwarding state Sep 8 15:03:10 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): peth1: link is not ready Sep 8 15:03:11 192.168.100.104 kernel: peth1: Link is Up 100 Mbps Full Duplex, Flow Control: None Sep 8 15:03:11 192.168.100.104 kernel: peth1: 10/100 speed: disabling TSO Sep 8 15:03:11 192.168.100.104 kernel: ADDRCONF(NETDEV_CHANGE): peth1: link becomes ready Sep 8 15:03:12 192.168.100.104 kernel: device peth1 entered promiscuous mode Sep 8 15:03:12 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:03:12 192.168.100.104 kernel: xenbr1: port 2(peth1) entering forwarding state Sep 8 15:03:12 192.168.100.104 kernel: DLM (built Apr 1 2009 09:54:52) installed Sep 8 15:03:12 192.168.100.104 kernel: GFS2 (built Apr 1 2009 09:56:12) installed Sep 8 15:03:12 192.168.100.104 kernel: Lock_DLM (built Apr 1 2009 09:56:21) installed Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Starting ccsd 2.0.98: Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Built: Jan 21 2009 05:40:28 Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Copyright (C) Red Hat, Inc. 2004 All rights reserved. Sep 8 15:03:12 192.168.100.104 ccsd[4072]: cluster.conf (cluster name = xencluster1, version = 6) found. Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Remote copy of cluster.conf is from quorate node. Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Local version # : 6 Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Remote version #: 6 Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Remote copy of cluster.conf is from quorate node. Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Local version # : 6 Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Remote version #: 6 Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Remote copy of cluster.conf is from quorate node. Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Local version # : 6 Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Remote version #: 6 Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Remote copy of cluster.conf is from quorate node. Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Local version # : 6 Sep 8 15:03:12 192.168.100.104 ccsd[4072]: Remote version #: 6 Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] AIS Executive Service RELEASE 'subrev 1358 version 0.80.3' Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Copyright (C) 2002-2006 MontaVista Software, Inc and contributors. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Copyright (C) 2006 Red Hat, Inc. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] AIS Executive Service: started and ready to provide service. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] openais component openais_cpg loaded. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Registering service handler 'openais cluster closed process group service v1.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] openais component openais_cfg loaded. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Registering service handler 'openais configuration service' Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] openais component openais_msg loaded. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Registering service handler 'openais message service B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] openais component openais_lck loaded. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Registering service handler 'openais distributed locking service B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] openais component openais_evt loaded. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Registering service handler 'openais event service B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] openais component openais_ckpt loaded. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Registering service handler 'openais checkpoint service B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] openais component openais_amf loaded. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Registering service handler 'openais availability management framework B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] openais component openais_clm loaded. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Registering service handler 'openais cluster membership service B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] openais component openais_evs loaded. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Registering service handler 'openais extended virtual synchrony service' Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] openais component openais_cman loaded. Sep 8 15:03:12 192.168.100.104 openais[4094]: [MAIN ] Registering service handler 'openais CMAN membership service 2.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] Token Timeout (10000 ms) retransmit timeout (495 ms) Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] token hold (386 ms) retransmits before loss (20 retrans) Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] join (60 ms) send_join (0 ms) consensus (4800 ms) merge (200 ms) Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] downcheck (1000 ms) fail to recv const (50 msgs) Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] seqno unchanged const (30 rotations) Maximum network MTU 1500 Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] window size per rotation (50 messages) maximum messages per rotation (17 messages) Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] send threads (0 threads) Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] RRP token expired timeout (495 ms) Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] RRP token problem counter (2000 ms) Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] RRP threshold (10 problem count) Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] RRP mode set to none. Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] heartbeat_failures_allowed (0) Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] max_network_delay (50 ms) Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] HeartBeat is Disabled. To enable set heartbeat_failures_allowed > 0 Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] Receive multicast socket recv buffer size (262142 bytes). Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] Transmit multicast socket send buffer size (262142 bytes). Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] The network interface [10.103.103.104] is now up. Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] Created or loaded sequence id 116.10.103.103.104 for this ring. Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] entering GATHER state from 15. Sep 8 15:03:12 192.168.100.104 openais[4094]: [SERV ] Initialising service handler 'openais extended virtual synchrony service' Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] entering GATHER state from 11. Sep 8 15:03:12 192.168.100.104 openais[4094]: [SERV ] Initialising service handler 'openais cluster membership service B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [SERV ] Initialising service handler 'openais availability management framework B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [SERV ] Initialising service handler 'openais checkpoint service B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [SERV ] Initialising service handler 'openais event service B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [SERV ] Initialising service handler 'openais distributed locking service B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [SERV ] Initialising service handler 'openais message service B.01.01' Sep 8 15:03:12 192.168.100.104 openais[4094]: [SERV ] Initialising service handler 'openais configuration service' Sep 8 15:03:12 192.168.100.104 openais[4094]: [SERV ] Initialising service handler 'openais cluster closed process group service v1.01' Sep 8 15:03:12 192.168.100.105 openais[4052]: [TOTEM] entering GATHER state from 11. Sep 8 15:03:12 192.168.100.104 openais[4094]: [SERV ] Initialising service handler 'openais CMAN membership service 2.01' Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] entering GATHER state from 11. Sep 8 15:03:12 192.168.100.104 openais[4094]: [CMAN ] CMAN 2.0.98 (built Jan 21 2009 05:40:32) started Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] entering GATHER state from 11. Sep 8 15:03:12 192.168.100.104 openais[4094]: [SYNC ] Not using a virtual synchrony filter. Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] Creating commit token because I am the rep. Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] Saving state aru 0 high seq received 0 Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] Storing new sequence id for ring 78 Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] entering COMMIT state. Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] entering RECOVERY state. Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] position [0] member 10.103.103.104: Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 116 rep 10.103.103.104 Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] aru 0 high delivered 0 received flag 1 Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] Sending initial ORF token Sep 8 15:03:12 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:12 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 15:03:12 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 15:03:12 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 15:03:12 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:12 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 15:03:12 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:12 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 15:03:12 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 15:03:12 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:12 192.168.100.104 openais[4094]: [SYNC ] This node is within the primary component and will provide service. Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] entering OPERATIONAL state. Sep 8 15:03:12 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] entering GATHER state from 11. Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] Creating commit token because I am the rep. Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] Saving state aru 4b high seq received 4b Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] Storing new sequence id for ring 7c Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] entering COMMIT state. Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] Saving state aru 4b high seq received 4b Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] Storing new sequence id for ring 7c Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] entering COMMIT state. Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] Saving state aru 4b high seq received 4b Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] Storing new sequence id for ring 7c Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] entering COMMIT state. Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] Saving state aru a high seq received a Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] Storing new sequence id for ring 7c Sep 8 15:03:12 192.168.100.104 openais[4094]: [TOTEM] entering COMMIT state. Sep 8 15:03:12 192.168.100.105 openais[4052]: [TOTEM] Saving state aru 4b high seq received 4b Sep 8 15:03:12 192.168.100.105 openais[4052]: [TOTEM] Storing new sequence id for ring 7c Sep 8 15:03:12 192.168.100.105 openais[4052]: [TOTEM] entering COMMIT state. Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] entering RECOVERY state. Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] position [0] member 10.103.103.101: Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] position [1] member 10.103.103.102: Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] position [2] member 10.103.103.103: Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] position [3] member 10.103.103.104: Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 120 rep 10.103.103.104 Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] aru a high delivered a received flag 1 Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] position [4] member 10.103.103.105: Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] entering RECOVERY state. Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] position [0] member 10.103.103.101: Sep 8 15:03:12 192.168.100.101 openais[3853]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] position [1] member 10.103.103.102: Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] position [2] member 10.103.103.103: Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] entering RECOVERY state. Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] position [0] member 10.103.103.101: Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] position [1] member 10.103.103.102: Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] position [3] member 10.103.103.104: Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 120 rep 10.103.103.104 Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] position [2] member 10.103.103.103: Sep 8 15:03:12 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:12 192.168.100.102 openais[12690]: [TOTEM] aru a high delivered a received flag 1 Sep 8 15:03:13 192.168.100.102 openais[12690]: [TOTEM] position [4] member 10.103.103.105: Sep 8 15:03:13 192.168.100.103 openais[3851]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:13 192.168.100.103 openais[3851]: [TOTEM] position [3] member 10.103.103.104: Sep 8 15:03:13 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 120 rep 10.103.103.104 Sep 8 15:03:13 192.168.100.102 openais[12690]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:13 192.168.100.103 openais[3851]: [TOTEM] aru a high delivered a received flag 1 Sep 8 15:03:13 192.168.100.102 openais[12690]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:13 192.168.100.103 openais[3851]: [TOTEM] position [4] member 10.103.103.105: Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] entering RECOVERY state. Sep 8 15:03:13 192.168.100.103 openais[3851]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:13 192.168.100.102 openais[12690]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] position [0] member 10.103.103.101: Sep 8 15:03:13 192.168.100.103 openais[3851]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:13 192.168.100.103 openais[3851]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] position [1] member 10.103.103.102: Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] position [2] member 10.103.103.103: Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] entering RECOVERY state. Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] position [0] member 10.103.103.101: Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] position [3] member 10.103.103.104: Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 120 rep 10.103.103.104 Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] aru a high delivered a received flag 1 Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] position [4] member 10.103.103.105: Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] position [1] member 10.103.103.102: Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] position [2] member 10.103.103.103: Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:13 192.168.100.101 openais[3853]: [TOTEM] Sending initial ORF token Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] position [3] member 10.103.103.104: Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 120 rep 10.103.103.104 Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] aru a high delivered a received flag 1 Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] position [4] member 10.103.103.105: Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 120 rep 10.103.103.101 Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] aru 4b high delivered 4b received flag 1 Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] New Configuration: Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] Members Left: Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] New Configuration: Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] Members Joined: Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] Members Left: Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] New Configuration: Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] Members Joined: Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] New Configuration: Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] Members Left: Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] Members Joined: Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 15:03:13 192.168.100.103 openais[3851]: [SYNC ] This node is within the primary component and will provide service. Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] Members Left: Sep 8 15:03:13 192.168.100.103 openais[3851]: [TOTEM] entering OPERATIONAL state. Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] Members Joined: Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:03:13 192.168.100.102 openais[12690]: [SYNC ] This node is within the primary component and will provide service. Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:03:13 192.168.100.102 openais[12690]: [TOTEM] entering OPERATIONAL state. Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:03:13 192.168.100.104 openais[4094]: [SYNC ] This node is within the primary component and will provide service. Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 15:03:13 192.168.100.104 openais[4094]: [TOTEM] entering OPERATIONAL state. Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:13 192.168.100.105 openais[4052]: [SYNC ] This node is within the primary component and will provide service. Sep 8 15:03:13 192.168.100.105 openais[4052]: [TOTEM] entering OPERATIONAL state. Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 15:03:13 192.168.100.101 openais[3853]: [SYNC ] This node is within the primary component and will provide service. Sep 8 15:03:13 192.168.100.101 openais[3853]: [TOTEM] entering OPERATIONAL state. Sep 8 15:03:13 192.168.100.104 openais[4094]: [CMAN ] quorum regained, resuming activity Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 15:03:13 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 15:03:13 192.168.100.103 openais[3851]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 15:03:13 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 15:03:13 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 15:03:13 192.168.100.102 openais[12690]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 15:03:13 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 3 Sep 8 15:03:13 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 3 Sep 8 15:03:13 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 3 Sep 8 15:03:13 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 3 Sep 8 15:03:13 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 3 Sep 8 15:03:13 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 5 Sep 8 15:03:13 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 5 Sep 8 15:03:13 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 5 Sep 8 15:03:13 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 1 Sep 8 15:03:13 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 5 Sep 8 15:03:13 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 5 Sep 8 15:03:13 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 1 Sep 8 15:03:13 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 1 Sep 8 15:03:13 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 1 Sep 8 15:03:13 192.168.100.102 openais[12690]: [CPG ] got joinlist message from node 2 Sep 8 15:03:13 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 1 Sep 8 15:03:13 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 2 Sep 8 15:03:13 192.168.100.103 openais[3851]: [CPG ] got joinlist message from node 2 Sep 8 15:03:13 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 2 Sep 8 15:03:13 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 2 Sep 8 15:03:13 192.168.100.104 ccsd[4072]: Initial status:: Quorate Sep 8 15:03:16 pxe mountd[2162]: authenticated mount request from 192.168.100.104:995 for /opt/xenxml (/opt/xenxml) Sep 8 15:03:16 192.168.100.104 kernel: GFS2: fsid=: Trying to join cluster "lock_dlm", "xencluster1:xenclusterfs1" Sep 8 15:03:16 192.168.100.104 kernel: dlm: Using TCP for communications Sep 8 15:03:16 192.168.100.104 kernel: dlm: connecting to 1 Sep 8 15:03:16 192.168.100.103 kernel: dlm: connecting to 4 Sep 8 15:03:16 192.168.100.105 kernel: dlm: connecting to 4 Sep 8 15:03:16 192.168.100.101 kernel: dlm: connecting to 4 Sep 8 15:03:16 192.168.100.104 kernel: dlm: got connection from 5 Sep 8 15:03:16 192.168.100.102 kernel: dlm: connecting to 4 Sep 8 15:03:16 192.168.100.104 kernel: dlm: got connection from 3 Sep 8 15:03:16 192.168.100.104 kernel: dlm: got connection from 1 Sep 8 15:03:16 192.168.100.104 kernel: dlm: got connection from 2 Sep 8 15:03:16 192.168.100.101 kernel: dlm: got connection from 4 Sep 8 15:03:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: Joined cluster. Now mounting FS... Sep 8 15:03:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=0, already locked for use Sep 8 15:03:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=0: Looking at journal... Sep 8 15:03:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=0: Acquiring the transaction lock... Sep 8 15:03:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=0: Replaying journal... Sep 8 15:03:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=0: Replayed 116 of 118 blocks Sep 8 15:03:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=0: Found 1 revoke tags Sep 8 15:03:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=0: Journal replayed in 1s Sep 8 15:03:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=0: Done Sep 8 15:03:18 192.168.100.104 gpm[4364]: *** info [startup.c(95)]: Sep 8 15:03:18 192.168.100.104 gpm[4364]: Started gpm successfully. Entered daemon mode. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70). Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Successfully dropped root privileges. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: avahi-daemon 0.6.16 starting up. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Successfully called chroot(). Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Successfully dropped remaining capabilities. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Loading service file /services/sftp-ssh.service. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: New relevant interface eth3.IPv6 for mDNS. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface eth3.IPv6 with address fe80::215:17ff:feb9:9191. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: New relevant interface eth3.IPv4 for mDNS. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface eth3.IPv4 with address 10.103.103.104. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: New relevant interface eth2.IPv6 for mDNS. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface eth2.IPv6 with address fe80::215:17ff:feb9:9190. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: New relevant interface eth2.IPv4 for mDNS. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.102.102.104. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: New relevant interface eth0.IPv6 for mDNS. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::230:48ff:fec5:8d5a. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: New relevant interface eth0.IPv4 for mDNS. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.100.104. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Network interface enumeration completed. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::215:17ff:feb9:9191 on eth3. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Registering new address record for 10.103.103.104 on eth3. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::215:17ff:feb9:9190 on eth2. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Registering new address record for 10.102.102.104 on eth2. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::230:48ff:fec5:8d5a on eth0. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Registering new address record for 192.168.100.104 on eth0. Sep 8 15:03:20 192.168.100.104 avahi-daemon[4605]: Registering HINFO record with values 'X86_64'/'LINUX'. Sep 8 15:03:21 192.168.100.104 avahi-daemon[4605]: Server startup complete. Host name is xen4.local. Local service cookie is 3007088798. Sep 8 15:03:22 192.168.100.104 avahi-daemon[4605]: Service "SFTP File Transfer on xen4" (/services/sftp-ssh.service) successfully established. Sep 8 15:03:23 192.168.100.104 xenstored: Checking store ... Sep 8 15:03:23 192.168.100.104 xenstored: Checking store complete. Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 14 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 271 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 272 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 273 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 18 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 277 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 278 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 279 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 19 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 274 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 275 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 276 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 268 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 269 Sep 8 15:03:23 192.168.100.104 kernel: Breaking affinity for irq 270 Sep 8 15:03:24 192.168.100.104 smartd[4866]: smartd version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Sep 8 15:03:24 192.168.100.104 smartd[4866]: Home page is http://smartmontools.sourceforge.net/ Sep 8 15:03:24 192.168.100.104 smartd[4866]: Opened configuration file /etc/smartd.conf Sep 8 15:03:24 192.168.100.104 smartd[4866]: Configuration file /etc/smartd.conf parsed. Sep 8 15:03:24 192.168.100.104 smartd[4866]: Device: /dev/sda, opened Sep 8 15:03:24 192.168.100.104 smartd[4866]: Device: /dev/sda, not ATA, no IDENTIFY DEVICE Structure Sep 8 15:03:24 192.168.100.104 smartd[4866]: Unable to register ATA device /dev/sda at line 32 of file /etc/smartd.conf Sep 8 15:03:24 192.168.100.104 smartd[4866]: Device /dev/sda not available Sep 8 15:03:24 192.168.100.104 smartd[4866]: Monitoring 0 ATA and 0 SCSI devices Sep 8 15:03:24 192.168.100.104 smartd[4868]: smartd has fork()ed into background mode. New PID=4868. Sep 8 15:03:58 192.168.100.105 kernel: device tap7 entered promiscuous mode Sep 8 15:03:58 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:03:58 192.168.100.105 kernel: xenbr1: port 17(tap7) entering forwarding state Sep 8 15:03:59 192.168.100.105 kernel: device vif8.0 entered promiscuous mode Sep 8 15:03:59 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif8.0: link is not ready Sep 8 15:04:00 192.168.100.105 avahi-daemon[4535]: New relevant interface tap7.IPv6 for mDNS. Sep 8 15:04:00 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap7.IPv6 with address fe80::2490:39ff:fec4:4b52. Sep 8 15:04:00 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::2490:39ff:fec4:4b52 on tap7. Sep 8 15:04:16 192.168.100.105 kernel: device tap8 entered promiscuous mode Sep 8 15:04:16 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:04:16 192.168.100.105 kernel: xenbr1: port 19(tap8) entering forwarding state Sep 8 15:04:16 192.168.100.105 kernel: device vif9.0 entered promiscuous mode Sep 8 15:04:16 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif9.0: link is not ready Sep 8 15:04:17 192.168.100.105 avahi-daemon[4535]: New relevant interface tap8.IPv6 for mDNS. Sep 8 15:04:17 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap8.IPv6 with address fe80::e47a:d3ff:fe46:1b56. Sep 8 15:04:17 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::e47a:d3ff:fe46:1b56 on tap8. Sep 8 15:04:28 192.168.100.105 kernel: xenbr1: port 4(vif1.0) entering disabled state Sep 8 15:04:28 192.168.100.105 kernel: device vif1.0 left promiscuous mode Sep 8 15:04:28 192.168.100.105 kernel: xenbr1: port 4(vif1.0) entering disabled state Sep 8 15:04:28 192.168.100.105 avahi-daemon[4535]: Interface tap0.IPv6 no longer relevant for mDNS. Sep 8 15:04:28 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap0.IPv6 with address fe80::34e8:94ff:fe4e:ab32. Sep 8 15:04:28 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::34e8:94ff:fe4e:ab32 on tap0. Sep 8 15:04:28 192.168.100.105 kernel: xenbr1: port 3(tap0) entering disabled state Sep 8 15:04:28 192.168.100.105 kernel: device tap0 left promiscuous mode Sep 8 15:04:28 192.168.100.105 kernel: xenbr1: port 3(tap0) entering disabled state Sep 8 15:04:28 192.168.100.105 kernel: device tap9 entered promiscuous mode Sep 8 15:04:28 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:04:28 192.168.100.105 kernel: xenbr1: port 3(tap9) entering forwarding state Sep 8 15:04:28 192.168.100.105 kernel: device vif10.0 entered promiscuous mode Sep 8 15:04:28 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif10.0: link is not ready Sep 8 15:04:30 192.168.100.105 avahi-daemon[4535]: New relevant interface tap9.IPv6 for mDNS. Sep 8 15:04:30 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap9.IPv6 with address fe80::9c24:c1ff:fef8:67d. Sep 8 15:04:30 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::9c24:c1ff:fef8:67d on tap9. Sep 8 15:04:39 192.168.100.105 kernel: device tap0 entered promiscuous mode Sep 8 15:04:39 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:04:39 192.168.100.105 kernel: xenbr1: port 21(tap0) entering forwarding state Sep 8 15:04:40 192.168.100.105 kernel: device vif11.0 entered promiscuous mode Sep 8 15:04:40 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif11.0: link is not ready Sep 8 15:04:41 192.168.100.105 avahi-daemon[4535]: New relevant interface tap0.IPv6 for mDNS. Sep 8 15:04:41 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap0.IPv6 with address fe80::b477:10ff:fecf:bb9b. Sep 8 15:04:41 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::b477:10ff:fecf:bb9b on tap0. Sep 8 15:04:54 192.168.100.105 kernel: device tap10 entered promiscuous mode Sep 8 15:04:54 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:04:54 192.168.100.105 kernel: xenbr1: port 23(tap10) entering forwarding state Sep 8 15:04:54 192.168.100.105 kernel: device vif12.0 entered promiscuous mode Sep 8 15:04:54 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif12.0: link is not ready Sep 8 15:04:55 192.168.100.105 avahi-daemon[4535]: New relevant interface tap10.IPv6 for mDNS. Sep 8 15:04:55 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap10.IPv6 with address fe80::d49c:28ff:fe95:ce8c. Sep 8 15:04:55 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::d49c:28ff:fe95:ce8c on tap10. Sep 8 15:05:07 192.168.100.102 kernel: xenbr1: port 36(vif33.0) entering disabled state Sep 8 15:05:07 192.168.100.102 kernel: device vif33.0 left promiscuous mode Sep 8 15:05:07 192.168.100.102 kernel: xenbr1: port 36(vif33.0) entering disabled state Sep 8 15:05:07 192.168.100.102 avahi-daemon[4486]: Interface tap16.IPv6 no longer relevant for mDNS. Sep 8 15:05:07 192.168.100.102 avahi-daemon[4486]: Leaving mDNS multicast group on interface tap16.IPv6 with address fe80::1c90:55ff:fe96:2f91. Sep 8 15:05:07 192.168.100.102 avahi-daemon[4486]: Withdrawing address record for fe80::1c90:55ff:fe96:2f91 on tap16. Sep 8 15:05:07 192.168.100.102 kernel: xenbr1: port 35(tap16) entering disabled state Sep 8 15:05:07 192.168.100.102 kernel: device tap16 left promiscuous mode Sep 8 15:05:07 192.168.100.102 kernel: xenbr1: port 35(tap16) entering disabled state Sep 8 15:05:10 192.168.100.105 kernel: device tap11 entered promiscuous mode Sep 8 15:05:10 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:05:10 192.168.100.105 kernel: xenbr1: port 25(tap11) entering forwarding state Sep 8 15:05:10 192.168.100.105 kernel: device vif13.0 entered promiscuous mode Sep 8 15:05:10 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif13.0: link is not ready Sep 8 15:05:11 192.168.100.105 avahi-daemon[4535]: New relevant interface tap11.IPv6 for mDNS. Sep 8 15:05:11 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap11.IPv6 with address fe80::7496:e3ff:fea0:165c. Sep 8 15:05:11 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::7496:e3ff:fea0:165c on tap11. Sep 8 15:05:17 192.168.100.104 kernel: tun: Universal TUN/TAP device driver, 1.6 Sep 8 15:05:17 192.168.100.104 kernel: tun: (C) 1999-2004 Max Krasnyansky Sep 8 15:05:17 192.168.100.104 kernel: device tap0 entered promiscuous mode Sep 8 15:05:17 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:05:17 192.168.100.104 kernel: xenbr1: port 3(tap0) entering forwarding state Sep 8 15:05:17 192.168.100.104 kernel: device vif1.0 entered promiscuous mode Sep 8 15:05:17 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif1.0: link is not ready Sep 8 15:05:17 192.168.100.104 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team Sep 8 15:05:17 192.168.100.104 kernel: loop: loaded (max 150 devices) Sep 8 15:05:19 192.168.100.104 avahi-daemon[4605]: New relevant interface tap0.IPv6 for mDNS. Sep 8 15:05:19 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap0.IPv6 with address fe80::10d7:fbff:fe87:9b1d. Sep 8 15:05:19 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::10d7:fbff:fe87:9b1d on tap0. Sep 8 15:05:25 192.168.100.105 kernel: device tap12 entered promiscuous mode Sep 8 15:05:25 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:05:25 192.168.100.105 kernel: xenbr1: port 27(tap12) entering forwarding state Sep 8 15:05:26 192.168.100.105 kernel: device vif14.0 entered promiscuous mode Sep 8 15:05:26 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif14.0: link is not ready Sep 8 15:05:27 192.168.100.105 avahi-daemon[4535]: New relevant interface tap12.IPv6 for mDNS. Sep 8 15:05:27 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap12.IPv6 with address fe80::68b5:fff:fee5:1bf. Sep 8 15:05:27 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::68b5:fff:fee5:1bf on tap12. Sep 8 15:06:46 192.168.100.102 kernel: xenbr1: port 38(vif34.0) entering disabled state Sep 8 15:06:47 192.168.100.102 kernel: device vif34.0 left promiscuous mode Sep 8 15:06:47 192.168.100.102 kernel: xenbr1: port 38(vif34.0) entering disabled state Sep 8 15:06:47 192.168.100.102 avahi-daemon[4486]: Interface tap17.IPv6 no longer relevant for mDNS. Sep 8 15:06:47 192.168.100.102 avahi-daemon[4486]: Leaving mDNS multicast group on interface tap17.IPv6 with address fe80::fce9:3aff:fe0f:5685. Sep 8 15:06:47 192.168.100.102 avahi-daemon[4486]: Withdrawing address record for fe80::fce9:3aff:fe0f:5685 on tap17. Sep 8 15:06:47 192.168.100.102 kernel: xenbr1: port 37(tap17) entering disabled state Sep 8 15:06:47 192.168.100.102 kernel: device tap17 left promiscuous mode Sep 8 15:06:47 192.168.100.102 kernel: xenbr1: port 37(tap17) entering disabled state Sep 8 15:06:47 192.168.100.102 kernel: device tap16 entered promiscuous mode Sep 8 15:06:47 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 15:06:47 192.168.100.102 kernel: xenbr1: port 35(tap16) entering forwarding state Sep 8 15:06:48 192.168.100.102 kernel: device vif35.0 entered promiscuous mode Sep 8 15:06:48 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): vif35.0: link is not ready Sep 8 15:06:49 192.168.100.102 avahi-daemon[4486]: New relevant interface tap16.IPv6 for mDNS. Sep 8 15:06:49 192.168.100.102 avahi-daemon[4486]: Joining mDNS multicast group on interface tap16.IPv6 with address fe80::3cb4:56ff:fe48:c2a9. Sep 8 15:06:49 192.168.100.102 avahi-daemon[4486]: Registering new address record for fe80::3cb4:56ff:fe48:c2a9 on tap16. Sep 8 15:07:12 192.168.100.105 kernel: device tap13 entered promiscuous mode Sep 8 15:07:12 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:07:12 192.168.100.105 kernel: xenbr1: port 29(tap13) entering forwarding state Sep 8 15:07:13 192.168.100.105 kernel: device vif15.0 entered promiscuous mode Sep 8 15:07:13 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif15.0: link is not ready Sep 8 15:07:14 192.168.100.105 avahi-daemon[4535]: New relevant interface tap13.IPv6 for mDNS. Sep 8 15:07:14 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap13.IPv6 with address fe80::9017:c2ff:fee8:d37. Sep 8 15:07:14 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::9017:c2ff:fee8:d37 on tap13. Sep 8 15:09:07 192.168.100.105 kernel: device tap14 entered promiscuous mode Sep 8 15:09:07 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:09:07 192.168.100.105 kernel: xenbr1: port 31(tap14) entering forwarding state Sep 8 15:09:07 192.168.100.105 kernel: device vif16.0 entered promiscuous mode Sep 8 15:09:07 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif16.0: link is not ready Sep 8 15:09:08 192.168.100.105 avahi-daemon[4535]: New relevant interface tap14.IPv6 for mDNS. Sep 8 15:09:08 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap14.IPv6 with address fe80::45f:e9ff:fed4:e37e. Sep 8 15:09:08 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::45f:e9ff:fed4:e37e on tap14. Sep 8 15:09:30 192.168.100.105 kernel: device tap15 entered promiscuous mode Sep 8 15:09:30 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:09:30 192.168.100.105 kernel: xenbr1: port 33(tap15) entering forwarding state Sep 8 15:09:31 192.168.100.105 kernel: device vif17.0 entered promiscuous mode Sep 8 15:09:31 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif17.0: link is not ready Sep 8 15:09:32 192.168.100.105 avahi-daemon[4535]: New relevant interface tap15.IPv6 for mDNS. Sep 8 15:09:32 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap15.IPv6 with address fe80::248a:ecff:fe34:66d8. Sep 8 15:09:32 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::248a:ecff:fe34:66d8 on tap15. Sep 8 15:09:46 192.168.100.105 kernel: device tap16 entered promiscuous mode Sep 8 15:09:46 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:09:46 192.168.100.105 kernel: xenbr1: port 35(tap16) entering forwarding state Sep 8 15:09:47 192.168.100.105 kernel: device vif18.0 entered promiscuous mode Sep 8 15:09:47 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif18.0: link is not ready Sep 8 15:09:48 192.168.100.105 avahi-daemon[4535]: New relevant interface tap16.IPv6 for mDNS. Sep 8 15:09:48 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap16.IPv6 with address fe80::34aa:66ff:fe36:f559. Sep 8 15:09:48 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::34aa:66ff:fe36:f559 on tap16. Sep 8 15:10:00 192.168.100.105 kernel: device tap17 entered promiscuous mode Sep 8 15:10:00 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:10:00 192.168.100.105 kernel: xenbr1: port 37(tap17) entering forwarding state Sep 8 15:10:00 192.168.100.105 kernel: device vif19.0 entered promiscuous mode Sep 8 15:10:00 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif19.0: link is not ready Sep 8 15:10:01 192.168.100.105 avahi-daemon[4535]: New relevant interface tap17.IPv6 for mDNS. Sep 8 15:10:01 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap17.IPv6 with address fe80::3083:3cff:fe93:f01c. Sep 8 15:10:01 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::3083:3cff:fe93:f01c on tap17. Sep 8 15:10:11 192.168.100.104 kernel: device tap1 entered promiscuous mode Sep 8 15:10:11 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:10:11 192.168.100.104 kernel: xenbr1: port 5(tap1) entering forwarding state Sep 8 15:10:11 192.168.100.104 kernel: device vif2.0 entered promiscuous mode Sep 8 15:10:11 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif2.0: link is not ready Sep 8 15:10:12 192.168.100.104 avahi-daemon[4605]: New relevant interface tap1.IPv6 for mDNS. Sep 8 15:10:12 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap1.IPv6 with address fe80::c93:4ff:fea7:70b4. Sep 8 15:10:12 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::c93:4ff:fea7:70b4 on tap1. Sep 8 15:10:24 192.168.100.104 kernel: device tap2 entered promiscuous mode Sep 8 15:10:24 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:10:24 192.168.100.104 kernel: xenbr1: port 7(tap2) entering forwarding state Sep 8 15:10:24 192.168.100.104 kernel: device vif3.0 entered promiscuous mode Sep 8 15:10:24 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif3.0: link is not ready Sep 8 15:10:26 192.168.100.104 avahi-daemon[4605]: New relevant interface tap2.IPv6 for mDNS. Sep 8 15:10:26 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap2.IPv6 with address fe80::489d:1cff:fec5:224d. Sep 8 15:10:26 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::489d:1cff:fec5:224d on tap2. Sep 8 15:10:32 192.168.100.105 kernel: device tap18 entered promiscuous mode Sep 8 15:10:32 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:10:32 192.168.100.105 kernel: xenbr1: port 39(tap18) entering forwarding state Sep 8 15:10:33 192.168.100.105 kernel: device vif20.0 entered promiscuous mode Sep 8 15:10:33 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif20.0: link is not ready Sep 8 15:10:34 192.168.100.105 avahi-daemon[4535]: New relevant interface tap18.IPv6 for mDNS. Sep 8 15:10:34 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap18.IPv6 with address fe80::10ef:7fff:fe32:fe1d. Sep 8 15:10:34 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::10ef:7fff:fe32:fe1d on tap18. Sep 8 15:10:38 192.168.100.104 kernel: device tap3 entered promiscuous mode Sep 8 15:10:38 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:10:38 192.168.100.104 kernel: xenbr1: port 9(tap3) entering forwarding state Sep 8 15:10:38 192.168.100.104 kernel: device vif4.0 entered promiscuous mode Sep 8 15:10:38 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif4.0: link is not ready Sep 8 15:10:40 192.168.100.104 avahi-daemon[4605]: New relevant interface tap3.IPv6 for mDNS. Sep 8 15:10:40 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap3.IPv6 with address fe80::30f9:b8ff:fead:8112. Sep 8 15:10:40 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::30f9:b8ff:fead:8112 on tap3. Sep 8 15:10:53 192.168.100.104 kernel: device tap4 entered promiscuous mode Sep 8 15:10:53 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:10:53 192.168.100.104 kernel: xenbr1: port 11(tap4) entering forwarding state Sep 8 15:10:54 192.168.100.104 kernel: device vif5.0 entered promiscuous mode Sep 8 15:10:54 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif5.0: link is not ready Sep 8 15:10:55 192.168.100.104 avahi-daemon[4605]: New relevant interface tap4.IPv6 for mDNS. Sep 8 15:10:55 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap4.IPv6 with address fe80::dc51:6fff:fe7c:c04d. Sep 8 15:10:55 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::dc51:6fff:fe7c:c04d on tap4. Sep 8 15:10:59 192.168.100.105 kernel: device tap19 entered promiscuous mode Sep 8 15:10:59 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:10:59 192.168.100.105 kernel: xenbr1: port 41(tap19) entering forwarding state Sep 8 15:11:00 192.168.100.105 kernel: device vif21.0 entered promiscuous mode Sep 8 15:11:00 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif21.0: link is not ready Sep 8 15:11:01 192.168.100.105 avahi-daemon[4535]: New relevant interface tap19.IPv6 for mDNS. Sep 8 15:11:01 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap19.IPv6 with address fe80::38ef:c1ff:fed7:398b. Sep 8 15:11:01 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::38ef:c1ff:fed7:398b on tap19. Sep 8 15:11:09 192.168.100.104 kernel: device tap5 entered promiscuous mode Sep 8 15:11:09 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:11:09 192.168.100.104 kernel: xenbr1: port 13(tap5) entering forwarding state Sep 8 15:11:09 192.168.100.104 kernel: device vif6.0 entered promiscuous mode Sep 8 15:11:10 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif6.0: link is not ready Sep 8 15:11:11 192.168.100.104 avahi-daemon[4605]: New relevant interface tap5.IPv6 for mDNS. Sep 8 15:11:11 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap5.IPv6 with address fe80::34b0:eff:fe14:66a2. Sep 8 15:11:11 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::34b0:eff:fe14:66a2 on tap5. Sep 8 15:11:24 192.168.100.104 kernel: device tap6 entered promiscuous mode Sep 8 15:11:24 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:11:24 192.168.100.104 kernel: xenbr1: port 15(tap6) entering forwarding state Sep 8 15:11:24 192.168.100.104 kernel: device vif7.0 entered promiscuous mode Sep 8 15:11:24 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif7.0: link is not ready Sep 8 15:11:25 192.168.100.104 avahi-daemon[4605]: New relevant interface tap6.IPv6 for mDNS. Sep 8 15:11:25 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap6.IPv6 with address fe80::f02e:aaff:fedf:178c. Sep 8 15:11:25 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::f02e:aaff:fedf:178c on tap6. Sep 8 15:11:40 192.168.100.104 kernel: device tap7 entered promiscuous mode Sep 8 15:11:40 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:11:40 192.168.100.104 kernel: xenbr1: port 17(tap7) entering forwarding state Sep 8 15:11:40 192.168.100.104 kernel: device vif8.0 entered promiscuous mode Sep 8 15:11:40 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif8.0: link is not ready Sep 8 15:11:41 192.168.100.104 avahi-daemon[4605]: New relevant interface tap7.IPv6 for mDNS. Sep 8 15:11:41 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap7.IPv6 with address fe80::403:bff:fe70:f0d3. Sep 8 15:11:41 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::403:bff:fe70:f0d3 on tap7. Sep 8 15:11:54 192.168.100.104 kernel: device tap8 entered promiscuous mode Sep 8 15:11:54 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:11:54 192.168.100.104 kernel: xenbr1: port 19(tap8) entering forwarding state Sep 8 15:11:55 192.168.100.104 kernel: device vif9.0 entered promiscuous mode Sep 8 15:11:55 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif9.0: link is not ready Sep 8 15:11:56 192.168.100.104 avahi-daemon[4605]: New relevant interface tap8.IPv6 for mDNS. Sep 8 15:11:56 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap8.IPv6 with address fe80::80db:1bff:fe4a:b33d. Sep 8 15:11:56 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::80db:1bff:fe4a:b33d on tap8. Sep 8 15:12:12 192.168.100.104 kernel: device tap9 entered promiscuous mode Sep 8 15:12:12 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:12:12 192.168.100.104 kernel: xenbr1: port 21(tap9) entering forwarding state Sep 8 15:12:12 192.168.100.104 kernel: device vif10.0 entered promiscuous mode Sep 8 15:12:12 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif10.0: link is not ready Sep 8 15:12:13 192.168.100.104 avahi-daemon[4605]: New relevant interface tap9.IPv6 for mDNS. Sep 8 15:12:13 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap9.IPv6 with address fe80::4ce6:67ff:fe56:597e. Sep 8 15:12:13 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::4ce6:67ff:fe56:597e on tap9. Sep 8 15:12:27 192.168.100.104 kernel: device tap10 entered promiscuous mode Sep 8 15:12:27 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:12:27 192.168.100.104 kernel: xenbr1: port 23(tap10) entering forwarding state Sep 8 15:12:27 192.168.100.104 kernel: device vif11.0 entered promiscuous mode Sep 8 15:12:27 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif11.0: link is not ready Sep 8 15:12:28 192.168.100.104 avahi-daemon[4605]: New relevant interface tap10.IPv6 for mDNS. Sep 8 15:12:28 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap10.IPv6 with address fe80::4f8:7aff:fe56:4776. Sep 8 15:12:28 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::4f8:7aff:fe56:4776 on tap10. Sep 8 15:12:40 192.168.100.105 kernel: device tap20 entered promiscuous mode Sep 8 15:12:40 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:12:40 192.168.100.105 kernel: xenbr1: port 43(tap20) entering forwarding state Sep 8 15:12:41 192.168.100.105 kernel: device vif22.0 entered promiscuous mode Sep 8 15:12:41 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif22.0: link is not ready Sep 8 15:12:42 192.168.100.105 avahi-daemon[4535]: New relevant interface tap20.IPv6 for mDNS. Sep 8 15:12:42 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap20.IPv6 with address fe80::3c8f:dfff:fec5:a919. Sep 8 15:12:42 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::3c8f:dfff:fec5:a919 on tap20. Sep 8 15:12:43 192.168.100.104 kernel: device tap11 entered promiscuous mode Sep 8 15:12:43 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:12:43 192.168.100.104 kernel: xenbr1: port 25(tap11) entering forwarding state Sep 8 15:12:43 192.168.100.104 kernel: device vif12.0 entered promiscuous mode Sep 8 15:12:43 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif12.0: link is not ready Sep 8 15:12:44 192.168.100.104 avahi-daemon[4605]: New relevant interface tap11.IPv6 for mDNS. Sep 8 15:12:44 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap11.IPv6 with address fe80::40d:e6ff:fec2:b5d8. Sep 8 15:12:44 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::40d:e6ff:fec2:b5d8 on tap11. Sep 8 15:12:59 192.168.100.104 kernel: device tap12 entered promiscuous mode Sep 8 15:12:59 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:12:59 192.168.100.104 kernel: xenbr1: port 27(tap12) entering forwarding state Sep 8 15:12:59 192.168.100.104 kernel: device vif13.0 entered promiscuous mode Sep 8 15:13:00 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif13.0: link is not ready Sep 8 15:13:00 192.168.100.104 avahi-daemon[4605]: New relevant interface tap12.IPv6 for mDNS. Sep 8 15:13:00 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap12.IPv6 with address fe80::3004:faff:fe0f:712. Sep 8 15:13:00 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::3004:faff:fe0f:712 on tap12. Sep 8 15:13:20 192.168.100.104 kernel: device tap13 entered promiscuous mode Sep 8 15:13:20 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:13:20 192.168.100.104 kernel: xenbr1: port 29(tap13) entering forwarding state Sep 8 15:13:21 192.168.100.104 kernel: device vif14.0 entered promiscuous mode Sep 8 15:13:21 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif14.0: link is not ready Sep 8 15:13:21 192.168.100.104 avahi-daemon[4605]: New relevant interface tap13.IPv6 for mDNS. Sep 8 15:13:21 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap13.IPv6 with address fe80::20f5:d0ff:fe17:7037. Sep 8 15:13:21 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::20f5:d0ff:fe17:7037 on tap13. Sep 8 15:13:27 192.168.100.104 kernel: blkback: ring-ref 8, event-channel 4, protocol 1 (x86_64-abi) Sep 8 15:13:27 192.168.100.104 kernel: blkback: ring-ref 9, event-channel 5, protocol 1 (x86_64-abi) Sep 8 15:13:27 192.168.100.104 kernel: blkback: ring-ref 10, event-channel 6, protocol 1 (x86_64-abi) Sep 8 15:13:40 192.168.100.104 kernel: device tap14 entered promiscuous mode Sep 8 15:13:40 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:13:40 192.168.100.104 kernel: xenbr1: port 31(tap14) entering forwarding state Sep 8 15:13:40 192.168.100.104 kernel: device vif15.0 entered promiscuous mode Sep 8 15:13:40 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif15.0: link is not ready Sep 8 15:13:42 192.168.100.104 avahi-daemon[4605]: New relevant interface tap14.IPv6 for mDNS. Sep 8 15:13:42 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap14.IPv6 with address fe80::14bc:88ff:fe03:b40b. Sep 8 15:13:42 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::14bc:88ff:fe03:b40b on tap14. Sep 8 15:14:01 192.168.100.104 kernel: device tap15 entered promiscuous mode Sep 8 15:14:01 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:14:01 192.168.100.104 kernel: xenbr1: port 33(tap15) entering forwarding state Sep 8 15:14:01 192.168.100.104 kernel: device vif16.0 entered promiscuous mode Sep 8 15:14:01 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif16.0: link is not ready Sep 8 15:14:02 192.168.100.104 avahi-daemon[4605]: New relevant interface tap15.IPv6 for mDNS. Sep 8 15:14:02 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap15.IPv6 with address fe80::dc11:9eff:febb:3379. Sep 8 15:14:02 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::dc11:9eff:febb:3379 on tap15. Sep 8 15:14:17 192.168.100.105 kernel: device tap21 entered promiscuous mode Sep 8 15:14:17 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:14:17 192.168.100.105 kernel: xenbr1: port 45(tap21) entering forwarding state Sep 8 15:14:17 192.168.100.105 kernel: device vif23.0 entered promiscuous mode Sep 8 15:14:17 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif23.0: link is not ready Sep 8 15:14:19 192.168.100.105 avahi-daemon[4535]: New relevant interface tap21.IPv6 for mDNS. Sep 8 15:14:19 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap21.IPv6 with address fe80::444b:70ff:feac:1a5e. Sep 8 15:14:19 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::444b:70ff:feac:1a5e on tap21. Sep 8 15:14:27 192.168.100.104 kernel: device tap16 entered promiscuous mode Sep 8 15:14:27 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:14:27 192.168.100.104 kernel: xenbr1: port 35(tap16) entering forwarding state Sep 8 15:14:28 192.168.100.104 kernel: device vif17.0 entered promiscuous mode Sep 8 15:14:28 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif17.0: link is not ready Sep 8 15:14:29 192.168.100.104 avahi-daemon[4605]: New relevant interface tap16.IPv6 for mDNS. Sep 8 15:14:29 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap16.IPv6 with address fe80::74f4:d6ff:febe:ff08. Sep 8 15:14:29 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::74f4:d6ff:febe:ff08 on tap16. Sep 8 15:14:44 192.168.100.105 kernel: device tap22 entered promiscuous mode Sep 8 15:14:44 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:14:44 192.168.100.105 kernel: xenbr1: port 47(tap22) entering forwarding state Sep 8 15:14:45 192.168.100.105 kernel: device vif24.0 entered promiscuous mode Sep 8 15:14:45 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif24.0: link is not ready Sep 8 15:14:46 192.168.100.105 avahi-daemon[4535]: New relevant interface tap22.IPv6 for mDNS. Sep 8 15:14:46 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap22.IPv6 with address fe80::204e:21ff:fee3:25d3. Sep 8 15:14:46 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::204e:21ff:fee3:25d3 on tap22. Sep 8 15:14:58 192.168.100.104 kernel: device tap17 entered promiscuous mode Sep 8 15:14:58 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:14:58 192.168.100.104 kernel: xenbr1: port 37(tap17) entering forwarding state Sep 8 15:14:58 192.168.100.104 kernel: device vif18.0 entered promiscuous mode Sep 8 15:14:58 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif18.0: link is not ready Sep 8 15:14:59 192.168.100.104 avahi-daemon[4605]: New relevant interface tap17.IPv6 for mDNS. Sep 8 15:14:59 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap17.IPv6 with address fe80::b0fa:93ff:fe98:8e5. Sep 8 15:14:59 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::b0fa:93ff:fe98:8e5 on tap17. Sep 8 15:15:08 192.168.100.102 kernel: do_vfs_lock: VFS is out of sync with lock manager! Sep 8 15:15:09 192.168.100.102 kernel: do_vfs_lock: VFS is out of sync with lock manager! Sep 8 15:15:19 192.168.100.104 kernel: device tap18 entered promiscuous mode Sep 8 15:15:19 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:15:19 192.168.100.104 kernel: xenbr1: port 39(tap18) entering forwarding state Sep 8 15:15:19 192.168.100.104 kernel: device vif19.0 entered promiscuous mode Sep 8 15:15:19 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif19.0: link is not ready Sep 8 15:15:20 192.168.100.104 avahi-daemon[4605]: New relevant interface tap18.IPv6 for mDNS. Sep 8 15:15:20 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap18.IPv6 with address fe80::c04e:baff:fe9d:53bb. Sep 8 15:15:20 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::c04e:baff:fe9d:53bb on tap18. Sep 8 15:16:33 192.168.100.104 kernel: device tap19 entered promiscuous mode Sep 8 15:16:33 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:16:33 192.168.100.104 kernel: xenbr1: port 41(tap19) entering forwarding state Sep 8 15:16:33 192.168.100.104 kernel: device vif20.0 entered promiscuous mode Sep 8 15:16:33 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif20.0: link is not ready Sep 8 15:16:35 192.168.100.104 avahi-daemon[4605]: New relevant interface tap19.IPv6 for mDNS. Sep 8 15:16:35 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap19.IPv6 with address fe80::2c52:1dff:fe0e:f23f. Sep 8 15:16:35 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::2c52:1dff:fe0e:f23f on tap19. Sep 8 15:17:08 pxe xinetd[16078]: EXIT: tftp status=0 pid=26569 duration=2178(sec) Sep 8 15:17:46 192.168.100.104 kernel: device tap20 entered promiscuous mode Sep 8 15:17:46 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:17:46 192.168.100.104 kernel: xenbr1: port 43(tap20) entering forwarding state Sep 8 15:17:46 192.168.100.104 kernel: device vif21.0 entered promiscuous mode Sep 8 15:17:46 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif21.0: link is not ready Sep 8 15:17:48 192.168.100.104 avahi-daemon[4605]: New relevant interface tap20.IPv6 for mDNS. Sep 8 15:17:48 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap20.IPv6 with address fe80::30ed:5cff:fe05:c288. Sep 8 15:17:48 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::30ed:5cff:fe05:c288 on tap20. Sep 8 15:18:30 192.168.100.104 kernel: device tap21 entered promiscuous mode Sep 8 15:18:30 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:18:30 192.168.100.104 kernel: xenbr1: port 45(tap21) entering forwarding state Sep 8 15:18:30 192.168.100.104 kernel: device vif22.0 entered promiscuous mode Sep 8 15:18:30 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif22.0: link is not ready Sep 8 15:18:31 192.168.100.104 avahi-daemon[4605]: New relevant interface tap21.IPv6 for mDNS. Sep 8 15:18:31 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap21.IPv6 with address fe80::1448:34ff:fe7f:cda1. Sep 8 15:18:31 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::1448:34ff:fe7f:cda1 on tap21. Sep 8 15:19:18 192.168.100.102 kernel: device vif36.0 entered promiscuous mode Sep 8 15:19:18 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): vif36.0: link is not ready Sep 8 15:19:27 192.168.100.105 kernel: xenbr1: port 13(tap5) entering disabled state Sep 8 15:19:27 192.168.100.105 avahi-daemon[4535]: Interface tap5.IPv6 no longer relevant for mDNS. Sep 8 15:19:27 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap5.IPv6 with address fe80::6492:46ff:fe7e:38dd. Sep 8 15:19:27 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::6492:46ff:fe7e:38dd on tap5. Sep 8 15:19:27 192.168.100.105 kernel: device tap5 left promiscuous mode Sep 8 15:19:27 192.168.100.105 kernel: xenbr1: port 13(tap5) entering disabled state Sep 8 15:19:28 192.168.100.105 kernel: xenbr1: port 14(vif6.0) entering disabled state Sep 8 15:19:28 192.168.100.105 kernel: device vif6.0 left promiscuous mode Sep 8 15:19:28 192.168.100.105 kernel: xenbr1: port 14(vif6.0) entering disabled state Sep 8 15:19:33 192.168.100.102 kernel: device tap17 entered promiscuous mode Sep 8 15:19:33 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 15:19:33 192.168.100.102 kernel: xenbr1: port 38(tap17) entering forwarding state Sep 8 15:19:34 192.168.100.102 avahi-daemon[4486]: New relevant interface tap17.IPv6 for mDNS. Sep 8 15:19:34 192.168.100.102 avahi-daemon[4486]: Joining mDNS multicast group on interface tap17.IPv6 with address fe80::5444:55ff:fe99:2e18. Sep 8 15:19:34 192.168.100.102 avahi-daemon[4486]: Registering new address record for fe80::5444:55ff:fe99:2e18 on tap17. Sep 8 15:19:37 192.168.100.104 kernel: device tap22 entered promiscuous mode Sep 8 15:19:37 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:19:37 192.168.100.104 kernel: xenbr1: port 47(tap22) entering forwarding state Sep 8 15:19:38 192.168.100.104 kernel: device vif23.0 entered promiscuous mode Sep 8 15:19:38 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif23.0: link is not ready Sep 8 15:19:38 192.168.100.104 kernel: xenbr1: port 20(vif9.0) entering disabled state Sep 8 15:19:38 192.168.100.104 kernel: device vif9.0 left promiscuous mode Sep 8 15:19:38 192.168.100.104 kernel: xenbr1: port 20(vif9.0) entering disabled state Sep 8 15:19:38 192.168.100.104 avahi-daemon[4605]: Interface tap8.IPv6 no longer relevant for mDNS. Sep 8 15:19:38 192.168.100.104 avahi-daemon[4605]: Leaving mDNS multicast group on interface tap8.IPv6 with address fe80::80db:1bff:fe4a:b33d. Sep 8 15:19:38 192.168.100.104 avahi-daemon[4605]: Withdrawing address record for fe80::80db:1bff:fe4a:b33d on tap8. Sep 8 15:19:38 192.168.100.104 kernel: xenbr1: port 19(tap8) entering disabled state Sep 8 15:19:38 192.168.100.104 kernel: device tap8 left promiscuous mode Sep 8 15:19:38 192.168.100.104 kernel: xenbr1: port 19(tap8) entering disabled state Sep 8 15:19:39 192.168.100.104 avahi-daemon[4605]: New relevant interface tap22.IPv6 for mDNS. Sep 8 15:19:39 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap22.IPv6 with address fe80::d879:47ff:fe5c:de8a. Sep 8 15:19:39 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::d879:47ff:fe5c:de8a on tap22. Sep 8 15:19:39 192.168.100.104 kernel: device vif24.0 entered promiscuous mode Sep 8 15:19:39 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif24.0: link is not ready Sep 8 15:19:39 192.168.100.104 kernel: device tap8 entered promiscuous mode Sep 8 15:19:39 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:19:39 192.168.100.104 kernel: xenbr1: port 20(tap8) entering forwarding state Sep 8 15:19:41 192.168.100.104 avahi-daemon[4605]: New relevant interface tap8.IPv6 for mDNS. Sep 8 15:19:41 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap8.IPv6 with address fe80::4850:a0ff:fe4f:e01c. Sep 8 15:19:41 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::4850:a0ff:fe4f:e01c on tap8. Sep 8 15:21:08 192.168.100.104 kernel: device tap23 entered promiscuous mode Sep 8 15:21:08 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:21:08 192.168.100.104 kernel: xenbr1: port 49(tap23) entering forwarding state Sep 8 15:21:09 192.168.100.104 kernel: device vif25.0 entered promiscuous mode Sep 8 15:21:09 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif25.0: link is not ready Sep 8 15:21:10 192.168.100.104 avahi-daemon[4605]: New relevant interface tap23.IPv6 for mDNS. Sep 8 15:21:10 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap23.IPv6 with address fe80::a450:91ff:feb2:2c2b. Sep 8 15:21:10 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::a450:91ff:feb2:2c2b on tap23. Sep 8 15:21:23 192.168.100.105 kernel: device tap5 entered promiscuous mode Sep 8 15:21:23 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:21:23 192.168.100.105 kernel: xenbr1: port 13(tap5) entering forwarding state Sep 8 15:21:23 192.168.100.105 kernel: device vif25.0 entered promiscuous mode Sep 8 15:21:23 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif25.0: link is not ready Sep 8 15:21:25 192.168.100.105 avahi-daemon[4535]: New relevant interface tap5.IPv6 for mDNS. Sep 8 15:21:25 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap5.IPv6 with address fe80::88a6:56ff:fed1:c74e. Sep 8 15:21:25 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::88a6:56ff:fed1:c74e on tap5. Sep 8 15:21:46 192.168.100.104 kernel: device tap24 entered promiscuous mode Sep 8 15:21:46 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:21:46 192.168.100.104 kernel: xenbr1: port 51(tap24) entering forwarding state Sep 8 15:21:47 192.168.100.104 kernel: device vif26.0 entered promiscuous mode Sep 8 15:21:47 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif26.0: link is not ready Sep 8 15:21:48 192.168.100.104 avahi-daemon[4605]: New relevant interface tap24.IPv6 for mDNS. Sep 8 15:21:48 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap24.IPv6 with address fe80::f494:45ff:fe4c:445c. Sep 8 15:21:48 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::f494:45ff:fe4c:445c on tap24. Sep 8 15:22:21 192.168.100.102 kernel: device vif37.0 entered promiscuous mode Sep 8 15:22:21 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): vif37.0: link is not ready Sep 8 15:22:39 192.168.100.105 avahi-daemon[4535]: Interface tap6.IPv6 no longer relevant for mDNS. Sep 8 15:22:39 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap6.IPv6 with address fe80::9cc7:5eff:fe09:bb9b. Sep 8 15:22:39 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::9cc7:5eff:fe09:bb9b on tap6. Sep 8 15:22:39 192.168.100.105 kernel: xenbr1: port 15(tap6) entering disabled state Sep 8 15:22:39 192.168.100.105 kernel: device tap6 left promiscuous mode Sep 8 15:22:39 192.168.100.105 kernel: xenbr1: port 15(tap6) entering disabled state Sep 8 15:22:39 192.168.100.104 kernel: device tap25 entered promiscuous mode Sep 8 15:22:39 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:22:39 192.168.100.104 kernel: xenbr1: port 53(tap25) entering forwarding state Sep 8 15:22:39 192.168.100.104 kernel: device vif27.0 entered promiscuous mode Sep 8 15:22:39 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif27.0: link is not ready Sep 8 15:22:40 192.168.100.105 kernel: xenbr1: port 16(vif7.0) entering disabled state Sep 8 15:22:40 192.168.100.105 kernel: device vif7.0 left promiscuous mode Sep 8 15:22:40 192.168.100.105 kernel: xenbr1: port 16(vif7.0) entering disabled state Sep 8 15:22:40 192.168.100.102 kernel: device tap18 entered promiscuous mode Sep 8 15:22:40 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 15:22:40 192.168.100.102 kernel: xenbr1: port 40(tap18) entering forwarding state Sep 8 15:22:40 192.168.100.104 avahi-daemon[4605]: New relevant interface tap25.IPv6 for mDNS. Sep 8 15:22:40 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap25.IPv6 with address fe80::acfe:7fff:fe45:232c. Sep 8 15:22:40 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::acfe:7fff:fe45:232c on tap25. Sep 8 15:22:42 192.168.100.102 avahi-daemon[4486]: New relevant interface tap18.IPv6 for mDNS. Sep 8 15:22:42 192.168.100.102 avahi-daemon[4486]: Joining mDNS multicast group on interface tap18.IPv6 with address fe80::c5e:2dff:fefe:f096. Sep 8 15:22:42 192.168.100.102 avahi-daemon[4486]: Registering new address record for fe80::c5e:2dff:fefe:f096 on tap18. Sep 8 15:23:18 192.168.100.105 kernel: device tap6 entered promiscuous mode Sep 8 15:23:18 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:23:18 192.168.100.105 kernel: xenbr1: port 15(tap6) entering forwarding state Sep 8 15:23:18 192.168.100.105 kernel: device vif26.0 entered promiscuous mode Sep 8 15:23:18 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif26.0: link is not ready Sep 8 15:23:19 192.168.100.105 avahi-daemon[4535]: New relevant interface tap6.IPv6 for mDNS. Sep 8 15:23:19 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap6.IPv6 with address fe80::acf2:aff:fe42:ba57. Sep 8 15:23:19 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::acf2:aff:fe42:ba57 on tap6. Sep 8 15:23:44 192.168.100.104 kernel: device tap26 entered promiscuous mode Sep 8 15:23:44 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:23:44 192.168.100.104 kernel: xenbr1: port 55(tap26) entering forwarding state Sep 8 15:23:45 192.168.100.105 kernel: device tap23 entered promiscuous mode Sep 8 15:23:45 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:23:45 192.168.100.105 kernel: xenbr1: port 49(tap23) entering forwarding state Sep 8 15:23:45 192.168.100.104 kernel: device vif28.0 entered promiscuous mode Sep 8 15:23:45 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif28.0: link is not ready Sep 8 15:23:45 192.168.100.105 kernel: device vif27.0 entered promiscuous mode Sep 8 15:23:45 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif27.0: link is not ready Sep 8 15:23:46 192.168.100.104 avahi-daemon[4605]: New relevant interface tap26.IPv6 for mDNS. Sep 8 15:23:46 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap26.IPv6 with address fe80::4821:d6ff:fe43:b7ea. Sep 8 15:23:46 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::4821:d6ff:fe43:b7ea on tap26. Sep 8 15:23:46 192.168.100.105 avahi-daemon[4535]: New relevant interface tap23.IPv6 for mDNS. Sep 8 15:23:46 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap23.IPv6 with address fe80::285d:74ff:fe84:cd6. Sep 8 15:23:46 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::285d:74ff:fe84:cd6 on tap23. Sep 8 15:24:09 192.168.100.102 kernel: xenbr1: port 39(vif37.0) entering disabled state Sep 8 15:24:09 192.168.100.102 kernel: device vif37.0 left promiscuous mode Sep 8 15:24:09 192.168.100.102 kernel: xenbr1: port 39(vif37.0) entering disabled state Sep 8 15:24:09 192.168.100.102 kernel: xenbr1: port 40(tap18) entering disabled state Sep 8 15:24:09 192.168.100.102 avahi-daemon[4486]: Interface tap18.IPv6 no longer relevant for mDNS. Sep 8 15:24:09 192.168.100.102 avahi-daemon[4486]: Leaving mDNS multicast group on interface tap18.IPv6 with address fe80::c5e:2dff:fefe:f096. Sep 8 15:24:09 192.168.100.102 avahi-daemon[4486]: Withdrawing address record for fe80::c5e:2dff:fefe:f096 on tap18. Sep 8 15:24:09 192.168.100.102 kernel: device tap18 left promiscuous mode Sep 8 15:24:09 192.168.100.102 kernel: xenbr1: port 40(tap18) entering disabled state Sep 8 15:24:10 192.168.100.102 kernel: device tap18 entered promiscuous mode Sep 8 15:24:11 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 15:24:11 192.168.100.102 kernel: xenbr1: port 39(tap18) entering forwarding state Sep 8 15:24:11 192.168.100.102 kernel: device vif38.0 entered promiscuous mode Sep 8 15:24:11 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): vif38.0: link is not ready Sep 8 15:24:12 192.168.100.102 avahi-daemon[4486]: New relevant interface tap18.IPv6 for mDNS. Sep 8 15:24:12 192.168.100.102 avahi-daemon[4486]: Joining mDNS multicast group on interface tap18.IPv6 with address fe80::6ca1:e2ff:feb5:5178. Sep 8 15:24:12 192.168.100.102 avahi-daemon[4486]: Registering new address record for fe80::6ca1:e2ff:feb5:5178 on tap18. Sep 8 15:24:57 192.168.100.102 kernel: xenbr1: port 40(vif38.0) entering disabled state Sep 8 15:24:57 192.168.100.102 kernel: device vif38.0 left promiscuous mode Sep 8 15:24:57 192.168.100.102 kernel: xenbr1: port 40(vif38.0) entering disabled state Sep 8 15:24:57 192.168.100.102 avahi-daemon[4486]: Interface tap18.IPv6 no longer relevant for mDNS. Sep 8 15:24:57 192.168.100.102 avahi-daemon[4486]: Leaving mDNS multicast group on interface tap18.IPv6 with address fe80::6ca1:e2ff:feb5:5178. Sep 8 15:24:57 192.168.100.102 avahi-daemon[4486]: Withdrawing address record for fe80::6ca1:e2ff:feb5:5178 on tap18. Sep 8 15:24:57 192.168.100.102 kernel: xenbr1: port 39(tap18) entering disabled state Sep 8 15:24:57 192.168.100.102 kernel: device tap18 left promiscuous mode Sep 8 15:24:57 192.168.100.102 kernel: xenbr1: port 39(tap18) entering disabled state Sep 8 15:25:06 192.168.100.104 kernel: device tap27 entered promiscuous mode Sep 8 15:25:06 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:25:06 192.168.100.104 kernel: xenbr1: port 57(tap27) entering forwarding state Sep 8 15:25:08 192.168.100.104 avahi-daemon[4605]: New relevant interface tap27.IPv6 for mDNS. Sep 8 15:25:08 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap27.IPv6 with address fe80::1c1a:dfff:fe3f:de2a. Sep 8 15:25:08 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::1c1a:dfff:fe3f:de2a on tap27. Sep 8 15:25:08 192.168.100.104 kernel: device vif29.0 entered promiscuous mode Sep 8 15:25:08 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif29.0: link is not ready Sep 8 15:25:14 192.168.100.102 kernel: device tap18 entered promiscuous mode Sep 8 15:25:14 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 15:25:14 192.168.100.102 kernel: xenbr1: port 39(tap18) entering forwarding state Sep 8 15:25:15 192.168.100.102 kernel: device vif39.0 entered promiscuous mode Sep 8 15:25:15 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): vif39.0: link is not ready Sep 8 15:25:16 192.168.100.102 avahi-daemon[4486]: New relevant interface tap18.IPv6 for mDNS. Sep 8 15:25:16 192.168.100.102 avahi-daemon[4486]: Joining mDNS multicast group on interface tap18.IPv6 with address fe80::b8ee:4ff:fe0d:1a3. Sep 8 15:25:16 192.168.100.102 avahi-daemon[4486]: Registering new address record for fe80::b8ee:4ff:fe0d:1a3 on tap18. Sep 8 15:26:32 192.168.100.104 kernel: device tap28 entered promiscuous mode Sep 8 15:26:32 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:26:32 192.168.100.104 kernel: xenbr1: port 59(tap28) entering forwarding state Sep 8 15:26:33 192.168.100.104 kernel: device vif30.0 entered promiscuous mode Sep 8 15:26:33 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif30.0: link is not ready Sep 8 15:26:33 192.168.100.104 avahi-daemon[4605]: New relevant interface tap28.IPv6 for mDNS. Sep 8 15:26:33 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap28.IPv6 with address fe80::58c2:97ff:fe8b:c371. Sep 8 15:26:33 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::58c2:97ff:fe8b:c371 on tap28. Sep 8 15:27:49 192.168.100.104 kernel: device tap29 entered promiscuous mode Sep 8 15:27:49 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 15:27:49 192.168.100.104 kernel: xenbr1: port 61(tap29) entering forwarding state Sep 8 15:27:50 192.168.100.104 kernel: device vif31.0 entered promiscuous mode Sep 8 15:27:50 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif31.0: link is not ready Sep 8 15:27:51 192.168.100.104 avahi-daemon[4605]: New relevant interface tap29.IPv6 for mDNS. Sep 8 15:27:51 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap29.IPv6 with address fe80::9c91:29ff:fe18:10e3. Sep 8 15:27:51 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::9c91:29ff:fe18:10e3 on tap29. Sep 8 15:28:02 192.168.100.105 kernel: device tap24 entered promiscuous mode Sep 8 15:28:02 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:28:02 192.168.100.105 kernel: xenbr1: port 51(tap24) entering forwarding state Sep 8 15:28:02 192.168.100.105 kernel: device vif28.0 entered promiscuous mode Sep 8 15:28:02 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif28.0: link is not ready Sep 8 15:28:04 192.168.100.105 avahi-daemon[4535]: New relevant interface tap24.IPv6 for mDNS. Sep 8 15:28:04 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap24.IPv6 with address fe80::c8ce:77ff:fe52:8271. Sep 8 15:28:04 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::c8ce:77ff:fe52:8271 on tap24. Sep 8 15:28:34 192.168.100.105 kernel: device tap25 entered promiscuous mode Sep 8 15:28:34 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:28:34 192.168.100.105 kernel: xenbr1: port 53(tap25) entering forwarding state Sep 8 15:28:34 192.168.100.105 kernel: device vif29.0 entered promiscuous mode Sep 8 15:28:34 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif29.0: link is not ready Sep 8 15:28:35 192.168.100.105 avahi-daemon[4535]: New relevant interface tap25.IPv6 for mDNS. Sep 8 15:28:35 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap25.IPv6 with address fe80::4036:a9ff:fe32:633a. Sep 8 15:28:35 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::4036:a9ff:fe32:633a on tap25. Sep 8 15:29:38 192.168.100.105 kernel: device tap26 entered promiscuous mode Sep 8 15:29:38 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:29:38 192.168.100.105 kernel: xenbr1: port 55(tap26) entering forwarding state Sep 8 15:29:38 192.168.100.105 kernel: device vif30.0 entered promiscuous mode Sep 8 15:29:38 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif30.0: link is not ready Sep 8 15:29:39 192.168.100.105 avahi-daemon[4535]: New relevant interface tap26.IPv6 for mDNS. Sep 8 15:29:39 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap26.IPv6 with address fe80::f0b8:66ff:fe3b:d073. Sep 8 15:29:39 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::f0b8:66ff:fe3b:d073 on tap26. Sep 8 15:30:26 192.168.100.105 kernel: device tap27 entered promiscuous mode Sep 8 15:30:26 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:30:26 192.168.100.105 kernel: xenbr1: port 57(tap27) entering forwarding state Sep 8 15:30:26 192.168.100.105 kernel: device vif31.0 entered promiscuous mode Sep 8 15:30:26 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif31.0: link is not ready Sep 8 15:30:27 192.168.100.105 avahi-daemon[4535]: New relevant interface tap27.IPv6 for mDNS. Sep 8 15:30:27 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap27.IPv6 with address fe80::547d:14ff:fe4f:cfc5. Sep 8 15:30:27 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::547d:14ff:fe4f:cfc5 on tap27. Sep 8 15:31:39 192.168.100.105 kernel: device tap28 entered promiscuous mode Sep 8 15:31:39 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:31:39 192.168.100.105 kernel: xenbr1: port 59(tap28) entering forwarding state Sep 8 15:31:40 192.168.100.105 kernel: device vif32.0 entered promiscuous mode Sep 8 15:31:40 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif32.0: link is not ready Sep 8 15:31:41 192.168.100.105 avahi-daemon[4535]: New relevant interface tap28.IPv6 for mDNS. Sep 8 15:31:41 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap28.IPv6 with address fe80::9885:edff:fe5f:1899. Sep 8 15:31:41 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::9885:edff:fe5f:1899 on tap28. Sep 8 15:32:35 192.168.100.104 kernel: blkback: ring-ref 8, event-channel 4, protocol 1 (x86_64-abi) Sep 8 15:32:35 192.168.100.104 kernel: blkback: ring-ref 9, event-channel 5, protocol 1 (x86_64-abi) Sep 8 15:32:35 192.168.100.104 kernel: blkback: ring-ref 10, event-channel 6, protocol 1 (x86_64-abi) Sep 8 15:32:41 192.168.100.104 kernel: blkback: ring-ref 768, event-channel 4, protocol 1 (x86_64-abi) Sep 8 15:32:41 192.168.100.104 kernel: blkback: ring-ref 769, event-channel 5, protocol 1 (x86_64-abi) Sep 8 15:32:41 192.168.100.104 kernel: blkback: ring-ref 770, event-channel 6, protocol 1 (x86_64-abi) Sep 8 15:32:46 192.168.100.105 kernel: device tap29 entered promiscuous mode Sep 8 15:32:46 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:32:46 192.168.100.105 kernel: xenbr1: port 61(tap29) entering forwarding state Sep 8 15:32:46 192.168.100.105 kernel: device vif33.0 entered promiscuous mode Sep 8 15:32:46 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif33.0: link is not ready Sep 8 15:32:47 192.168.100.105 avahi-daemon[4535]: New relevant interface tap29.IPv6 for mDNS. Sep 8 15:32:47 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap29.IPv6 with address fe80::54d6:73ff:fe24:d3c2. Sep 8 15:32:47 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::54d6:73ff:fe24:d3c2 on tap29. Sep 8 15:33:31 192.168.100.105 kernel: blkback: ring-ref 8, event-channel 4, protocol 1 (x86_64-abi) Sep 8 15:33:31 192.168.100.105 kernel: blkback: ring-ref 9, event-channel 5, protocol 1 (x86_64-abi) Sep 8 15:33:31 192.168.100.105 kernel: blkback: ring-ref 10, event-channel 6, protocol 1 (x86_64-abi) Sep 8 15:34:26 192.168.100.105 kernel: device tap30 entered promiscuous mode Sep 8 15:34:26 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:34:26 192.168.100.105 kernel: xenbr1: port 63(tap30) entering forwarding state Sep 8 15:34:26 192.168.100.105 kernel: device vif34.0 entered promiscuous mode Sep 8 15:34:26 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif34.0: link is not ready Sep 8 15:34:27 192.168.100.105 avahi-daemon[4535]: New relevant interface tap30.IPv6 for mDNS. Sep 8 15:34:27 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap30.IPv6 with address fe80::a455:d5ff:fed8:d98. Sep 8 15:34:27 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::a455:d5ff:fed8:d98 on tap30. Sep 8 15:35:16 192.168.100.105 kernel: blkback: ring-ref 8, event-channel 4, protocol 1 (x86_64-abi) Sep 8 15:35:16 192.168.100.105 kernel: blkback: ring-ref 9, event-channel 5, protocol 1 (x86_64-abi) Sep 8 15:35:16 192.168.100.105 kernel: blkback: ring-ref 10, event-channel 6, protocol 1 (x86_64-abi) Sep 8 15:35:50 192.168.100.104 kernel: xenbr1: port 30(vif14.0) entering disabled state Sep 8 15:35:50 192.168.100.104 kernel: device vif14.0 left promiscuous mode Sep 8 15:35:50 192.168.100.104 kernel: xenbr1: port 30(vif14.0) entering disabled state Sep 8 15:35:51 192.168.100.104 avahi-daemon[4605]: Interface tap13.IPv6 no longer relevant for mDNS. Sep 8 15:35:51 192.168.100.104 avahi-daemon[4605]: Leaving mDNS multicast group on interface tap13.IPv6 with address fe80::20f5:d0ff:fe17:7037. Sep 8 15:35:51 192.168.100.104 avahi-daemon[4605]: Withdrawing address record for fe80::20f5:d0ff:fe17:7037 on tap13. Sep 8 15:35:51 192.168.100.104 kernel: xenbr1: port 29(tap13) entering disabled state Sep 8 15:35:51 192.168.100.104 kernel: device tap13 left promiscuous mode Sep 8 15:35:51 192.168.100.104 kernel: xenbr1: port 29(tap13) entering disabled state Sep 8 15:38:19 192.168.100.101 kernel: xenbr1: port 35(vif61.0) entering disabled state Sep 8 15:38:19 192.168.100.101 kernel: device vif61.0 left promiscuous mode Sep 8 15:38:19 192.168.100.101 kernel: xenbr1: port 35(vif61.0) entering disabled state Sep 8 15:38:19 192.168.100.101 avahi-daemon[4286]: Interface tap16.IPv6 no longer relevant for mDNS. Sep 8 15:38:19 192.168.100.101 avahi-daemon[4286]: Leaving mDNS multicast group on interface tap16.IPv6 with address fe80::7424:3fff:fe76:2455. Sep 8 15:38:19 192.168.100.101 avahi-daemon[4286]: Withdrawing address record for fe80::7424:3fff:fe76:2455 on tap16. Sep 8 15:38:19 192.168.100.101 kernel: xenbr1: port 36(tap16) entering disabled state Sep 8 15:38:19 192.168.100.101 kernel: device tap16 left promiscuous mode Sep 8 15:38:19 192.168.100.101 kernel: xenbr1: port 36(tap16) entering disabled state Sep 8 15:38:22 192.168.100.101 kernel: device tap16 entered promiscuous mode Sep 8 15:38:22 192.168.100.101 kernel: xenbr1: topology change detected, propagating Sep 8 15:38:22 192.168.100.101 kernel: xenbr1: port 35(tap16) entering forwarding state Sep 8 15:38:22 192.168.100.101 kernel: device vif67.0 entered promiscuous mode Sep 8 15:38:22 192.168.100.101 kernel: ADDRCONF(NETDEV_UP): vif67.0: link is not ready Sep 8 15:38:24 192.168.100.101 avahi-daemon[4286]: New relevant interface tap16.IPv6 for mDNS. Sep 8 15:38:24 192.168.100.101 avahi-daemon[4286]: Joining mDNS multicast group on interface tap16.IPv6 with address fe80::3440:10ff:fee9:3531. Sep 8 15:38:24 192.168.100.101 avahi-daemon[4286]: Registering new address record for fe80::3440:10ff:fee9:3531 on tap16. Sep 8 15:38:36 192.168.100.102 kernel: xenbr1: port 40(vif39.0) entering disabled state Sep 8 15:38:36 192.168.100.102 kernel: device vif39.0 left promiscuous mode Sep 8 15:38:36 192.168.100.102 kernel: xenbr1: port 40(vif39.0) entering disabled state Sep 8 15:38:36 192.168.100.102 avahi-daemon[4486]: Interface tap18.IPv6 no longer relevant for mDNS. Sep 8 15:38:36 192.168.100.102 avahi-daemon[4486]: Leaving mDNS multicast group on interface tap18.IPv6 with address fe80::b8ee:4ff:fe0d:1a3. Sep 8 15:38:36 192.168.100.102 avahi-daemon[4486]: Withdrawing address record for fe80::b8ee:4ff:fe0d:1a3 on tap18. Sep 8 15:38:36 192.168.100.102 kernel: xenbr1: port 39(tap18) entering disabled state Sep 8 15:38:36 192.168.100.102 kernel: device tap18 left promiscuous mode Sep 8 15:38:36 192.168.100.102 kernel: xenbr1: port 39(tap18) entering disabled state Sep 8 15:39:04 192.168.100.102 kernel: kjournald starting. Commit interval 5 seconds Sep 8 15:39:04 192.168.100.102 kernel: EXT3 FS on loop2, internal journal Sep 8 15:39:04 192.168.100.102 kernel: EXT3-fs: mounted filesystem with ordered data mode. Sep 8 15:39:12 192.168.100.102 kernel: EXT3-fs error (device loop2): ext3_lookup: unlinked inode 296462 in dir #295489 Sep 8 15:39:12 192.168.100.102 kernel: Aborting journal on device loop2. Sep 8 15:39:12 192.168.100.102 kernel: ext3_abort called. Sep 8 15:39:12 192.168.100.102 kernel: EXT3-fs error (device loop2): ext3_journal_start_sb: Detected aborted journal Sep 8 15:39:12 192.168.100.102 kernel: Remounting filesystem read-only Sep 8 15:39:12 192.168.100.102 kernel: EXT3-fs error (device loop2): ext3_lookup: unlinked inode 296475 in dir #295489 Sep 8 15:39:12 192.168.100.102 kernel: EXT3-fs error (device loop2): ext3_lookup: unlinked inode 296464 in dir #295489 Sep 8 15:39:35 192.168.100.102 kernel: ext3_abort called. Sep 8 15:39:35 192.168.100.102 kernel: EXT3-fs error (device loop2): ext3_put_super: Couldn't clean up the journal Sep 8 15:39:56 192.168.100.102 kernel: device tap18 entered promiscuous mode Sep 8 15:39:56 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 15:39:56 192.168.100.102 kernel: xenbr1: port 39(tap18) entering forwarding state Sep 8 15:39:56 192.168.100.102 kernel: device vif40.0 entered promiscuous mode Sep 8 15:39:56 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): vif40.0: link is not ready Sep 8 15:39:57 192.168.100.102 avahi-daemon[4486]: New relevant interface tap18.IPv6 for mDNS. Sep 8 15:39:57 192.168.100.102 avahi-daemon[4486]: Joining mDNS multicast group on interface tap18.IPv6 with address fe80::bc:c7ff:fe20:5b84. Sep 8 15:39:57 192.168.100.102 avahi-daemon[4486]: Registering new address record for fe80::bc:c7ff:fe20:5b84 on tap18. Sep 8 15:40:11 192.168.100.105 kernel: xenbr1: port 34(vif17.0) entering disabled state Sep 8 15:40:12 192.168.100.105 kernel: device vif17.0 left promiscuous mode Sep 8 15:40:12 192.168.100.105 kernel: xenbr1: port 34(vif17.0) entering disabled state Sep 8 15:40:12 192.168.100.105 avahi-daemon[4535]: Interface tap15.IPv6 no longer relevant for mDNS. Sep 8 15:40:12 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap15.IPv6 with address fe80::248a:ecff:fe34:66d8. Sep 8 15:40:12 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::248a:ecff:fe34:66d8 on tap15. Sep 8 15:40:12 192.168.100.105 kernel: xenbr1: port 33(tap15) entering disabled state Sep 8 15:40:12 192.168.100.105 kernel: device tap15 left promiscuous mode Sep 8 15:40:12 192.168.100.105 kernel: xenbr1: port 33(tap15) entering disabled state Sep 8 15:40:13 192.168.100.105 kernel: device tap15 entered promiscuous mode Sep 8 15:40:13 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:40:13 192.168.100.105 kernel: xenbr1: port 33(tap15) entering forwarding state Sep 8 15:40:13 192.168.100.105 kernel: device vif35.0 entered promiscuous mode Sep 8 15:40:13 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif35.0: link is not ready Sep 8 15:40:14 192.168.100.105 avahi-daemon[4535]: New relevant interface tap15.IPv6 for mDNS. Sep 8 15:40:14 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap15.IPv6 with address fe80::64aa:7ff:fe42:a99f. Sep 8 15:40:14 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::64aa:7ff:fe42:a99f on tap15. Sep 8 15:41:10 192.168.100.102 kernel: xenbr1: port 40(vif40.0) entering disabled state Sep 8 15:41:11 192.168.100.102 kernel: device vif40.0 left promiscuous mode Sep 8 15:41:11 192.168.100.102 kernel: xenbr1: port 40(vif40.0) entering disabled state Sep 8 15:41:11 192.168.100.102 kernel: xenbr1: port 39(tap18) entering disabled state Sep 8 15:41:11 192.168.100.102 avahi-daemon[4486]: Interface tap18.IPv6 no longer relevant for mDNS. Sep 8 15:41:11 192.168.100.102 avahi-daemon[4486]: Leaving mDNS multicast group on interface tap18.IPv6 with address fe80::bc:c7ff:fe20:5b84. Sep 8 15:41:11 192.168.100.102 avahi-daemon[4486]: Withdrawing address record for fe80::bc:c7ff:fe20:5b84 on tap18. Sep 8 15:41:11 192.168.100.102 kernel: device tap18 left promiscuous mode Sep 8 15:41:11 192.168.100.102 kernel: xenbr1: port 39(tap18) entering disabled state Sep 8 15:42:46 192.168.100.102 kernel: kjournald starting. Commit interval 5 seconds Sep 8 15:42:46 192.168.100.102 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended Sep 8 15:42:46 192.168.100.102 kernel: EXT3 FS on loop3, internal journal Sep 8 15:42:46 192.168.100.102 kernel: EXT3-fs: mounted filesystem with ordered data mode. Sep 8 15:43:41 192.168.100.102 kernel: EXT3-fs error (device loop3): ext3_free_blocks_sb: bit already cleared for block 623604 Sep 8 15:43:41 192.168.100.102 kernel: Aborting journal on device loop3. Sep 8 15:43:41 192.168.100.102 kernel: EXT3-fs error (device loop3) in ext3_free_blocks_sb: Journal has aborted Sep 8 15:43:41 192.168.100.102 kernel: EXT3-fs error (device loop3) in ext3_free_blocks_sb: Journal has aborted Sep 8 15:43:41 192.168.100.102 kernel: EXT3-fs error (device loop3) in ext3_reserve_inode_write: Journal has aborted Sep 8 15:43:41 192.168.100.102 kernel: EXT3-fs error (device loop3) in ext3_truncate: Journal has aborted Sep 8 15:43:41 192.168.100.102 kernel: EXT3-fs error (device loop3) in ext3_reserve_inode_write: Journal has aborted Sep 8 15:43:41 192.168.100.102 kernel: EXT3-fs error (device loop3) in ext3_orphan_del: Journal has aborted Sep 8 15:43:41 192.168.100.102 kernel: EXT3-fs error (device loop3) in ext3_reserve_inode_write: Journal has aborted Sep 8 15:43:41 192.168.100.102 kernel: EXT3-fs error (device loop3) in ext3_delete_inode: Journal has aborted Sep 8 15:43:41 192.168.100.102 kernel: ext3_abort called. Sep 8 15:43:41 192.168.100.102 kernel: EXT3-fs error (device loop3): ext3_journal_start_sb: Detected aborted journal Sep 8 15:43:41 192.168.100.102 kernel: Remounting filesystem read-only Sep 8 15:43:42 192.168.100.102 kernel: __journal_remove_journal_head: freeing b_committed_data Sep 8 15:43:43 192.168.100.102 kernel: __journal_remove_journal_head: freeing b_committed_data Sep 8 15:44:01 192.168.100.102 kernel: __journal_remove_journal_head: freeing b_committed_data Sep 8 15:44:01 192.168.100.102 kernel: ext3_abort called. Sep 8 15:44:01 192.168.100.102 kernel: EXT3-fs error (device loop3): ext3_put_super: Couldn't clean up the journal Sep 8 15:44:08 192.168.100.102 kernel: kjournald starting. Commit interval 5 seconds Sep 8 15:44:09 192.168.100.102 kernel: EXT3-fs warning (device loop4): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure Sep 8 15:44:09 192.168.100.102 kernel: EXT3-fs warning (device loop4): ext3_clear_journal_err: Marking fs in need of filesystem check. Sep 8 15:44:09 192.168.100.102 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended Sep 8 15:44:09 192.168.100.102 kernel: EXT3 FS on loop4, internal journal Sep 8 15:44:09 192.168.100.102 kernel: EXT3-fs: recovery complete. Sep 8 15:44:09 192.168.100.102 kernel: EXT3-fs: mounted filesystem with ordered data mode. Sep 8 15:46:16 192.168.100.102 kernel: xenbr1: port 37(vif36.0) entering disabled state Sep 8 15:46:16 192.168.100.102 kernel: device vif36.0 left promiscuous mode Sep 8 15:46:16 192.168.100.102 kernel: xenbr1: port 37(vif36.0) entering disabled state Sep 8 15:46:16 192.168.100.102 avahi-daemon[4486]: Interface tap17.IPv6 no longer relevant for mDNS. Sep 8 15:46:16 192.168.100.102 avahi-daemon[4486]: Leaving mDNS multicast group on interface tap17.IPv6 with address fe80::5444:55ff:fe99:2e18. Sep 8 15:46:16 192.168.100.102 avahi-daemon[4486]: Withdrawing address record for fe80::5444:55ff:fe99:2e18 on tap17. Sep 8 15:46:16 192.168.100.102 kernel: xenbr1: port 38(tap17) entering disabled state Sep 8 15:46:16 192.168.100.102 kernel: device tap17 left promiscuous mode Sep 8 15:46:16 192.168.100.102 kernel: xenbr1: port 38(tap17) entering disabled state Sep 8 15:47:10 192.168.100.102 kernel: device tap17 entered promiscuous mode Sep 8 15:47:10 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 15:47:10 192.168.100.102 kernel: xenbr1: port 37(tap17) entering forwarding state Sep 8 15:47:10 192.168.100.102 kernel: device vif41.0 entered promiscuous mode Sep 8 15:47:10 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): vif41.0: link is not ready Sep 8 15:47:11 192.168.100.102 avahi-daemon[4486]: New relevant interface tap17.IPv6 for mDNS. Sep 8 15:47:11 192.168.100.102 avahi-daemon[4486]: Joining mDNS multicast group on interface tap17.IPv6 with address fe80::ac07:14ff:fedd:a77a. Sep 8 15:47:11 192.168.100.102 avahi-daemon[4486]: Registering new address record for fe80::ac07:14ff:fedd:a77a on tap17. Sep 8 15:48:14 192.168.100.105 kernel: xenbr1: port 56(vif30.0) entering disabled state Sep 8 15:48:14 192.168.100.105 kernel: device vif30.0 left promiscuous mode Sep 8 15:48:14 192.168.100.105 kernel: xenbr1: port 56(vif30.0) entering disabled state Sep 8 15:48:15 192.168.100.105 avahi-daemon[4535]: Interface tap26.IPv6 no longer relevant for mDNS. Sep 8 15:48:15 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap26.IPv6 with address fe80::f0b8:66ff:fe3b:d073. Sep 8 15:48:15 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::f0b8:66ff:fe3b:d073 on tap26. Sep 8 15:48:15 192.168.100.105 kernel: xenbr1: port 55(tap26) entering disabled state Sep 8 15:48:15 192.168.100.105 kernel: device tap26 left promiscuous mode Sep 8 15:48:15 192.168.100.105 kernel: xenbr1: port 55(tap26) entering disabled state Sep 8 15:48:17 192.168.100.105 kernel: device vif36.0 entered promiscuous mode Sep 8 15:48:17 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif36.0: link is not ready Sep 8 15:48:17 192.168.100.105 kernel: device tap26 entered promiscuous mode Sep 8 15:48:17 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:48:17 192.168.100.105 kernel: xenbr1: port 56(tap26) entering forwarding state Sep 8 15:48:18 192.168.100.105 avahi-daemon[4535]: New relevant interface tap26.IPv6 for mDNS. Sep 8 15:48:18 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap26.IPv6 with address fe80::9ca6:c8ff:fe8d:1534. Sep 8 15:48:18 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::9ca6:c8ff:fe8d:1534 on tap26. Sep 8 15:52:15 192.168.100.102 kernel: xenbr1: port 38(vif41.0) entering disabled state Sep 8 15:52:15 192.168.100.102 kernel: device vif41.0 left promiscuous mode Sep 8 15:52:15 192.168.100.102 kernel: xenbr1: port 38(vif41.0) entering disabled state Sep 8 15:52:15 192.168.100.102 avahi-daemon[4486]: Interface tap17.IPv6 no longer relevant for mDNS. Sep 8 15:52:15 192.168.100.102 avahi-daemon[4486]: Leaving mDNS multicast group on interface tap17.IPv6 with address fe80::ac07:14ff:fedd:a77a. Sep 8 15:52:15 192.168.100.102 avahi-daemon[4486]: Withdrawing address record for fe80::ac07:14ff:fedd:a77a on tap17. Sep 8 15:52:15 192.168.100.102 kernel: xenbr1: port 37(tap17) entering disabled state Sep 8 15:52:15 192.168.100.102 kernel: device tap17 left promiscuous mode Sep 8 15:52:15 192.168.100.102 kernel: xenbr1: port 37(tap17) entering disabled state Sep 8 15:52:16 192.168.100.102 kernel: device tap17 entered promiscuous mode Sep 8 15:52:16 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 15:52:16 192.168.100.102 kernel: xenbr1: port 37(tap17) entering forwarding state Sep 8 15:52:16 192.168.100.102 kernel: device vif42.0 entered promiscuous mode Sep 8 15:52:16 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): vif42.0: link is not ready Sep 8 15:52:17 192.168.100.102 avahi-daemon[4486]: New relevant interface tap17.IPv6 for mDNS. Sep 8 15:52:17 192.168.100.102 avahi-daemon[4486]: Joining mDNS multicast group on interface tap17.IPv6 with address fe80::dcc9:54ff:fe64:e70b. Sep 8 15:52:17 192.168.100.102 avahi-daemon[4486]: Registering new address record for fe80::dcc9:54ff:fe64:e70b on tap17. Sep 8 15:54:43 192.168.100.103 syslogd 1.4.1: restart. Sep 8 15:54:46 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: fatal: invalid metadata block Sep 8 15:54:46 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: bh = 567447924 (magic number) Sep 8 15:54:46 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: function = gfs2_meta_indirect_buffer, file = fs/gfs2/meta_io.c, line = 334 Sep 8 15:54:46 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: about to withdraw this file system Sep 8 15:54:46 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: telling LM to withdraw Sep 8 15:54:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 15:54:47 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 15:54:47 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=1: Trying to acquire journal lock... Sep 8 15:54:47 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 15:54:47 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=1: Busy Sep 8 15:54:47 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 15:54:47 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 15:54:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Busy Sep 8 15:54:47 192.168.100.103 kernel: GFS2: fsid=xencluster1:xenclusterfs1.1: withdrawn Sep 8 15:54:47 192.168.100.103 kernel: Sep 8 15:54:47 192.168.100.103 kernel: Call Trace: Sep 8 15:54:47 192.168.100.103 kernel: [] :gfs2:gfs2_lm_withdraw+0xc1/0xd0 Sep 8 15:54:47 192.168.100.103 kernel: [] __wait_on_bit+0x60/0x6e Sep 8 15:54:47 192.168.100.103 kernel: [] sync_buffer+0x0/0x3f Sep 8 15:54:47 192.168.100.103 kernel: [] :gfs2:glock_work_func+0x0/0xb8 Sep 8 15:54:47 192.168.100.103 kernel: [] out_of_line_wait_on_bit+0x6c/0x78 Sep 8 15:54:47 192.168.100.103 kernel: [] wake_bit_function+0x0/0x23 Sep 8 15:54:47 192.168.100.103 kernel: [] submit_bh+0x10a/0x111 Sep 8 15:54:47 192.168.100.103 kernel: [] :gfs2:gfs2_meta_check_ii+0x2c/0x38 Sep 8 15:54:47 192.168.100.103 kernel: [] :gfs2:gfs2_meta_indirect_buffer+0x104/0x160 Sep 8 15:54:47 192.168.100.103 kernel: [] __wake_up_common+0x3e/0x68 Sep 8 15:54:47 192.168.100.103 kernel: [] :gfs2:gfs2_inode_refresh+0x22/0x2cf Sep 8 15:54:48 192.168.100.103 kernel: [] :gfs2:inode_go_lock+0x44/0xbe Sep 8 15:54:48 192.168.100.103 kernel: [] :gfs2:do_promote+0xad/0x137 Sep 8 15:54:48 192.168.100.103 kernel: [] :gfs2:finish_xmote+0x28c/0x2b7 Sep 8 15:54:48 192.168.100.103 kernel: [] :gfs2:glock_work_func+0x1d/0xb8 Sep 8 15:54:48 192.168.100.103 kernel: [] run_workqueue+0x94/0xe4 Sep 8 15:54:48 192.168.100.103 kernel: [] worker_thread+0x0/0x122 Sep 8 15:54:48 192.168.100.103 kernel: [] keventd_create_kthread+0x0/0xc4 Sep 8 15:54:48 192.168.100.103 kernel: [] worker_thread+0xf0/0x122 Sep 8 15:54:48 192.168.100.103 kernel: [] default_wake_function+0x0/0xe Sep 8 15:54:48 192.168.100.103 kernel: [] keventd_create_kthread+0x0/0xc4 Sep 8 15:54:48 192.168.100.103 kernel: [] keventd_create_kthread+0x0/0xc4 Sep 8 15:54:48 192.168.100.103 kernel: [] kthread+0xfe/0x132 Sep 8 15:54:48 192.168.100.103 kernel: [] child_rip+0xa/0x12 Sep 8 15:54:48 192.168.100.103 kernel: [] keventd_create_kthread+0x0/0xc4 Sep 8 15:54:48 192.168.100.103 kernel: [] kthread+0x0/0x132 Sep 8 15:54:48 192.168.100.103 kernel: [] child_rip+0x0/0x12 Sep 8 15:54:48 192.168.100.103 kernel: Sep 8 15:54:48 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=1: Trying to acquire journal lock... Sep 8 15:54:48 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 15:54:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 15:54:48 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 15:54:48 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 15:54:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Busy Sep 8 15:54:48 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 15:54:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 15:54:48 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 15:54:48 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 15:54:49 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 15:54:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Busy Sep 8 15:54:49 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 15:54:49 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=1: Looking at journal... Sep 8 15:54:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 15:54:49 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 15:54:49 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 15:54:49 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 15:54:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Busy Sep 8 15:54:49 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 15:54:49 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 15:54:49 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 15:54:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 15:54:50 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 15:54:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Busy Sep 8 15:54:50 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 15:54:50 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 15:54:50 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 15:54:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 15:54:50 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 15:54:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Busy Sep 8 15:54:50 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Busy Sep 8 15:54:50 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=1: Acquiring the transaction lock... Sep 8 15:54:50 192.168.100.105 kernel: lock_dlm: gdlm_cancel 1,2 flags 0 Sep 8 15:54:50 192.168.100.105 kernel: lock_dlm: gdlm_cancel skip 1,2 flags 0 Sep 8 15:54:50 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=1: Replaying journal... Sep 8 15:54:50 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=1: Replayed 0 of 0 blocks Sep 8 15:54:50 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=1: Found 0 revoke tags Sep 8 15:54:50 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=1: Journal replayed in 0s Sep 8 15:54:50 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=1: Done Sep 8 15:54:50 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Trying to acquire journal lock... Sep 8 15:54:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 15:54:50 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 15:54:50 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 15:54:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Busy Sep 8 15:54:51 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Looking at journal... Sep 8 15:54:51 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 15:54:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 15:54:51 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Busy Sep 8 15:54:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Busy Sep 8 15:54:51 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: jid=1: Done Sep 8 15:54:52 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Trying to acquire journal lock... Sep 8 15:54:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 15:54:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Busy Sep 8 15:54:52 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Looking at journal... Sep 8 15:54:52 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=1: Done Sep 8 15:54:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Trying to acquire journal lock... Sep 8 15:54:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Looking at journal... Sep 8 15:54:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=1: Done Sep 8 15:57:50 192.168.100.105 kernel: xenbr1: port 46(vif23.0) entering disabled state Sep 8 15:57:50 192.168.100.105 kernel: device vif23.0 left promiscuous mode Sep 8 15:57:50 192.168.100.105 kernel: xenbr1: port 46(vif23.0) entering disabled state Sep 8 15:57:50 192.168.100.105 avahi-daemon[4535]: Interface tap21.IPv6 no longer relevant for mDNS. Sep 8 15:57:50 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap21.IPv6 with address fe80::444b:70ff:feac:1a5e. Sep 8 15:57:50 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::444b:70ff:feac:1a5e on tap21. Sep 8 15:57:50 192.168.100.105 kernel: xenbr1: port 45(tap21) entering disabled state Sep 8 15:57:50 192.168.100.105 kernel: device tap21 left promiscuous mode Sep 8 15:57:50 192.168.100.105 kernel: xenbr1: port 45(tap21) entering disabled state Sep 8 15:57:51 192.168.100.105 kernel: device tap21 entered promiscuous mode Sep 8 15:57:51 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 15:57:51 192.168.100.105 kernel: xenbr1: port 45(tap21) entering forwarding state Sep 8 15:57:51 192.168.100.105 kernel: device vif37.0 entered promiscuous mode Sep 8 15:57:51 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif37.0: link is not ready Sep 8 15:57:53 192.168.100.105 avahi-daemon[4535]: New relevant interface tap21.IPv6 for mDNS. Sep 8 15:57:53 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap21.IPv6 with address fe80::4074:49ff:fe31:3b11. Sep 8 15:57:53 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::4074:49ff:fe31:3b11 on tap21. Sep 8 16:06:01 192.168.100.105 kernel: xenbr1: port 18(vif8.0) entering disabled state Sep 8 16:06:02 192.168.100.105 kernel: device vif8.0 left promiscuous mode Sep 8 16:06:02 192.168.100.105 kernel: xenbr1: port 18(vif8.0) entering disabled state Sep 8 16:06:02 192.168.100.105 kernel: xenbr1: port 17(tap7) entering disabled state Sep 8 16:06:02 192.168.100.105 avahi-daemon[4535]: Interface tap7.IPv6 no longer relevant for mDNS. Sep 8 16:06:02 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap7.IPv6 with address fe80::2490:39ff:fec4:4b52. Sep 8 16:06:02 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::2490:39ff:fec4:4b52 on tap7. Sep 8 16:06:02 192.168.100.105 kernel: device tap7 left promiscuous mode Sep 8 16:06:02 192.168.100.105 kernel: xenbr1: port 17(tap7) entering disabled state Sep 8 16:06:03 192.168.100.105 kernel: device tap7 entered promiscuous mode Sep 8 16:06:03 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 16:06:03 192.168.100.105 kernel: xenbr1: port 17(tap7) entering forwarding state Sep 8 16:06:04 192.168.100.105 kernel: device vif38.0 entered promiscuous mode Sep 8 16:06:04 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif38.0: link is not ready Sep 8 16:06:05 192.168.100.105 avahi-daemon[4535]: New relevant interface tap7.IPv6 for mDNS. Sep 8 16:06:05 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap7.IPv6 with address fe80::83f:f1ff:fed0:8c03. Sep 8 16:06:05 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::83f:f1ff:fed0:8c03 on tap7. Sep 8 16:14:47 192.168.100.102 kernel: kjournald starting. Commit interval 5 seconds Sep 8 16:14:47 192.168.100.102 kernel: EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended Sep 8 16:14:47 192.168.100.102 kernel: EXT3 FS on loop5, internal journal Sep 8 16:14:47 192.168.100.102 kernel: EXT3-fs: recovery complete. Sep 8 16:14:47 192.168.100.102 kernel: EXT3-fs: mounted filesystem with ordered data mode. Sep 8 16:14:50 192.168.100.105 kernel: xenbr1: port 24(vif12.0) entering disabled state Sep 8 16:14:50 192.168.100.105 kernel: device vif12.0 left promiscuous mode Sep 8 16:14:50 192.168.100.105 kernel: xenbr1: port 24(vif12.0) entering disabled state Sep 8 16:14:50 192.168.100.105 avahi-daemon[4535]: Interface tap10.IPv6 no longer relevant for mDNS. Sep 8 16:14:50 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap10.IPv6 with address fe80::d49c:28ff:fe95:ce8c. Sep 8 16:14:50 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::d49c:28ff:fe95:ce8c on tap10. Sep 8 16:14:50 192.168.100.105 kernel: xenbr1: port 23(tap10) entering disabled state Sep 8 16:14:50 192.168.100.105 kernel: device tap10 left promiscuous mode Sep 8 16:14:50 192.168.100.105 kernel: xenbr1: port 23(tap10) entering disabled state Sep 8 16:15:04 192.168.100.105 kernel: device tap10 entered promiscuous mode Sep 8 16:15:04 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 16:15:04 192.168.100.105 kernel: xenbr1: port 23(tap10) entering forwarding state Sep 8 16:15:05 192.168.100.105 kernel: device vif39.0 entered promiscuous mode Sep 8 16:15:05 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif39.0: link is not ready Sep 8 16:15:06 192.168.100.105 avahi-daemon[4535]: New relevant interface tap10.IPv6 for mDNS. Sep 8 16:15:06 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap10.IPv6 with address fe80::2848:25ff:fe81:c140. Sep 8 16:15:06 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::2848:25ff:fe81:c140 on tap10. Sep 8 16:15:35 192.168.100.104 kernel: xenbr1: port 32(vif15.0) entering disabled state Sep 8 16:15:35 192.168.100.104 kernel: device vif15.0 left promiscuous mode Sep 8 16:15:35 192.168.100.104 kernel: xenbr1: port 32(vif15.0) entering disabled state Sep 8 16:15:36 192.168.100.104 avahi-daemon[4605]: Interface tap14.IPv6 no longer relevant for mDNS. Sep 8 16:15:36 192.168.100.104 avahi-daemon[4605]: Leaving mDNS multicast group on interface tap14.IPv6 with address fe80::14bc:88ff:fe03:b40b. Sep 8 16:15:36 192.168.100.104 avahi-daemon[4605]: Withdrawing address record for fe80::14bc:88ff:fe03:b40b on tap14. Sep 8 16:15:36 192.168.100.104 kernel: xenbr1: port 31(tap14) entering disabled state Sep 8 16:15:36 192.168.100.104 kernel: device tap14 left promiscuous mode Sep 8 16:15:36 192.168.100.104 kernel: xenbr1: port 31(tap14) entering disabled state Sep 8 16:15:38 192.168.100.104 kernel: device tap13 entered promiscuous mode Sep 8 16:15:38 192.168.100.104 kernel: xenbr1: topology change detected, propagating Sep 8 16:15:38 192.168.100.104 kernel: xenbr1: port 29(tap13) entering forwarding state Sep 8 16:15:38 192.168.100.104 kernel: device vif32.0 entered promiscuous mode Sep 8 16:15:38 192.168.100.104 kernel: ADDRCONF(NETDEV_UP): vif32.0: link is not ready Sep 8 16:15:39 192.168.100.104 avahi-daemon[4605]: New relevant interface tap13.IPv6 for mDNS. Sep 8 16:15:39 192.168.100.104 avahi-daemon[4605]: Joining mDNS multicast group on interface tap13.IPv6 with address fe80::d4b9:70ff:fe59:6b18. Sep 8 16:15:39 192.168.100.104 avahi-daemon[4605]: Registering new address record for fe80::d4b9:70ff:fe59:6b18 on tap13. Sep 8 16:16:09 192.168.100.105 kernel: xenbr1: port 32(vif16.0) entering disabled state Sep 8 16:16:09 192.168.100.105 kernel: device vif16.0 left promiscuous mode Sep 8 16:16:09 192.168.100.105 kernel: xenbr1: port 32(vif16.0) entering disabled state Sep 8 16:16:09 192.168.100.105 avahi-daemon[4535]: Interface tap14.IPv6 no longer relevant for mDNS. Sep 8 16:16:09 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap14.IPv6 with address fe80::45f:e9ff:fed4:e37e. Sep 8 16:16:09 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::45f:e9ff:fed4:e37e on tap14. Sep 8 16:16:09 192.168.100.105 kernel: xenbr1: port 31(tap14) entering disabled state Sep 8 16:16:09 192.168.100.105 kernel: device tap14 left promiscuous mode Sep 8 16:16:09 192.168.100.105 kernel: xenbr1: port 31(tap14) entering disabled state Sep 8 16:16:11 192.168.100.105 kernel: device tap14 entered promiscuous mode Sep 8 16:16:11 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 16:16:11 192.168.100.105 kernel: xenbr1: port 31(tap14) entering forwarding state Sep 8 16:16:11 192.168.100.105 kernel: device vif40.0 entered promiscuous mode Sep 8 16:16:11 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif40.0: link is not ready Sep 8 16:16:13 192.168.100.105 avahi-daemon[4535]: New relevant interface tap14.IPv6 for mDNS. Sep 8 16:16:13 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap14.IPv6 with address fe80::f88b:7cff:fed7:4e99. Sep 8 16:16:13 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::f88b:7cff:fed7:4e99 on tap14. Sep 8 16:17:23 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:23 192.168.100.102 kernel: loop5: rw=0, want=13464957736, limit=83904449 Sep 8 16:17:23 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1683119716 Sep 8 16:17:24 192.168.100.102 kernel: Aborting journal on device loop5. Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=5309763088, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=663720385 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=10321439120, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1290179889 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=17006777776, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2125847221 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=533753400, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=66719174 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=1407161008, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=175895125 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=18947277632, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2368409703 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=13673039840, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1709129979 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=10979342856, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1372417856 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=31642908928, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3955363615 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=20412275416, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2551534426 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16935963280, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2116995409 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=30736507480, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3842063434 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=5657230192, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=707153773 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=6716141568, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=839517695 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16781886056, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2097735756 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=9506583176, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1188322896 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=34182792552, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4272849068 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=13819179816, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1727397476 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=17882994432, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2235374303 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=22495400008, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2811925000 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=25570816304, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3196352037 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=8936311776, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1117038971 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=5688614760, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=711076844 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=7139251072, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=892406383 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=11782259888, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1472782485 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=29847760896, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3730970111 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=17084675416, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2135584426 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=3033351632, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=379168953 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=2416019320, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=302002414 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=1106274040, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=138284254 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=20053775280, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2506721909 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=27487203824, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3435900477 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=19372796432, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2421599553 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=31575564736, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3946945591 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=21205566592, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2650695823 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=33084063704, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4135507962 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=13132443144, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1641555392 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=21907579880, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2738447484 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=11336471472, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1417058933 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=6260247832, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=782530978 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=1683531808, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=210441475 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=15731748072, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1966468508 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=20843462856, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2605432856 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=9486390056, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1185798756 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=11027903464, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1378487932 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=32026596024, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4003324502 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=20786089352, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2598261168 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=21037561600, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2629695199 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=13162236192, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1645279523 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=17068524024, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2133565502 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=13702820744, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1712852592 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=30298002160, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3787250269 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=14737489888, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1842186235 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=959551768, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=119943970 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=14081854632, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1760231828 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=22702969744, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2837871217 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=11725074040, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1465634254 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=11157631800, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1394703974 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16887158896, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2110894861 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=28391954400, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3548994299 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16567971504, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2070996437 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=10003204272, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1250400533 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=449338352, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=56167293 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=34299848504, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4287481062 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=10512554192, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1314069273 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=22157435864, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2769679482 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=10987611088, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1373451385 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=13475362232, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1684420278 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=8494227432, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1061778428 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=7732648936, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=966581116 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=24338331800, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3042291474 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16256519552, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2032064943 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=3974172616, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=496771576 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=5055713240, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=631964154 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16574159368, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2071769920 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=8118437448, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1014804680 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=9654907768, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1206863470 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=23038646416, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2879830801 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=3661755504, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=457719437 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=23428567984, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2928570997 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=13482016208, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1685252025 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=30719409336, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3839926166 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=28748270416, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3593533801 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=5509202696, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=688650336 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=26250398600, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3281299824 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=17214949688, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2151868710 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=22822223296, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2852777911 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=13346651872, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1668331483 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=7378866208, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=922358275 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=6904976952, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=863122118 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=32250535856, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4031316981 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=1991351784, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=248918972 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=18344910288, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2293113785 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=19554097880, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2444262234 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=26687688432, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3335961053 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=5232338880, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=654042359 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=15652573664, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1956571707 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=34326105528, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4290763190 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=27171600096, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3396450011 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=14707825520, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1838478189 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=19987805920, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2498475739 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=14725602160, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1840700269 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=24542531464, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3067816432 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=14722331616, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1840291451 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=15654256448, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1956782055 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=13086208720, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1635776089 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=18528453720, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2316056714 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=29127757040, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3640969629 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=19161287816, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2395160976 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=8618772256, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1077346531 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=2885154256, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=360644281 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=12297956264, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1537244532 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16370826296, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2046353286 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=34047002520, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4255875314 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=17621605104, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2202700637 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=24113237344, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3014154667 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=17352968184, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2169121022 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=21927209624, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2740901202 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16219761592, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2027470198 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=25664886744, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3208110842 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=21775484424, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2721935552 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=15583414328, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1947926790 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=4395592896, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=549449111 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=26503774392, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3312971798 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=19906868664, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2488358582 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=1172012488, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=146501560 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=30072558168, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3759069770 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=1569742936, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=196217866 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=14348847816, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1842738262 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=272137720 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3861090769 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2509131195 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1104305835 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=9324638232, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1165579778 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=28321412928, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3540176615 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=22930152840, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=4028767136, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1286384696 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=424084296 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3890254114 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=915607904 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=722466107 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2482154904 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2291395996 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4271881399 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=86664546 Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=13293931280, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=24602149904, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1171093158 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3346485864 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=18030680984, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2253835122 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16518052928, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2064756615 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1145482058 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=433105881 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4061529148 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=349339147 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3861836192 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3647891856 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3484022753 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4158482224 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=668063404 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3812905495 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2088824691 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=369375937 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1504437728 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16881482312, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3524925268 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3792741993 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2913518264 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3180644799 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=23260316296, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2907539536 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=29394054752, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3674256843 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=6586356712, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=31894332688, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1158256008 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2637376969 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=29142405168, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=15524722408, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=25428957328, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4282080572 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2328562784 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1303915724 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3773352395 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3797376926 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3365052352 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2556038690 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1383468888 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=11832719344, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=2552478360, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=319059794 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3401346382 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=154134344 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=25140752560, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3003493054 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3858556952 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=607282392 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3428591551 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2773201447 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3071872647 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1536216571 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=286858275 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=13513703080, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=15481207 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1596364125 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2302102020 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3003301081 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4229599271 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1833245470 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2376409397 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=15381460808, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1922682600 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16927228240, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2115903529 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1331162250 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2860797315 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2230837383 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1544945855 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=130988259 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=295421817 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=4062992259 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2795709052 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1377831968 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1077401335 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=8133190160, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=1492906336, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2811312593 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=7170316104, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=896289512 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=18930482920, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2366310364 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=4685348168, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=29383389952, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3672923743 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=23441676928, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=10959214168, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=10122709192, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2230386822 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3155888856 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=21972062952, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1868953949 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2028985033 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=31357330896, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=12218734488, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16230788768, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2028848595 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=24737684920, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=34164698128, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=450693327 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2520966272 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=896451258 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1310322713 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2663333863 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3347751845 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3572476648 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=85683387 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=953053331 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3069860757 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2452177827 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3093223038 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2942643469 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1724829093 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=16406378560, limit=83904449 Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2050797319 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2026709738 Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:24 192.168.100.102 kernel: loop5: rw=0, want=26267674144, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3283459267 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=6116248312, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=764531038 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=21736419872, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2717052483 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2585367434 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2098815580 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=14460392976, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1399392502 Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=29682877176, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1006329835 Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=32658567712, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2092976308 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3375555243 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=3670260480, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1913785412 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=27801329224, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2078905633 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2056864598 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2452658573 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=433406200 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=3654809752, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=456851218 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=8466036640, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1058254579 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=11675363304, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=458181189 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=8121172520, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=1743038840, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=32537923128, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=13865940848, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3948621856 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1059824298 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=17814276040, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1623878587 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1465292698 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1719899028 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=30576417952, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=25405218344, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=32408751328, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=32639252376, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2034736988 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2544191114 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3955740412 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3183049301 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=31041877280, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=3880234659 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=13853013712, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1731626713 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=1202543006 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=21378973528, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=3721600392, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2920974975 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=843430782 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=20409509512, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=2580899448 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: loop5: rw=0, want=16790569984, limit=83904449 Sep 8 16:17:25 192.168.100.102 kernel: attempt to access beyond end of device Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_free_branches: Read failure, inode=1070722, block=830382449 Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5) in ext3_truncate: Journal has aborted Sep 8 16:17:25 192.168.100.102 kernel: EXT3-fs error (device loop5) in ext3_reserve_inode_write: Journal has aborted Sep 8 16:17:25 192.168.100.102 kernel: Remounting filesystem read-only Sep 8 16:17:28 192.168.100.102 kernel: ext3_abort called. Sep 8 16:17:28 192.168.100.102 kernel: EXT3-fs error (device loop5): ext3_put_super: Couldn't clean up the journal Sep 8 16:18:15 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: fatal: invalid metadata block Sep 8 16:18:15 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: bh = 567447924 (magic number) Sep 8 16:18:15 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: function = gfs2_meta_indirect_buffer, file = fs/gfs2/meta_io.c, line = 334 Sep 8 16:18:15 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: about to withdraw this file system Sep 8 16:18:15 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: telling LM to withdraw Sep 8 16:18:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Trying to acquire journal lock... Sep 8 16:18:17 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Trying to acquire journal lock... Sep 8 16:18:17 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=3: Trying to acquire journal lock... Sep 8 16:18:17 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=3: Busy Sep 8 16:18:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Busy Sep 8 16:18:17 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Busy Sep 8 16:18:17 192.168.100.102 kernel: GFS2: fsid=xencluster1:xenclusterfs1.3: withdrawn Sep 8 16:18:17 192.168.100.102 kernel: Sep 8 16:18:17 192.168.100.102 kernel: Call Trace: Sep 8 16:18:17 192.168.100.102 kernel: [] :gfs2:gfs2_lm_withdraw+0xc1/0xd0 Sep 8 16:18:17 192.168.100.102 kernel: [] __wait_on_bit+0x60/0x6e Sep 8 16:18:17 192.168.100.102 kernel: [] sync_buffer+0x0/0x3f Sep 8 16:18:17 192.168.100.102 kernel: [] out_of_line_wait_on_bit+0x6c/0x78 Sep 8 16:18:17 192.168.100.102 kernel: [] wake_bit_function+0x0/0x23 Sep 8 16:18:17 192.168.100.102 kernel: [] submit_bh+0x10a/0x111 Sep 8 16:18:17 192.168.100.102 kernel: [] :gfs2:gfs2_meta_check_ii+0x2c/0x38 Sep 8 16:18:17 192.168.100.102 kernel: [] :gfs2:gfs2_meta_indirect_buffer+0x104/0x160 Sep 8 16:18:17 192.168.100.102 kernel: [] :gfs2:gfs2_permission+0xaf/0xd3 Sep 8 16:18:17 192.168.100.102 kernel: [] :gfs2:gfs2_dir_read+0x403/0x535 Sep 8 16:18:17 192.168.100.102 kernel: [] filldir+0x0/0xb7 Sep 8 16:18:17 192.168.100.102 kernel: [] wake_up_bit+0x11/0x22 Sep 8 16:18:17 192.168.100.102 kernel: [] wake_up_bit+0x11/0x22 Sep 8 16:18:17 192.168.100.102 kernel: [] :gfs2:do_promote+0xf5/0x137 Sep 8 16:18:17 192.168.100.102 kernel: [] :gfs2:run_queue+0xad/0x17c Sep 8 16:18:17 192.168.100.102 kernel: [] filldir+0x0/0xb7 Sep 8 16:18:17 192.168.100.102 kernel: [] :gfs2:gfs2_readdir+0x6b/0x8f Sep 8 16:18:17 192.168.100.102 kernel: [] :gfs2:gfs2_readdir+0x40/0x8f Sep 8 16:18:17 192.168.100.102 kernel: [] filldir+0x0/0xb7 Sep 8 16:18:17 192.168.100.102 kernel: [] vfs_readdir+0x77/0xa9 Sep 8 16:18:17 192.168.100.102 kernel: [] sys_getdents+0x75/0xbd Sep 8 16:18:17 192.168.100.102 kernel: [] tracesys+0x47/0xb6 Sep 8 16:18:17 192.168.100.102 kernel: [] tracesys+0xab/0xb6 Sep 8 16:18:17 192.168.100.102 kernel: Sep 8 16:18:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Trying to acquire journal lock... Sep 8 16:18:18 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Trying to acquire journal lock... Sep 8 16:18:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Busy Sep 8 16:18:18 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Busy Sep 8 16:18:18 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=3: Trying to acquire journal lock... Sep 8 16:18:18 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=3: Looking at journal... Sep 8 16:18:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Trying to acquire journal lock... Sep 8 16:18:18 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Trying to acquire journal lock... Sep 8 16:18:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Busy Sep 8 16:18:18 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Busy Sep 8 16:18:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Trying to acquire journal lock... Sep 8 16:18:19 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Trying to acquire journal lock... Sep 8 16:18:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Busy Sep 8 16:18:19 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Busy Sep 8 16:18:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Trying to acquire journal lock... Sep 8 16:18:19 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Trying to acquire journal lock... Sep 8 16:18:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Busy Sep 8 16:18:19 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Busy Sep 8 16:18:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Trying to acquire journal lock... Sep 8 16:18:20 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Trying to acquire journal lock... Sep 8 16:18:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Busy Sep 8 16:18:20 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Busy Sep 8 16:18:20 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=3: Acquiring the transaction lock... Sep 8 16:18:20 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=3: Replaying journal... Sep 8 16:18:20 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=3: Replayed 24 of 25 blocks Sep 8 16:18:20 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=3: Found 1 revoke tags Sep 8 16:18:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Trying to acquire journal lock... Sep 8 16:18:20 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Trying to acquire journal lock... Sep 8 16:18:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Busy Sep 8 16:18:20 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Busy Sep 8 16:18:21 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=3: Journal replayed in 1s Sep 8 16:18:21 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: jid=3: Done Sep 8 16:18:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Trying to acquire journal lock... Sep 8 16:18:21 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Trying to acquire journal lock... Sep 8 16:18:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Busy Sep 8 16:18:21 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Busy Sep 8 16:18:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Trying to acquire journal lock... Sep 8 16:18:21 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Trying to acquire journal lock... Sep 8 16:18:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Busy Sep 8 16:18:21 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Busy Sep 8 16:18:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Trying to acquire journal lock... Sep 8 16:18:22 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Trying to acquire journal lock... Sep 8 16:18:22 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Busy Sep 8 16:18:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Looking at journal... Sep 8 16:18:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=3: Done Sep 8 16:18:23 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Trying to acquire journal lock... Sep 8 16:18:23 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Looking at journal... Sep 8 16:18:24 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=3: Done Sep 8 16:19:08 192.168.100.105 kernel: xenbr1: port 24(vif39.0) entering disabled state Sep 8 16:19:08 192.168.100.105 kernel: device vif39.0 left promiscuous mode Sep 8 16:19:08 192.168.100.105 kernel: xenbr1: port 24(vif39.0) entering disabled state Sep 8 16:19:08 192.168.100.105 avahi-daemon[4535]: Interface tap10.IPv6 no longer relevant for mDNS. Sep 8 16:19:08 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap10.IPv6 with address fe80::2848:25ff:fe81:c140. Sep 8 16:19:08 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::2848:25ff:fe81:c140 on tap10. Sep 8 16:19:08 192.168.100.105 kernel: xenbr1: port 23(tap10) entering disabled state Sep 8 16:19:08 192.168.100.105 kernel: device tap10 left promiscuous mode Sep 8 16:19:08 192.168.100.105 kernel: xenbr1: port 23(tap10) entering disabled state Sep 8 16:22:43 192.168.100.105 kernel: xenbr1: port 18(vif38.0) entering disabled state Sep 8 16:22:43 192.168.100.105 kernel: device vif38.0 left promiscuous mode Sep 8 16:22:43 192.168.100.105 kernel: xenbr1: port 18(vif38.0) entering disabled state Sep 8 16:22:43 192.168.100.105 avahi-daemon[4535]: Interface tap7.IPv6 no longer relevant for mDNS. Sep 8 16:22:43 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap7.IPv6 with address fe80::83f:f1ff:fed0:8c03. Sep 8 16:22:43 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::83f:f1ff:fed0:8c03 on tap7. Sep 8 16:22:43 192.168.100.105 kernel: xenbr1: port 17(tap7) entering disabled state Sep 8 16:22:43 192.168.100.105 kernel: device tap7 left promiscuous mode Sep 8 16:22:43 192.168.100.105 kernel: xenbr1: port 17(tap7) entering disabled state Sep 8 16:22:44 192.168.100.105 kernel: device vif41.0 entered promiscuous mode Sep 8 16:22:44 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif41.0: link is not ready Sep 8 16:22:45 192.168.100.105 kernel: device tap7 entered promiscuous mode Sep 8 16:22:45 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 16:22:45 192.168.100.105 kernel: xenbr1: port 18(tap7) entering forwarding state Sep 8 16:22:47 192.168.100.105 avahi-daemon[4535]: New relevant interface tap7.IPv6 for mDNS. Sep 8 16:22:47 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap7.IPv6 with address fe80::1478:1dff:fef5:2fd4. Sep 8 16:22:47 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::1478:1dff:fef5:2fd4 on tap7. Sep 8 16:36:29 192.168.100.105 kernel: xenbr1: port 48(vif24.0) entering disabled state Sep 8 16:36:30 192.168.100.105 kernel: device vif24.0 left promiscuous mode Sep 8 16:36:30 192.168.100.105 kernel: xenbr1: port 48(vif24.0) entering disabled state Sep 8 16:36:30 192.168.100.105 avahi-daemon[4535]: Interface tap22.IPv6 no longer relevant for mDNS. Sep 8 16:36:30 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap22.IPv6 with address fe80::204e:21ff:fee3:25d3. Sep 8 16:36:30 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::204e:21ff:fee3:25d3 on tap22. Sep 8 16:36:30 192.168.100.105 kernel: xenbr1: port 47(tap22) entering disabled state Sep 8 16:36:30 192.168.100.105 kernel: device tap22 left promiscuous mode Sep 8 16:36:30 192.168.100.105 kernel: xenbr1: port 47(tap22) entering disabled state Sep 8 16:36:31 192.168.100.105 kernel: device tap10 entered promiscuous mode Sep 8 16:36:31 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 16:36:31 192.168.100.105 kernel: xenbr1: port 23(tap10) entering forwarding state Sep 8 16:36:31 192.168.100.105 kernel: device vif42.0 entered promiscuous mode Sep 8 16:36:31 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif42.0: link is not ready Sep 8 16:36:32 192.168.100.105 avahi-daemon[4535]: New relevant interface tap10.IPv6 for mDNS. Sep 8 16:36:32 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap10.IPv6 with address fe80::3850:a3ff:fe4b:c0a7. Sep 8 16:36:32 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::3850:a3ff:fe4b:c0a7 on tap10. Sep 8 16:40:42 192.168.100.103 shutdown[442]: shutting down for system halt Sep 8 16:40:42 192.168.100.103 init: Switching to runlevel: 0 Sep 8 16:40:43 192.168.100.103 smartd[4592]: smartd received signal 15: Terminated Sep 8 16:40:43 192.168.100.103 smartd[4592]: smartd is exiting (exit status 0) Sep 8 16:40:43 192.168.100.103 avahi-daemon[4266]: Got SIGTERM, quitting. Sep 8 16:40:43 192.168.100.103 avahi-daemon[4266]: Leaving mDNS multicast group on interface eth3.IPv6 with address fe80::215:17ff:fec3:c169. Sep 8 16:40:43 192.168.100.103 avahi-daemon[4266]: Leaving mDNS multicast group on interface eth3.IPv4 with address 10.103.103.103. Sep 8 16:40:43 192.168.100.103 avahi-daemon[4266]: Leaving mDNS multicast group on interface eth2.IPv6 with address fe80::215:17ff:fec3:c168. Sep 8 16:40:43 192.168.100.103 avahi-daemon[4266]: Leaving mDNS multicast group on interface eth2.IPv4 with address 10.102.102.103. Sep 8 16:40:43 192.168.100.103 avahi-daemon[4266]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::230:48ff:fec5:4ad0. Sep 8 16:40:43 192.168.100.103 avahi-daemon[4266]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.100.103. Sep 8 16:40:46 192.168.100.102 shutdown[30865]: shutting down for system halt Sep 8 16:40:56 192.168.100.104 openais[4094]: [TOTEM] The token was lost in the OPERATIONAL state. Sep 8 16:40:56 192.168.100.104 openais[4094]: [TOTEM] Receive multicast socket recv buffer size (288000 bytes). Sep 8 16:40:56 192.168.100.104 openais[4094]: [TOTEM] Transmit multicast socket send buffer size (262142 bytes). Sep 8 16:40:56 192.168.100.104 openais[4094]: [TOTEM] entering GATHER state from 2. Sep 8 16:40:56 192.168.100.105 openais[4052]: [TOTEM] entering GATHER state from 12. Sep 8 16:40:56 192.168.100.101 openais[3853]: [TOTEM] entering GATHER state from 12. Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] entering GATHER state from 0. Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] entering GATHER state from 11. Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] entering GATHER state from 11. Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] Creating commit token because I am the rep. Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] Saving state aru a0 high seq received a0 Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] Storing new sequence id for ring 80 Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] entering COMMIT state. Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] Saving state aru a0 high seq received a0 Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] Storing new sequence id for ring 80 Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] entering COMMIT state. Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] Saving state aru a0 high seq received a0 Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] Storing new sequence id for ring 80 Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] entering COMMIT state. Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] entering RECOVERY state. Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 124 rep 10.103.103.101 Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] aru a0 high delivered a0 received flag 1 Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] position [1] member 10.103.103.104: Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 124 rep 10.103.103.101 Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] entering RECOVERY state. Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] aru a0 high delivered a0 received flag 1 Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] position [2] member 10.103.103.105: Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 124 rep 10.103.103.101 Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] aru a0 high delivered a0 received flag 1 Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 124 rep 10.103.103.101 Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] aru a0 high delivered a0 received flag 1 Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] position [1] member 10.103.103.104: Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 124 rep 10.103.103.101 Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] aru a0 high delivered a0 received flag 1 Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] position [2] member 10.103.103.105: Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 124 rep 10.103.103.101 Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] aru a0 high delivered a0 received flag 1 Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] Sending initial ORF token Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 16:41:01 192.168.100.104 openais[4094]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:41:01 192.168.100.104 openais[4094]: [TOTEM] entering OPERATIONAL state. Sep 8 16:41:01 192.168.100.105 kernel: dlm: closing connection to node 2 Sep 8 16:41:01 192.168.100.105 kernel: dlm: closing connection to node 3 Sep 8 16:41:01 192.168.100.104 kernel: dlm: closing connection to node 2 Sep 8 16:41:01 192.168.100.104 kernel: dlm: closing connection to node 3 Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 16:41:01 192.168.100.101 openais[3853]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:41:01 192.168.100.101 openais[3853]: [TOTEM] entering OPERATIONAL state. Sep 8 16:41:01 192.168.100.101 kernel: dlm: closing connection to node 2 Sep 8 16:41:01 192.168.100.101 kernel: dlm: closing connection to node 3 Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:41:01 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:41:01 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] entering RECOVERY state. Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 124 rep 10.103.103.101 Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] aru a0 high delivered a0 received flag 1 Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] position [1] member 10.103.103.104: Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 124 rep 10.103.103.101 Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] aru a0 high delivered a0 received flag 1 Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] position [2] member 10.103.103.105: Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 124 rep 10.103.103.101 Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] aru a0 high delivered a0 received flag 1 Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 16:41:01 192.168.100.105 openais[4052]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:41:01 192.168.100.105 openais[4052]: [TOTEM] entering OPERATIONAL state. Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:41:01 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:41:01 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 1 Sep 8 16:41:01 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 1 Sep 8 16:41:01 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 1 Sep 8 16:41:01 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 4 Sep 8 16:41:01 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 4 Sep 8 16:41:01 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 4 Sep 8 16:41:01 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 5 Sep 8 16:41:01 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 5 Sep 8 16:41:01 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 5 Sep 8 16:41:01 192.168.100.105 fenced[4075]: fencing deferred to xen1-cluster-if Sep 8 16:41:01 192.168.100.104 fenced[4118]: fencing deferred to xen1-cluster-if Sep 8 16:41:06 192.168.100.101 fenced[3873]: xen2-cluster-if not a cluster member after 5 sec post_fail_delay Sep 8 16:41:06 192.168.100.101 fenced[3873]: xen3-cluster-if not a cluster member after 5 sec post_fail_delay Sep 8 16:41:06 192.168.100.101 fenced[3873]: fencing node "xen2-cluster-if" Sep 8 16:41:06 192.168.100.101 fence_fibernet_cgi: http://pixie.fiber.net/cgi-bin/router-configurator.cgi?action=shutdown&router=bdr5.fbp.ore.fiber.net&port_ifDescr=GigabitEthernet9/9&redirect=no Sep 8 16:41:20 192.168.100.101 fence_fibernet_cgi: Fencing successful! Sep 8 16:41:20 192.168.100.101 fenced[3873]: fence "xen2-cluster-if" success Sep 8 16:41:20 192.168.100.101 fenced[3873]: fencing node "xen3-cluster-if" Sep 8 16:41:20 192.168.100.101 fence_fibernet_cgi: http://pixie.fiber.net/cgi-bin/router-configurator.cgi?action=shutdown&router=bdr5.fbp.ore.fiber.net&port_ifDescr=GigabitEthernet9/11&redirect=no Sep 8 16:41:34 pxe xinetd[16078]: START: tftp pid=29825 from=192.168.100.103 Sep 8 16:41:34 192.168.100.101 fence_fibernet_cgi: Fencing successful! Sep 8 16:41:34 192.168.100.101 fenced[3873]: fence "xen3-cluster-if" success Sep 8 16:42:04 192.168.100.105 kernel: xenbr1: port 36(vif18.0) entering disabled state Sep 8 16:42:04 192.168.100.105 kernel: device vif18.0 left promiscuous mode Sep 8 16:42:04 192.168.100.105 kernel: xenbr1: port 36(vif18.0) entering disabled state Sep 8 16:42:04 192.168.100.105 kernel: xenbr1: port 35(tap16) entering disabled state Sep 8 16:42:04 192.168.100.105 avahi-daemon[4535]: Interface tap16.IPv6 no longer relevant for mDNS. Sep 8 16:42:04 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap16.IPv6 with address fe80::34aa:66ff:fe36:f559. Sep 8 16:42:04 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::34aa:66ff:fe36:f559 on tap16. Sep 8 16:42:04 192.168.100.105 kernel: device tap16 left promiscuous mode Sep 8 16:42:04 192.168.100.105 kernel: xenbr1: port 35(tap16) entering disabled state Sep 8 16:42:05 pxe mountd[2162]: authenticated mount request from 192.168.100.103:875 for /opt/xen_5.3/root (/opt/xen_5.3/root) Sep 8 16:42:05 pxe mountd[2162]: authenticated mount request from 192.168.100.103:877 for /opt/xen_5.3/snapshot (/opt/xen_5.3/snapshot) Sep 8 16:42:05 192.168.100.105 kernel: device tap16 entered promiscuous mode Sep 8 16:42:05 192.168.100.105 kernel: xenbr1: topology change detected, propagating Sep 8 16:42:05 192.168.100.105 kernel: xenbr1: port 35(tap16) entering forwarding state Sep 8 16:42:06 192.168.100.105 kernel: device vif43.0 entered promiscuous mode Sep 8 16:42:06 192.168.100.105 kernel: ADDRCONF(NETDEV_UP): vif43.0: link is not ready Sep 8 16:42:07 192.168.100.105 avahi-daemon[4535]: New relevant interface tap16.IPv6 for mDNS. Sep 8 16:42:07 192.168.100.105 avahi-daemon[4535]: Joining mDNS multicast group on interface tap16.IPv6 with address fe80::8ff:12ff:fe17:e7f8. Sep 8 16:42:07 192.168.100.105 avahi-daemon[4535]: Registering new address record for fe80::8ff:12ff:fe17:e7f8 on tap16. Sep 8 16:42:12 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: fatal: invalid metadata block Sep 8 16:42:12 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: bh = 567447924 (magic number) Sep 8 16:42:12 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: function = gfs2_meta_indirect_buffer, file = fs/gfs2/meta_io.c, line = 334 Sep 8 16:42:12 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: about to withdraw this file system Sep 8 16:42:12 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: telling LM to withdraw Sep 8 16:42:12 192.168.100.105 logger: /etc/xen/scripts/block: losetup /dev/loop137 /xen/domains/2965-vps-28.heritagewebdesign.com/swap.img failed Sep 8 16:42:12 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=4: Trying to acquire journal lock... Sep 8 16:42:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:12 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=4: Busy Sep 8 16:42:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:12 192.168.100.105 kernel: GFS2: fsid=xencluster1:xenclusterfs1.4: withdrawn Sep 8 16:42:12 192.168.100.105 kernel: Sep 8 16:42:12 192.168.100.105 kernel: Call Trace: Sep 8 16:42:12 192.168.100.105 kernel: [] :gfs2:gfs2_lm_withdraw+0xc1/0xd0 Sep 8 16:42:12 192.168.100.105 kernel: [] __wait_on_bit+0x60/0x6e Sep 8 16:42:12 192.168.100.105 kernel: [] sync_buffer+0x0/0x3f Sep 8 16:42:12 192.168.100.105 kernel: [] :gfs2:glock_work_func+0x0/0xb8 Sep 8 16:42:12 192.168.100.105 kernel: [] out_of_line_wait_on_bit+0x6c/0x78 Sep 8 16:42:12 192.168.100.105 kernel: [] wake_bit_function+0x0/0x23 Sep 8 16:42:12 192.168.100.105 kernel: [] submit_bh+0x10a/0x111 Sep 8 16:42:12 192.168.100.105 kernel: [] :gfs2:gfs2_meta_check_ii+0x2c/0x38 Sep 8 16:42:12 192.168.100.105 kernel: [] :gfs2:gfs2_meta_indirect_buffer+0x104/0x160 Sep 8 16:42:12 192.168.100.105 kernel: [] __wake_up_common+0x3e/0x68 Sep 8 16:42:12 192.168.100.105 kernel: [] :gfs2:gfs2_inode_refresh+0x22/0x2cf Sep 8 16:42:12 192.168.100.105 kernel: [] :gfs2:inode_go_lock+0x44/0xbe Sep 8 16:42:12 192.168.100.105 kernel: [] :gfs2:do_promote+0xad/0x137 Sep 8 16:42:12 192.168.100.105 kernel: [] :gfs2:finish_xmote+0x28c/0x2b7 Sep 8 16:42:12 192.168.100.105 kernel: [] :gfs2:glock_work_func+0x1d/0xb8 Sep 8 16:42:12 192.168.100.105 kernel: [] run_workqueue+0x94/0xe4 Sep 8 16:42:12 192.168.100.105 kernel: [] worker_thread+0x0/0x122 Sep 8 16:42:12 192.168.100.105 kernel: [] keventd_create_kthread+0x0/0xc4 Sep 8 16:42:12 192.168.100.105 kernel: [] worker_thread+0xf0/0x122 Sep 8 16:42:12 192.168.100.105 kernel: [] default_wake_function+0x0/0xe Sep 8 16:42:12 192.168.100.105 kernel: [] keventd_create_kthread+0x0/0xc4 Sep 8 16:42:12 192.168.100.105 kernel: [] keventd_create_kthread+0x0/0xc4 Sep 8 16:42:12 192.168.100.105 kernel: [] kthread+0xfe/0x132 Sep 8 16:42:12 192.168.100.105 kernel: [] child_rip+0xa/0x12 Sep 8 16:42:12 192.168.100.105 kernel: [] keventd_create_kthread+0x0/0xc4 Sep 8 16:42:12 192.168.100.105 kernel: [] monotonic_clock+0x35/0x7b Sep 8 16:42:12 192.168.100.105 kernel: [] kthread+0x0/0x132 Sep 8 16:42:12 192.168.100.105 kernel: [] child_rip+0x0/0x12 Sep 8 16:42:12 192.168.100.105 kernel: Sep 8 16:42:12 192.168.100.105 avahi-daemon[4535]: Interface tap16.IPv6 no longer relevant for mDNS. Sep 8 16:42:12 192.168.100.105 avahi-daemon[4535]: Leaving mDNS multicast group on interface tap16.IPv6 with address fe80::8ff:12ff:fe17:e7f8. Sep 8 16:42:12 192.168.100.105 avahi-daemon[4535]: Withdrawing address record for fe80::8ff:12ff:fe17:e7f8 on tap16. Sep 8 16:42:12 192.168.100.105 kernel: xenbr1: port 35(tap16) entering disabled state Sep 8 16:42:12 192.168.100.105 kernel: device tap16 left promiscuous mode Sep 8 16:42:12 192.168.100.105 kernel: xenbr1: port 35(tap16) entering disabled state Sep 8 16:42:12 192.168.100.105 kernel: xenbr1: port 36(vif43.0) entering disabled state Sep 8 16:42:12 192.168.100.105 kernel: device vif43.0 left promiscuous mode Sep 8 16:42:12 192.168.100.105 kernel: xenbr1: port 36(vif43.0) entering disabled state Sep 8 16:42:13 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=4: Trying to acquire journal lock... Sep 8 16:42:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:13 192.168.100.105 logger: /etc/xen/scripts/block: xenstore-read backend/vbd/43/832/node failed. Sep 8 16:42:13 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=4: Looking at journal... Sep 8 16:42:13 192.168.100.105 logger: /etc/xen/scripts/block: /etc/xen/scripts/block failed; error detected. Sep 8 16:42:13 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=4: Acquiring the transaction lock... Sep 8 16:42:13 192.168.100.101 kernel: lock_dlm: gdlm_cancel 1,2 flags 0 Sep 8 16:42:13 192.168.100.101 kernel: lock_dlm: gdlm_cancel skip 1,2 flags 0 Sep 8 16:42:13 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: jid=4: Replaying journal... Sep 8 16:42:13 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: fatal: invalid metadata block Sep 8 16:42:13 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: bh = 143515 (type: exp=9, found=4) Sep 8 16:42:13 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: function = foreach_descriptor, file = fs/gfs2/recovery.c, line = 350 Sep 8 16:42:13 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: about to withdraw this file system Sep 8 16:42:13 192.168.100.101 kernel: GFS2: fsid=xencluster1:xenclusterfs1.2: telling LM to withdraw Sep 8 16:42:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:16 pxe mountd[2162]: authenticated mount request from 192.168.100.102:876 for /opt/xen_5.3/root (/opt/xen_5.3/root) Sep 8 16:42:16 pxe mountd[2162]: authenticated mount request from 192.168.100.102:878 for /opt/xen_5.3/snapshot (/opt/xen_5.3/snapshot) Sep 8 16:42:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:24 192.168.100.103 syslogd 1.4.1: restart. Sep 8 16:42:24 192.168.100.103 kernel: klogd 1.4.1, log source = /proc/kmsg started. Sep 8 16:42:24 192.168.100.103 kernel: Bootdata ok (command line is root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen3 ) Sep 8 16:42:24 192.168.100.103 kernel: Linux version 2.6.18-128.1.6.el5xen (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Apr 1 09:53:14 EDT 2009 Sep 8 16:42:24 192.168.100.103 kernel: BIOS-provided physical RAM map: Sep 8 16:42:24 192.168.100.103 kernel: Xen: 0000000000000000 - 00000000a0800000 (usable) Sep 8 16:42:24 192.168.100.103 kernel: DMI present. Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x04] enabled) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] enabled) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x06] enabled) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) Sep 8 16:42:24 192.168.100.103 kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24]) Sep 8 16:42:24 192.168.100.103 kernel: IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Sep 8 16:42:24 192.168.100.103 kernel: Setting APIC routing to xen Sep 8 16:42:24 192.168.100.103 kernel: Using ACPI (MADT) for SMP configuration information Sep 8 16:42:24 192.168.100.103 kernel: Allocating PCI resources starting at d1000000 (gap: d0000000:10000000) Sep 8 16:42:24 192.168.100.103 kernel: Built 1 zonelists. Total pages: 657408 Sep 8 16:42:24 192.168.100.103 kernel: Kernel command line: root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen3 Sep 8 16:42:24 192.168.100.103 kernel: Initializing CPU#0 Sep 8 16:42:24 192.168.100.103 kernel: PID hash table entries: 4096 (order: 12, 32768 bytes) Sep 8 16:42:24 192.168.100.103 kernel: Xen reported: 2000.066 MHz processor. Sep 8 16:42:24 192.168.100.103 kernel: Console: colour VGA+ 80x25 Sep 8 16:42:24 192.168.100.103 kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Sep 8 16:42:24 192.168.100.103 kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Sep 8 16:42:24 192.168.100.103 kernel: Software IO TLB enabled: Sep 8 16:42:24 192.168.100.103 kernel: Aperture: 64 megabytes Sep 8 16:42:24 192.168.100.103 kernel: Kernel range: 0xffff8800057c5000 - 0xffff8800097c5000 Sep 8 16:42:24 192.168.100.103 kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Sep 8 16:42:24 192.168.100.103 kernel: Memory: 2467584k/2629632k available (2447k kernel code, 153292k reserved, 1366k data, 180k init) Sep 8 16:42:24 192.168.100.103 kernel: Calibrating delay using timer specific routine.. 5004.03 BogoMIPS (lpj=10008074) Sep 8 16:42:24 192.168.100.103 kernel: Security Framework v1.0.0 initialized Sep 8 16:42:24 192.168.100.103 kernel: SELinux: Initializing. Sep 8 16:42:24 192.168.100.103 kernel: selinux_register_security: Registering secondary module capability Sep 8 16:42:24 192.168.100.103 kernel: Capability LSM initialized as secondary Sep 8 16:42:24 192.168.100.103 kernel: Mount-cache hash table entries: 256 Sep 8 16:42:24 192.168.100.103 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Sep 8 16:42:24 192.168.100.103 kernel: CPU: L2 cache: 6144K Sep 8 16:42:24 192.168.100.103 kernel: CPU: Physical Processor ID: 0 Sep 8 16:42:24 192.168.100.103 kernel: CPU: Processor Core ID: 0 Sep 8 16:42:24 192.168.100.103 kernel: (SMP-)alternatives turned off Sep 8 16:42:24 192.168.100.103 kernel: ACPI: Core revision 20060707 Sep 8 16:42:24 192.168.100.103 kernel: Initializing CPU#1 Sep 8 16:42:24 192.168.100.103 kernel: Initializing CPU#2 Sep 8 16:42:24 192.168.100.103 kernel: Initializing CPU#3 Sep 8 16:42:24 192.168.100.103 kernel: Initializing CPU#4 Sep 8 16:42:24 192.168.100.103 kernel: Initializing CPU#5 Sep 8 16:42:24 192.168.100.103 kernel: Initializing CPU#6 Sep 8 16:42:24 192.168.100.103 kernel: Brought up 8 CPUs Sep 8 16:42:24 192.168.100.103 kernel: Initializing CPU#7 Sep 8 16:42:24 192.168.100.103 kernel: migration_cost=13155 Sep 8 16:42:24 192.168.100.103 kernel: checking if image is initramfs... it is Sep 8 16:42:24 192.168.100.103 kernel: Grant table initialized Sep 8 16:42:24 192.168.100.103 kernel: NET: Registered protocol family 16 Sep 8 16:42:24 192.168.100.103 kernel: No dock devices found. Sep 8 16:42:24 192.168.100.103 kernel: ACPI: bus type pci registered Sep 8 16:42:24 192.168.100.103 kernel: PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved Sep 8 16:42:24 192.168.100.103 kernel: PCI: Not using MMCONFIG. Sep 8 16:42:24 192.168.100.103 kernel: PCI: Using configuration type 1 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: Interpreter enabled Sep 8 16:42:24 192.168.100.103 kernel: ACPI: Using IOAPIC for interrupt routing Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Root Bridge [PCI0] (0000:00) Sep 8 16:42:24 192.168.100.103 kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 Sep 8 16:42:24 192.168.100.103 kernel: PCI: Transparent bridge - 0000:00:1e.0 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 *7 10 11 14 15) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 14 15) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 14 15) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 14 15) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:42:24 192.168.100.103 kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Sep 8 16:42:24 192.168.100.103 kernel: pnp: PnP ACPI init Sep 8 16:42:24 192.168.100.103 kernel: pnp: PnP ACPI: found 12 devices Sep 8 16:42:24 192.168.100.103 kernel: xen_mem: Initialising balloon driver. Sep 8 16:42:24 192.168.100.103 kernel: usbcore: registered new driver usbfs Sep 8 16:42:24 192.168.100.103 kernel: usbcore: registered new driver hub Sep 8 16:42:24 192.168.100.103 kernel: PCI: Using ACPI for IRQ routing Sep 8 16:42:24 192.168.100.103 kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Sep 8 16:42:24 192.168.100.103 kernel: NetLabel: Initializing Sep 8 16:42:24 192.168.100.103 kernel: NetLabel: domain hash size = 128 Sep 8 16:42:24 192.168.100.103 kernel: NetLabel: protocols = UNLABELED CIPSOv4 Sep 8 16:42:24 192.168.100.103 kernel: NetLabel: unlabeled traffic allowed by default Sep 8 16:42:24 192.168.100.103 kernel: PCI: Bridge: 0000:02:00.0 Sep 8 16:42:24 192.168.100.103 kernel: IO window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: MEM window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: PREFETCH window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: PCI: Bridge: 0000:02:01.0 Sep 8 16:42:24 192.168.100.103 kernel: IO window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: MEM window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: PREFETCH window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: PCI: Bridge: 0000:02:02.0 Sep 8 16:42:24 192.168.100.103 kernel: IO window: 2000-2fff Sep 8 16:42:24 192.168.100.103 kernel: MEM window: d8000000-d80fffff Sep 8 16:42:24 192.168.100.103 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:42:24 192.168.100.103 kernel: PCI: Bridge: 0000:01:00.0 Sep 8 16:42:24 192.168.100.103 kernel: IO window: 2000-2fff Sep 8 16:42:24 192.168.100.103 kernel: MEM window: d8000000-d80fffff Sep 8 16:42:24 192.168.100.103 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:42:24 192.168.100.103 kernel: PCI: Bridge: 0000:01:00.3 Sep 8 16:42:24 192.168.100.103 kernel: IO window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: MEM window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: PREFETCH window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: PCI: Bridge: 0000:00:02.0 Sep 8 16:42:24 192.168.100.103 kernel: IO window: 2000-2fff Sep 8 16:42:24 192.168.100.103 kernel: MEM window: d8000000-d81fffff Sep 8 16:42:24 192.168.100.103 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:42:24 192.168.100.103 kernel: PCI: Bridge: 0000:00:04.0 Sep 8 16:42:24 192.168.100.103 kernel: IO window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: MEM window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: PREFETCH window: disabled. Sep 8 16:42:24 192.168.100.103 kernel: PCI: Bridge: 0000:00:06.0 Sep 8 16:42:24 192.168.100.103 kernel: IO window: 3000-3fff Sep 8 16:42:24 192.168.100.103 kernel: MEM window: d8200000-d82fffff Sep 8 16:42:24 192.168.100.103 kernel: PREFETCH window: d8500000-d85fffff Sep 8 16:42:24 192.168.100.103 kernel: PCI: Bridge: 0000:00:1e.0 Sep 8 16:42:24 192.168.100.103 kernel: IO window: 4000-4fff Sep 8 16:42:24 192.168.100.103 kernel: MEM window: d8300000-d83fffff Sep 8 16:42:24 192.168.100.103 kernel: PREFETCH window: d0000000-d7ffffff Sep 8 16:42:24 192.168.100.103 kernel: GSI 16 sharing vector 0xA0 and IRQ 16 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:42:24 192.168.100.103 kernel: GSI 17 sharing vector 0xA8 and IRQ 17 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 16:42:24 192.168.100.103 kernel: GSI 18 sharing vector 0xB0 and IRQ 18 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:42:24 192.168.100.103 kernel: NET: Registered protocol family 2 Sep 8 16:42:24 192.168.100.103 kernel: IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) Sep 8 16:42:24 192.168.100.103 kernel: TCP established hash table entries: 262144 (order: 10, 4194304 bytes) Sep 8 16:42:24 192.168.100.103 kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) Sep 8 16:42:24 192.168.100.103 kernel: TCP: Hash tables configured (established 262144 bind 65536) Sep 8 16:42:24 192.168.100.103 kernel: TCP reno registered Sep 8 16:42:24 192.168.100.103 kernel: Simple Boot Flag at 0x38 set to 0x1 Sep 8 16:42:24 192.168.100.103 kernel: audit: initializing netlink socket (disabled) Sep 8 16:42:24 192.168.100.103 kernel: type=2000 audit(1252428113.340:1): initialized Sep 8 16:42:24 192.168.100.103 kernel: VFS: Disk quotas dquot_6.5.1 Sep 8 16:42:24 192.168.100.103 kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Sep 8 16:42:24 192.168.100.103 kernel: Initializing Cryptographic API Sep 8 16:42:24 192.168.100.103 kernel: alg: No test for crc32c (crc32c-generic) Sep 8 16:42:24 192.168.100.103 kernel: ksign: Installing public key data Sep 8 16:42:24 192.168.100.103 kernel: Loading keyring Sep 8 16:42:24 192.168.100.103 kernel: - Added public key 5535842996BF3A42 Sep 8 16:42:24 192.168.100.103 kernel: - User ID: CentOS (Kernel Module GPG key) Sep 8 16:42:24 192.168.100.103 kernel: io scheduler noop registered Sep 8 16:42:24 192.168.100.103 kernel: io scheduler anticipatory registered Sep 8 16:42:24 192.168.100.103 kernel: io scheduler deadline registered Sep 8 16:42:24 192.168.100.103 kernel: io scheduler cfq registered (default) Sep 8 16:42:24 192.168.100.103 kernel: assign_interrupt_mode Found MSI capability Sep 8 16:42:24 192.168.100.103 kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: Processor [CPU0] (supports 8 throttling states) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: Processor [CPU1] (supports 8 throttling states) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: Processor [CPU2] (supports 8 throttling states) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: Processor [CPU3] (supports 8 throttling states) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: Processor [CPU4] (supports 8 throttling states) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: Processor [CPU5] (supports 8 throttling states) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: Processor [CPU6] (supports 8 throttling states) Sep 8 16:42:24 192.168.100.103 kernel: ACPI: Processor [CPU7] (supports 8 throttling states) Sep 8 16:42:24 192.168.100.103 kernel: Real Time Clock Driver v1.12ac Sep 8 16:42:24 192.168.100.103 kernel: Non-volatile memory driver v1.2 Sep 8 16:42:24 192.168.100.103 kernel: Linux agpgart interface v0.101 (c) Dave Jones Sep 8 16:42:24 192.168.100.103 kernel: RAMDISK driver initialized: 16 RAM disks of 26403K size 4096 blocksize Sep 8 16:42:24 192.168.100.103 kernel: Xen virtual console successfully installed as ttyS0 Sep 8 16:42:24 192.168.100.103 kernel: Event-channel device installed. Sep 8 16:42:24 192.168.100.103 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Sep 8 16:42:24 192.168.100.103 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Sep 8 16:42:24 192.168.100.103 kernel: ESB2: IDE controller at PCI slot 0000:00:1f.1 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:42:24 192.168.100.103 kernel: ESB2: chipset revision 9 Sep 8 16:42:24 192.168.100.103 kernel: ESB2: not 100% native mode: will probe irqs later Sep 8 16:42:24 192.168.100.103 kernel: ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:pio, hdb:DMA Sep 8 16:42:24 192.168.100.103 kernel: hdb: DVD-ROM UJDA780, ATAPI CD/DVD-ROM drive Sep 8 16:42:24 192.168.100.103 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Sep 8 16:42:24 192.168.100.103 kernel: ide-floppy driver 0.99.newide Sep 8 16:42:24 192.168.100.103 kernel: usbcore: registered new driver hiddev Sep 8 16:42:24 192.168.100.103 kernel: usbcore: registered new driver usbhid Sep 8 16:42:24 192.168.100.103 kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver Sep 8 16:42:24 192.168.100.103 kernel: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12 Sep 8 16:42:24 192.168.100.103 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Sep 8 16:42:24 192.168.100.103 kernel: mice: PS/2 mouse device common for all mice Sep 8 16:42:24 192.168.100.103 kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 Sep 8 16:42:24 192.168.100.103 kernel: md: bitmap version 4.39 Sep 8 16:42:24 192.168.100.103 kernel: TCP bic registered Sep 8 16:42:24 192.168.100.103 kernel: Initializing IPsec netlink socket Sep 8 16:42:24 192.168.100.103 kernel: NET: Registered protocol family 1 Sep 8 16:42:24 192.168.100.103 kernel: NET: Registered protocol family 17 Sep 8 16:42:24 192.168.100.103 kernel: Write protecting the kernel read-only data: 467k Sep 8 16:42:24 192.168.100.103 kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 Sep 8 16:42:24 192.168.100.103 kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation. Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:42:24 192.168.100.103 kernel: 0000:05:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:42:24 192.168.100.103 kernel: eth0: (PCI Express:2.5GB/s:Width x4) 00:30:48:c5:4a:d0 Sep 8 16:42:24 192.168.100.103 kernel: eth0: Intel(R) PRO/1000 Network Connection Sep 8 16:42:24 192.168.100.103 kernel: eth0: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 16:42:24 192.168.100.103 kernel: GSI 19 sharing vector 0xB8 and IRQ 19 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:05:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 16:42:24 192.168.100.103 kernel: 0000:05:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:42:24 192.168.100.103 kernel: eth1: (PCI Express:2.5GB/s:Width x4) 00:30:48:c5:4a:d1 Sep 8 16:42:24 192.168.100.103 kernel: eth1: Intel(R) PRO/1000 Network Connection Sep 8 16:42:24 192.168.100.103 kernel: eth1: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:08:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:42:24 192.168.100.103 kernel: 0000:08:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:42:24 192.168.100.103 kernel: eth2: (PCI Express:2.5GB/s:Width x4) 00:15:17:c3:c1:68 Sep 8 16:42:24 192.168.100.103 kernel: eth2: Intel(R) PRO/1000 Network Connection Sep 8 16:42:24 192.168.100.103 kernel: eth2: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:08:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 16:42:24 192.168.100.103 kernel: 0000:08:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:42:24 192.168.100.103 kernel: eth3: (PCI Express:2.5GB/s:Width x4) 00:15:17:c3:c1:69 Sep 8 16:42:24 192.168.100.103 kernel: eth3: Intel(R) PRO/1000 Network Connection Sep 8 16:42:24 192.168.100.103 kernel: eth3: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 16:42:24 192.168.100.103 kernel: FS-Cache: Loaded Sep 8 16:42:24 192.168.100.103 kernel: eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 8 16:42:24 192.168.100.103 kernel: NET: Registered protocol family 10 Sep 8 16:42:24 192.168.100.103 kernel: lo: Disabled Privacy Extensions Sep 8 16:42:24 192.168.100.103 kernel: IPv6 over IPv4 tunneling driver Sep 8 16:42:24 192.168.100.103 kernel: SELinux: Disabled at runtime. Sep 8 16:42:24 192.168.100.103 kernel: type=1404 audit(1252428126.817:2): selinux=0 auid=4294967295 ses=4294967295 Sep 8 16:42:24 192.168.100.103 kernel: intel_rng: FWH not detected Sep 8 16:42:24 192.168.100.103 kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Sep 8 16:42:24 192.168.100.103 kernel: EDAC MC: Ver: 2.0.1 Apr 1 2009 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 16:42:24 192.168.100.103 kernel: EDAC MC0: Giving out device to i5000_edac.c I5000: DEV 0000:00:10.0 Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 16:42:24 192.168.100.103 kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller Sep 8 16:42:24 192.168.100.103 kernel: ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 Sep 8 16:42:24 192.168.100.103 kernel: ehci_hcd 0000:00:1d.7: debug port 1 Sep 8 16:42:24 192.168.100.103 kernel: ehci_hcd 0000:00:1d.7: irq 17, io mem 0xd8600000 Sep 8 16:42:24 192.168.100.103 kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 Sep 8 16:42:24 192.168.100.103 kernel: usb usb1: configuration #1 chosen from 1 choice Sep 8 16:42:24 192.168.100.103 kernel: hub 1-0:1.0: USB hub found Sep 8 16:42:24 192.168.100.103 kernel: hub 1-0:1.0: 6 ports detected Sep 8 16:42:24 192.168.100.103 kernel: hdb: ATAPI 24X DVD-ROM drive, 2048kB Cache, UDMA(33) Sep 8 16:42:24 192.168.100.103 kernel: Uniform CD-ROM driver Revision: 3.20 Sep 8 16:42:24 192.168.100.103 kernel: input: PC Speaker as /class/input/input0 Sep 8 16:42:24 192.168.100.103 kernel: USB Universal Host Controller Interface driver v3.0 Sep 8 16:42:24 192.168.100.103 kernel: hub 2-0:1.0: 2 ports detected Sep 8 16:42:24 192.168.100.103 kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:42:24 192.168.100.103 kernel: FDC 0 is a post-1991 82077 Sep 8 16:42:24 192.168.100.103 kernel: iscsi: registered transport (iser) Sep 8 16:42:24 192.168.100.103 kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready Sep 8 16:42:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:28 192.168.100.103 iscsid: connect failed (113) Sep 8 16:42:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:31 192.168.100.103 iscsid: connect failed (113) Sep 8 16:42:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:34 192.168.100.103 iscsid: connect failed (113) Sep 8 16:42:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:35 192.168.100.102 syslogd 1.4.1: restart. Sep 8 16:42:35 192.168.100.102 kernel: klogd 1.4.1, log source = /proc/kmsg started. Sep 8 16:42:35 192.168.100.102 kernel: Bootdata ok (command line is root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen2 ) Sep 8 16:42:35 192.168.100.102 kernel: Linux version 2.6.18-128.1.6.el5xen (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Apr 1 09:53:14 EDT 2009 Sep 8 16:42:35 192.168.100.102 kernel: BIOS-provided physical RAM map: Sep 8 16:42:35 192.168.100.102 kernel: Xen: 0000000000000000 - 00000000a0800000 (usable) Sep 8 16:42:35 192.168.100.102 kernel: DMI present. Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x04] enabled) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] enabled) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x06] enabled) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) Sep 8 16:42:35 192.168.100.102 kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24]) Sep 8 16:42:35 192.168.100.102 kernel: IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Sep 8 16:42:35 192.168.100.102 kernel: Setting APIC routing to xen Sep 8 16:42:35 192.168.100.102 kernel: Using ACPI (MADT) for SMP configuration information Sep 8 16:42:35 192.168.100.102 kernel: Allocating PCI resources starting at d1000000 (gap: d0000000:10000000) Sep 8 16:42:35 192.168.100.102 kernel: Built 1 zonelists. Total pages: 657408 Sep 8 16:42:35 192.168.100.102 kernel: Kernel command line: root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen2 Sep 8 16:42:35 192.168.100.102 kernel: Initializing CPU#0 Sep 8 16:42:35 192.168.100.102 kernel: PID hash table entries: 4096 (order: 12, 32768 bytes) Sep 8 16:42:35 192.168.100.102 kernel: Xen reported: 1866.729 MHz processor. Sep 8 16:42:35 192.168.100.102 kernel: Console: colour VGA+ 80x25 Sep 8 16:42:35 192.168.100.102 kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Sep 8 16:42:35 192.168.100.102 kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Sep 8 16:42:35 192.168.100.102 kernel: Software IO TLB enabled: Sep 8 16:42:35 192.168.100.102 kernel: Aperture: 64 megabytes Sep 8 16:42:35 192.168.100.102 kernel: Kernel range: 0xffff8800057c5000 - 0xffff8800097c5000 Sep 8 16:42:35 192.168.100.102 kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Sep 8 16:42:35 192.168.100.102 kernel: Memory: 2467584k/2629632k available (2447k kernel code, 153292k reserved, 1366k data, 180k init) Sep 8 16:42:35 192.168.100.102 kernel: Calibrating delay using timer specific routine.. 4669.58 BogoMIPS (lpj=9339167) Sep 8 16:42:35 192.168.100.102 kernel: Security Framework v1.0.0 initialized Sep 8 16:42:35 192.168.100.102 kernel: SELinux: Initializing. Sep 8 16:42:35 192.168.100.102 kernel: selinux_register_security: Registering secondary module capability Sep 8 16:42:35 192.168.100.102 kernel: Capability LSM initialized as secondary Sep 8 16:42:35 192.168.100.102 kernel: Mount-cache hash table entries: 256 Sep 8 16:42:35 192.168.100.102 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Sep 8 16:42:35 192.168.100.102 kernel: CPU: L2 cache: 4096K Sep 8 16:42:35 192.168.100.102 kernel: CPU: Physical Processor ID: 0 Sep 8 16:42:35 192.168.100.102 kernel: CPU: Processor Core ID: 0 Sep 8 16:42:35 192.168.100.102 kernel: (SMP-)alternatives turned off Sep 8 16:42:35 192.168.100.102 kernel: ACPI: Core revision 20060707 Sep 8 16:42:35 192.168.100.102 kernel: Initializing CPU#1 Sep 8 16:42:35 192.168.100.102 kernel: Initializing CPU#2 Sep 8 16:42:35 192.168.100.102 kernel: Initializing CPU#3 Sep 8 16:42:35 192.168.100.102 kernel: Initializing CPU#4 Sep 8 16:42:35 192.168.100.102 kernel: Initializing CPU#5 Sep 8 16:42:35 192.168.100.102 kernel: Initializing CPU#6 Sep 8 16:42:35 192.168.100.102 kernel: Brought up 8 CPUs Sep 8 16:42:35 192.168.100.102 kernel: Initializing CPU#7 Sep 8 16:42:35 192.168.100.102 kernel: migration_cost=6583 Sep 8 16:42:35 192.168.100.102 kernel: checking if image is initramfs... it is Sep 8 16:42:35 192.168.100.102 kernel: Grant table initialized Sep 8 16:42:35 192.168.100.102 kernel: NET: Registered protocol family 16 Sep 8 16:42:35 192.168.100.102 kernel: No dock devices found. Sep 8 16:42:35 192.168.100.102 kernel: ACPI: bus type pci registered Sep 8 16:42:35 192.168.100.102 kernel: PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved Sep 8 16:42:35 192.168.100.102 kernel: PCI: Not using MMCONFIG. Sep 8 16:42:35 192.168.100.102 kernel: PCI: Using configuration type 1 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: Interpreter enabled Sep 8 16:42:35 192.168.100.102 kernel: ACPI: Using IOAPIC for interrupt routing Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Root Bridge [PCI0] (0000:00) Sep 8 16:42:35 192.168.100.102 kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 Sep 8 16:42:35 192.168.100.102 kernel: PCI: Transparent bridge - 0000:00:1e.0 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 *7 10 11 14 15) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 14 15) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 14 15) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 14 15) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:42:35 192.168.100.102 kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Sep 8 16:42:35 192.168.100.102 kernel: pnp: PnP ACPI init Sep 8 16:42:35 192.168.100.102 kernel: pnp: PnP ACPI: found 12 devices Sep 8 16:42:35 192.168.100.102 kernel: xen_mem: Initialising balloon driver. Sep 8 16:42:35 192.168.100.102 kernel: usbcore: registered new driver usbfs Sep 8 16:42:35 192.168.100.102 kernel: usbcore: registered new driver hub Sep 8 16:42:35 192.168.100.102 kernel: PCI: Using ACPI for IRQ routing Sep 8 16:42:35 192.168.100.102 kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Sep 8 16:42:35 192.168.100.102 kernel: NetLabel: Initializing Sep 8 16:42:35 192.168.100.102 kernel: NetLabel: domain hash size = 128 Sep 8 16:42:35 192.168.100.102 kernel: NetLabel: protocols = UNLABELED CIPSOv4 Sep 8 16:42:35 192.168.100.102 kernel: NetLabel: unlabeled traffic allowed by default Sep 8 16:42:35 192.168.100.102 kernel: PCI: Bridge: 0000:02:00.0 Sep 8 16:42:35 192.168.100.102 kernel: IO window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: MEM window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: PREFETCH window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: PCI: Bridge: 0000:02:01.0 Sep 8 16:42:35 192.168.100.102 kernel: IO window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: MEM window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: PREFETCH window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: PCI: Bridge: 0000:02:02.0 Sep 8 16:42:35 192.168.100.102 kernel: IO window: 2000-2fff Sep 8 16:42:35 192.168.100.102 kernel: MEM window: d8000000-d80fffff Sep 8 16:42:35 192.168.100.102 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:42:35 192.168.100.102 kernel: PCI: Bridge: 0000:01:00.0 Sep 8 16:42:35 192.168.100.102 kernel: IO window: 2000-2fff Sep 8 16:42:35 192.168.100.102 kernel: MEM window: d8000000-d80fffff Sep 8 16:42:35 192.168.100.102 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:42:35 192.168.100.102 kernel: PCI: Bridge: 0000:01:00.3 Sep 8 16:42:35 192.168.100.102 kernel: IO window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: MEM window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: PREFETCH window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: PCI: Bridge: 0000:00:02.0 Sep 8 16:42:35 192.168.100.102 kernel: IO window: 2000-2fff Sep 8 16:42:35 192.168.100.102 kernel: MEM window: d8000000-d81fffff Sep 8 16:42:35 192.168.100.102 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:42:35 192.168.100.102 kernel: PCI: Bridge: 0000:00:04.0 Sep 8 16:42:35 192.168.100.102 kernel: IO window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: MEM window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: PREFETCH window: disabled. Sep 8 16:42:35 192.168.100.102 kernel: PCI: Bridge: 0000:00:06.0 Sep 8 16:42:35 192.168.100.102 kernel: IO window: 3000-3fff Sep 8 16:42:35 192.168.100.102 kernel: MEM window: d8200000-d82fffff Sep 8 16:42:35 192.168.100.102 kernel: PREFETCH window: d8500000-d85fffff Sep 8 16:42:35 192.168.100.102 kernel: PCI: Bridge: 0000:00:1e.0 Sep 8 16:42:35 192.168.100.102 kernel: IO window: 4000-4fff Sep 8 16:42:35 192.168.100.102 kernel: MEM window: d8300000-d83fffff Sep 8 16:42:35 192.168.100.102 kernel: PREFETCH window: d0000000-d7ffffff Sep 8 16:42:35 192.168.100.102 kernel: GSI 16 sharing vector 0xA0 and IRQ 16 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:42:35 192.168.100.102 kernel: GSI 17 sharing vector 0xA8 and IRQ 17 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 16:42:35 192.168.100.102 kernel: GSI 18 sharing vector 0xB0 and IRQ 18 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:42:35 192.168.100.102 kernel: NET: Registered protocol family 2 Sep 8 16:42:35 192.168.100.102 kernel: IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) Sep 8 16:42:35 192.168.100.102 kernel: TCP established hash table entries: 262144 (order: 10, 4194304 bytes) Sep 8 16:42:35 192.168.100.102 kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) Sep 8 16:42:35 192.168.100.102 kernel: TCP: Hash tables configured (established 262144 bind 65536) Sep 8 16:42:35 192.168.100.102 kernel: TCP reno registered Sep 8 16:42:35 192.168.100.102 kernel: Simple Boot Flag at 0x38 set to 0x1 Sep 8 16:42:35 192.168.100.102 kernel: audit: initializing netlink socket (disabled) Sep 8 16:42:35 192.168.100.102 kernel: type=2000 audit(1252428128.892:1): initialized Sep 8 16:42:35 192.168.100.102 kernel: VFS: Disk quotas dquot_6.5.1 Sep 8 16:42:35 192.168.100.102 kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Sep 8 16:42:35 192.168.100.102 kernel: Initializing Cryptographic API Sep 8 16:42:35 192.168.100.102 kernel: alg: No test for crc32c (crc32c-generic) Sep 8 16:42:35 192.168.100.102 kernel: ksign: Installing public key data Sep 8 16:42:35 192.168.100.102 kernel: Loading keyring Sep 8 16:42:35 192.168.100.102 kernel: - Added public key 5535842996BF3A42 Sep 8 16:42:35 192.168.100.102 kernel: - User ID: CentOS (Kernel Module GPG key) Sep 8 16:42:35 192.168.100.102 kernel: io scheduler noop registered Sep 8 16:42:35 192.168.100.102 kernel: io scheduler anticipatory registered Sep 8 16:42:35 192.168.100.102 kernel: io scheduler deadline registered Sep 8 16:42:35 192.168.100.102 kernel: io scheduler cfq registered (default) Sep 8 16:42:35 192.168.100.102 kernel: assign_interrupt_mode Found MSI capability Sep 8 16:42:35 192.168.100.102 kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: Processor [CPU0] (supports 8 throttling states) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: Processor [CPU1] (supports 8 throttling states) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: Processor [CPU2] (supports 8 throttling states) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: Processor [CPU3] (supports 8 throttling states) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: Processor [CPU4] (supports 8 throttling states) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: Processor [CPU5] (supports 8 throttling states) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: Processor [CPU6] (supports 8 throttling states) Sep 8 16:42:35 192.168.100.102 kernel: ACPI: Processor [CPU7] (supports 8 throttling states) Sep 8 16:42:35 192.168.100.102 kernel: Real Time Clock Driver v1.12ac Sep 8 16:42:35 192.168.100.102 kernel: Non-volatile memory driver v1.2 Sep 8 16:42:35 192.168.100.102 kernel: Linux agpgart interface v0.101 (c) Dave Jones Sep 8 16:42:35 192.168.100.102 kernel: RAMDISK driver initialized: 16 RAM disks of 26403K size 4096 blocksize Sep 8 16:42:35 192.168.100.102 kernel: Xen virtual console successfully installed as ttyS0 Sep 8 16:42:35 192.168.100.102 kernel: Event-channel device installed. Sep 8 16:42:35 192.168.100.102 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Sep 8 16:42:35 192.168.100.102 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Sep 8 16:42:35 192.168.100.102 kernel: ESB2: IDE controller at PCI slot 0000:00:1f.1 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:42:35 192.168.100.102 kernel: ESB2: chipset revision 9 Sep 8 16:42:35 192.168.100.102 kernel: ESB2: not 100% native mode: will probe irqs later Sep 8 16:42:35 192.168.100.102 kernel: ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:pio, hdb:DMA Sep 8 16:42:35 192.168.100.102 kernel: hdb: DVD-ROM UJDA780, ATAPI CD/DVD-ROM drive Sep 8 16:42:35 192.168.100.102 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Sep 8 16:42:35 192.168.100.102 kernel: ide-floppy driver 0.99.newide Sep 8 16:42:35 192.168.100.102 kernel: usbcore: registered new driver hiddev Sep 8 16:42:35 192.168.100.102 kernel: usbcore: registered new driver usbhid Sep 8 16:42:35 192.168.100.102 kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver Sep 8 16:42:35 192.168.100.102 kernel: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12 Sep 8 16:42:35 192.168.100.102 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Sep 8 16:42:35 192.168.100.102 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Sep 8 16:42:35 192.168.100.102 kernel: mice: PS/2 mouse device common for all mice Sep 8 16:42:35 192.168.100.102 kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 Sep 8 16:42:35 192.168.100.102 kernel: md: bitmap version 4.39 Sep 8 16:42:35 192.168.100.102 kernel: TCP bic registered Sep 8 16:42:35 192.168.100.102 kernel: Initializing IPsec netlink socket Sep 8 16:42:35 192.168.100.102 kernel: NET: Registered protocol family 1 Sep 8 16:42:35 192.168.100.102 kernel: NET: Registered protocol family 17 Sep 8 16:42:35 192.168.100.102 kernel: Write protecting the kernel read-only data: 467k Sep 8 16:42:35 192.168.100.102 kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 Sep 8 16:42:35 192.168.100.102 kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation. Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:42:35 192.168.100.102 kernel: 0000:05:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:42:35 192.168.100.102 kernel: eth0: (PCI Express:2.5GB/s:Width x4) 00:30:48:c1:36:cc Sep 8 16:42:35 192.168.100.102 kernel: eth0: Intel(R) PRO/1000 Network Connection Sep 8 16:42:35 192.168.100.102 kernel: eth0: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 16:42:35 192.168.100.102 kernel: GSI 19 sharing vector 0xB8 and IRQ 19 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:05:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 16:42:35 192.168.100.102 kernel: 0000:05:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:42:35 192.168.100.102 kernel: eth1: (PCI Express:2.5GB/s:Width x4) 00:30:48:c1:36:cd Sep 8 16:42:35 192.168.100.102 kernel: eth1: Intel(R) PRO/1000 Network Connection Sep 8 16:42:35 192.168.100.102 kernel: eth1: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:08:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:42:35 192.168.100.102 kernel: 0000:08:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:42:35 192.168.100.102 kernel: eth2: (PCI Express:2.5GB/s:Width x4) 00:15:17:b2:64:a6 Sep 8 16:42:35 192.168.100.102 kernel: eth2: Intel(R) PRO/1000 Network Connection Sep 8 16:42:35 192.168.100.102 kernel: eth2: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:08:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 16:42:35 192.168.100.102 kernel: 0000:08:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:42:35 192.168.100.102 kernel: eth3: (PCI Express:2.5GB/s:Width x4) 00:15:17:b2:64:a7 Sep 8 16:42:35 192.168.100.102 kernel: eth3: Intel(R) PRO/1000 Network Connection Sep 8 16:42:35 192.168.100.102 kernel: eth3: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 16:42:35 192.168.100.102 kernel: FS-Cache: Loaded Sep 8 16:42:35 192.168.100.102 kernel: eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 8 16:42:35 192.168.100.102 kernel: NET: Registered protocol family 10 Sep 8 16:42:35 192.168.100.102 kernel: lo: Disabled Privacy Extensions Sep 8 16:42:35 192.168.100.102 kernel: IPv6 over IPv4 tunneling driver Sep 8 16:42:35 192.168.100.102 kernel: SELinux: Disabled at runtime. Sep 8 16:42:35 192.168.100.102 kernel: type=1404 audit(1252428141.989:2): selinux=0 auid=4294967295 ses=4294967295 Sep 8 16:42:35 192.168.100.102 kernel: hdb: ATAPI 24X DVD-ROM drive, 2048kB Cache, UDMA(33) Sep 8 16:42:35 192.168.100.102 kernel: Uniform CD-ROM driver Revision: 3.20 Sep 8 16:42:35 192.168.100.102 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Sep 8 16:42:35 192.168.100.102 kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Sep 8 16:42:35 192.168.100.102 kernel: intel_rng: FWH not detected Sep 8 16:42:35 192.168.100.102 kernel: 8250_pnp: Unknown symbol serial8250_unregister_port Sep 8 16:42:35 192.168.100.102 kernel: 8250_pnp: Unknown symbol serial8250_register_port Sep 8 16:42:35 192.168.100.102 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Sep 8 16:42:35 192.168.100.102 kernel: USB Universal Host Controller Interface driver v3.0 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 16:42:35 192.168.100.102 kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller Sep 8 16:42:35 192.168.100.102 kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 Sep 8 16:42:35 192.168.100.102 kernel: uhci_hcd 0000:00:1d.0: irq 17, io base 0x00001800 Sep 8 16:42:35 192.168.100.102 kernel: usb usb1: configuration #1 chosen from 1 choice Sep 8 16:42:35 192.168.100.102 kernel: hub 1-0:1.0: USB hub found Sep 8 16:42:35 192.168.100.102 kernel: hub 1-0:1.0: 2 ports detected Sep 8 16:42:35 192.168.100.102 kernel: 8250_pnp: Unknown symbol serial8250_unregister_port Sep 8 16:42:35 192.168.100.102 kernel: 8250_pnp: Unknown symbol serial8250_register_port Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 16:42:35 192.168.100.102 kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller Sep 8 16:42:35 192.168.100.102 kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 Sep 8 16:42:35 192.168.100.102 kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001820 Sep 8 16:42:35 192.168.100.102 kernel: usb usb2: configuration #1 chosen from 1 choice Sep 8 16:42:35 192.168.100.102 kernel: hub 2-0:1.0: USB hub found Sep 8 16:42:35 192.168.100.102 kernel: hub 2-0:1.0: 2 ports detected Sep 8 16:42:35 192.168.100.102 kernel: EDAC MC: Ver: 2.0.1 Apr 1 2009 Sep 8 16:42:35 192.168.100.102 kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:42:35 192.168.100.102 kernel: usb usb4: configuration #1 chosen from 1 choice Sep 8 16:42:35 192.168.100.102 kernel: device-mapper: multipath: version 1.0.5 loaded Sep 8 16:42:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:38 192.168.100.102 iscsid: connect failed (113) Sep 8 16:42:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:42 192.168.100.102 iscsid: connect failed (113) Sep 8 16:42:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:45 192.168.100.102 iscsid: connect failed (113) Sep 8 16:42:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:55 192.168.100.103 rpc.statd[3126]: Version 1.0.9 Starting Sep 8 16:42:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:56 192.168.100.103 kernel: Bridge firewalling registered Sep 8 16:42:56 192.168.100.103 kernel: xenbr1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. Sep 8 16:42:57 192.168.100.103 kernel: device vif0.0 entered promiscuous mode Sep 8 16:42:57 192.168.100.103 kernel: xenbr1: topology change detected, propagating Sep 8 16:42:57 192.168.100.103 kernel: xenbr1: port 1(vif0.0) entering forwarding state Sep 8 16:42:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:57 192.168.100.103 kernel: ADDRCONF(NETDEV_UP): peth1: link is not ready Sep 8 16:42:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:58 192.168.100.103 kernel: peth1: Link is Up 100 Mbps Full Duplex, Flow Control: None Sep 8 16:42:58 192.168.100.103 kernel: peth1: 10/100 speed: disabling TSO Sep 8 16:42:58 192.168.100.103 kernel: ADDRCONF(NETDEV_CHANGE): peth1: link becomes ready Sep 8 16:42:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:59 192.168.100.103 kernel: device peth1 entered promiscuous mode Sep 8 16:42:59 192.168.100.103 kernel: xenbr1: topology change detected, propagating Sep 8 16:42:59 192.168.100.103 kernel: xenbr1: port 2(peth1) entering forwarding state Sep 8 16:42:59 192.168.100.103 kernel: DLM (built Apr 1 2009 09:54:52) installed Sep 8 16:42:59 192.168.100.103 kernel: GFS2 (built Apr 1 2009 09:56:12) installed Sep 8 16:42:59 192.168.100.103 kernel: Lock_DLM (built Apr 1 2009 09:56:21) installed Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Starting ccsd 2.0.98: Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Built: Jan 21 2009 05:40:28 Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Copyright (C) Red Hat, Inc. 2004 All rights reserved. Sep 8 16:42:59 192.168.100.103 ccsd[3756]: cluster.conf (cluster name = xencluster1, version = 6) found. Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Remote copy of cluster.conf is from quorate node. Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Local version # : 6 Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Remote version #: 6 Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Remote copy of cluster.conf is from quorate node. Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Local version # : 6 Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Remote version #: 6 Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Remote copy of cluster.conf is from quorate node. Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Local version # : 6 Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Remote version #: 6 Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Remote copy of cluster.conf is from quorate node. Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Local version # : 6 Sep 8 16:42:59 192.168.100.103 ccsd[3756]: Remote version #: 6 Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] AIS Executive Service RELEASE 'subrev 1358 version 0.80.3' Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Copyright (C) 2002-2006 MontaVista Software, Inc and contributors. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Copyright (C) 2006 Red Hat, Inc. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] AIS Executive Service: started and ready to provide service. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] openais component openais_cpg loaded. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Registering service handler 'openais cluster closed process group service v1.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] openais component openais_cfg loaded. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Registering service handler 'openais configuration service' Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] openais component openais_msg loaded. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Registering service handler 'openais message service B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] openais component openais_lck loaded. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Registering service handler 'openais distributed locking service B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] openais component openais_evt loaded. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Registering service handler 'openais event service B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] openais component openais_ckpt loaded. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Registering service handler 'openais checkpoint service B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] openais component openais_amf loaded. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Registering service handler 'openais availability management framework B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] openais component openais_clm loaded. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Registering service handler 'openais cluster membership service B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] openais component openais_evs loaded. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Registering service handler 'openais extended virtual synchrony service' Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] openais component openais_cman loaded. Sep 8 16:42:59 192.168.100.103 openais[3762]: [MAIN ] Registering service handler 'openais CMAN membership service 2.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Token Timeout (10000 ms) retransmit timeout (495 ms) Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] token hold (386 ms) retransmits before loss (20 retrans) Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] join (60 ms) send_join (0 ms) consensus (4800 ms) merge (200 ms) Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] downcheck (1000 ms) fail to recv const (50 msgs) Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] seqno unchanged const (30 rotations) Maximum network MTU 1500 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] window size per rotation (50 messages) maximum messages per rotation (17 messages) Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] send threads (0 threads) Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] RRP token expired timeout (495 ms) Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] RRP token problem counter (2000 ms) Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] RRP threshold (10 problem count) Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] RRP mode set to none. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] heartbeat_failures_allowed (0) Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] max_network_delay (50 ms) Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] HeartBeat is Disabled. To enable set heartbeat_failures_allowed > 0 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Receive multicast socket recv buffer size (262142 bytes). Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] entering GATHER state from 11. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Transmit multicast socket send buffer size (262142 bytes). Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] The network interface [10.103.103.103] is now up. Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] entering GATHER state from 11. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Created or loaded sequence id 124.10.103.103.103 for this ring. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] entering GATHER state from 15. Sep 8 16:42:59 192.168.100.103 openais[3762]: [SERV ] Initialising service handler 'openais extended virtual synchrony service' Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] entering GATHER state from 11. Sep 8 16:42:59 192.168.100.103 openais[3762]: [SERV ] Initialising service handler 'openais cluster membership service B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [SERV ] Initialising service handler 'openais availability management framework B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [SERV ] Initialising service handler 'openais checkpoint service B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [SERV ] Initialising service handler 'openais event service B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [SERV ] Initialising service handler 'openais distributed locking service B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [SERV ] Initialising service handler 'openais message service B.01.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [SERV ] Initialising service handler 'openais configuration service' Sep 8 16:42:59 192.168.100.103 openais[3762]: [SERV ] Initialising service handler 'openais cluster closed process group service v1.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [SERV ] Initialising service handler 'openais CMAN membership service 2.01' Sep 8 16:42:59 192.168.100.103 openais[3762]: [CMAN ] CMAN 2.0.98 (built Jan 21 2009 05:40:32) started Sep 8 16:42:59 192.168.100.103 openais[3762]: [SYNC ] Not using a virtual synchrony filter. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Creating commit token because I am the rep. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Saving state aru 0 high seq received 0 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Storing new sequence id for ring 80 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] entering COMMIT state. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] entering RECOVERY state. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] position [0] member 10.103.103.103: Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 124 rep 10.103.103.103 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] aru 0 high delivered 0 received flag 1 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Sending initial ORF token Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] New Configuration: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] Members Left: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] Members Joined: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] New Configuration: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] Members Left: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] Members Joined: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:42:59 192.168.100.103 openais[3762]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] entering OPERATIONAL state. Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:42:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:42:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] entering GATHER state from 11. Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] Creating commit token because I am the rep. Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] Saving state aru 43 high seq received 43 Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] Storing new sequence id for ring 84 Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] entering COMMIT state. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Saving state aru a high seq received a Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Storing new sequence id for ring 84 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] entering COMMIT state. Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] Saving state aru 43 high seq received 43 Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] Storing new sequence id for ring 84 Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] entering COMMIT state. Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] Saving state aru 43 high seq received 43 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] Storing new sequence id for ring 84 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] entering COMMIT state. Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] entering RECOVERY state. Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] position [1] member 10.103.103.103: Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 128 rep 10.103.103.103 Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] aru a high delivered a received flag 1 Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] position [2] member 10.103.103.104: Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] position [3] member 10.103.103.105: Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] entering RECOVERY state. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] position [1] member 10.103.103.103: Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] entering RECOVERY state. Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 128 rep 10.103.103.103 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] aru a high delivered a received flag 1 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] position [2] member 10.103.103.104: Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] position [3] member 10.103.103.105: Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] position [1] member 10.103.103.103: Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 128 rep 10.103.103.103 Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] aru a high delivered a received flag 1 Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] position [2] member 10.103.103.104: Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] entering RECOVERY state. Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] position [3] member 10.103.103.105: Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] position [1] member 10.103.103.103: Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 128 rep 10.103.103.103 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] aru a high delivered a received flag 1 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] position [2] member 10.103.103.104: Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] position [3] member 10.103.103.105: Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 128 rep 10.103.103.101 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] aru 43 high delivered 43 received flag 1 Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:42:59 192.168.100.101 openais[3853]: [TOTEM] Sending initial ORF token Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] New Configuration: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] Members Left: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] Members Joined: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] New Configuration: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] Members Left: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] Members Joined: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:42:59 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 16:42:59 192.168.100.103 openais[3762]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 16:42:59 192.168.100.103 openais[3762]: [TOTEM] entering OPERATIONAL state. Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 16:42:59 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:42:59 192.168.100.104 openais[4094]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:42:59 192.168.100.104 openais[4094]: [TOTEM] entering OPERATIONAL state. Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 16:42:59 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 16:42:59 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:42:59 192.168.100.105 openais[4052]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:42:59 192.168.100.105 openais[4052]: [TOTEM] entering OPERATIONAL state. Sep 8 16:42:59 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 16:42:59 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:42:59 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:42:59 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:42:59 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 16:42:59 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 16:42:59 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:42:59 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 16:43:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:43:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:43:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:43:00 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 16:43:00 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 16:43:00 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:00 192.168.100.101 openais[3853]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:43:00 192.168.100.101 openais[3853]: [TOTEM] entering OPERATIONAL state. Sep 8 16:43:00 192.168.100.103 openais[3762]: [CMAN ] quorum regained, resuming activity Sep 8 16:43:00 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:43:00 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:43:00 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:43:00 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:43:00 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:43:00 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:43:00 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:43:00 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:43:00 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:43:00 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:43:00 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:43:00 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:43:00 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:43:00 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:43:00 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:43:00 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:43:00 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 1 Sep 8 16:43:00 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 1 Sep 8 16:43:00 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 1 Sep 8 16:43:00 192.168.100.103 openais[3762]: [CPG ] got joinlist message from node 1 Sep 8 16:43:00 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 4 Sep 8 16:43:00 192.168.100.103 openais[3762]: [CPG ] got joinlist message from node 4 Sep 8 16:43:00 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 4 Sep 8 16:43:00 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 4 Sep 8 16:43:00 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 5 Sep 8 16:43:00 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 5 Sep 8 16:43:00 192.168.100.103 openais[3762]: [CPG ] got joinlist message from node 5 Sep 8 16:43:00 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 5 Sep 8 16:43:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:00 192.168.100.103 ccsd[3756]: Initial status:: Quorate Sep 8 16:43:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:01 192.168.100.103 fenced[3785]: fencing deferred to prior member Sep 8 16:43:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:03 pxe mountd[2162]: authenticated mount request from 192.168.100.103:637 for /opt/xenxml (/opt/xenxml) Sep 8 16:43:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:04 192.168.100.103 gpm[3974]: *** info [startup.c(95)]: Sep 8 16:43:04 192.168.100.103 gpm[3974]: Started gpm successfully. Entered daemon mode. Sep 8 16:43:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70). Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Successfully dropped root privileges. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: avahi-daemon 0.6.16 starting up. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Successfully called chroot(). Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Successfully dropped remaining capabilities. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Loading service file /services/sftp-ssh.service. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: New relevant interface eth3.IPv6 for mDNS. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Joining mDNS multicast group on interface eth3.IPv6 with address fe80::215:17ff:fec3:c169. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: New relevant interface eth3.IPv4 for mDNS. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Joining mDNS multicast group on interface eth3.IPv4 with address 10.103.103.103. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: New relevant interface eth2.IPv4 for mDNS. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.102.102.103. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: New relevant interface eth0.IPv6 for mDNS. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::230:48ff:fec5:4ad0. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: New relevant interface eth0.IPv4 for mDNS. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.100.103. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Network interface enumeration completed. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Registering new address record for fe80::215:17ff:fec3:c169 on eth3. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Registering new address record for 10.103.103.103 on eth3. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Registering new address record for 10.102.102.103 on eth2. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Registering new address record for fe80::230:48ff:fec5:4ad0 on eth0. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Registering new address record for 192.168.100.103 on eth0. Sep 8 16:43:06 192.168.100.103 avahi-daemon[4166]: Registering HINFO record with values 'X86_64'/'LINUX'. Sep 8 16:43:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:06 192.168.100.102 rpc.statd[3216]: Version 1.0.9 Starting Sep 8 16:43:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:07 192.168.100.103 avahi-daemon[4166]: Server startup complete. Host name is xen3.local. Local service cookie is 801741977. Sep 8 16:43:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:07 192.168.100.102 kernel: Bridge firewalling registered Sep 8 16:43:07 192.168.100.102 kernel: xenbr1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. Sep 8 16:43:08 192.168.100.103 avahi-daemon[4166]: Service "SFTP File Transfer on xen3" (/services/sftp-ssh.service) successfully established. Sep 8 16:43:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:08 192.168.100.103 xenstored: Checking store ... Sep 8 16:43:08 192.168.100.103 xenstored: Checking store complete. Sep 8 16:43:08 192.168.100.102 kernel: device vif0.0 entered promiscuous mode Sep 8 16:43:08 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 16:43:08 192.168.100.102 kernel: xenbr1: port 1(vif0.0) entering forwarding state Sep 8 16:43:08 192.168.100.102 kernel: ADDRCONF(NETDEV_UP): peth1: link is not ready Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 271 Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 272 Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 273 Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 277 Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 278 Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 279 Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 274 Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 275 Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 276 Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 268 Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 269 Sep 8 16:43:08 192.168.100.103 kernel: Breaking affinity for irq 270 Sep 8 16:43:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:09 192.168.100.103 smartd[4446]: smartd version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Sep 8 16:43:09 192.168.100.103 smartd[4446]: Home page is http://smartmontools.sourceforge.net/ Sep 8 16:43:09 192.168.100.103 smartd[4446]: Opened configuration file /etc/smartd.conf Sep 8 16:43:09 192.168.100.103 smartd[4446]: Configuration file /etc/smartd.conf parsed. Sep 8 16:43:09 192.168.100.103 smartd[4446]: Device: /dev/sda, No such device, open() failed Sep 8 16:43:09 192.168.100.103 smartd[4446]: Unable to register ATA device /dev/sda at line 32 of file /etc/smartd.conf Sep 8 16:43:09 192.168.100.103 smartd[4446]: Device /dev/sda not available Sep 8 16:43:09 192.168.100.103 smartd[4446]: Monitoring 0 ATA and 0 SCSI devices Sep 8 16:43:09 192.168.100.103 smartd[4448]: smartd has fork()ed into background mode. New PID=4448. Sep 8 16:43:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:10 192.168.100.102 kernel: peth1: Link is Up 100 Mbps Full Duplex, Flow Control: None Sep 8 16:43:10 192.168.100.102 kernel: peth1: 10/100 speed: disabling TSO Sep 8 16:43:10 192.168.100.102 kernel: ADDRCONF(NETDEV_CHANGE): peth1: link becomes ready Sep 8 16:43:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:10 192.168.100.102 kernel: device peth1 entered promiscuous mode Sep 8 16:43:10 192.168.100.102 kernel: xenbr1: topology change detected, propagating Sep 8 16:43:10 192.168.100.102 kernel: xenbr1: port 2(peth1) entering forwarding state Sep 8 16:43:10 192.168.100.102 kernel: DLM (built Apr 1 2009 09:54:52) installed Sep 8 16:43:10 192.168.100.102 kernel: GFS2 (built Apr 1 2009 09:56:12) installed Sep 8 16:43:10 192.168.100.102 kernel: Lock_DLM (built Apr 1 2009 09:56:21) installed Sep 8 16:43:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:10 192.168.100.102 ccsd[3847]: Starting ccsd 2.0.98: Sep 8 16:43:10 192.168.100.102 ccsd[3847]: Built: Jan 21 2009 05:40:28 Sep 8 16:43:10 192.168.100.102 ccsd[3847]: Copyright (C) Red Hat, Inc. 2004 All rights reserved. Sep 8 16:43:11 192.168.100.102 ccsd[3847]: cluster.conf (cluster name = xencluster1, version = 6) found. Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Remote copy of cluster.conf is from quorate node. Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Local version # : 6 Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Remote version #: 6 Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Remote copy of cluster.conf is from quorate node. Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Local version # : 6 Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Remote version #: 6 Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Remote copy of cluster.conf is from quorate node. Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Local version # : 6 Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Remote version #: 6 Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Remote copy of cluster.conf is from quorate node. Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Local version # : 6 Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Remote version #: 6 Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] AIS Executive Service RELEASE 'subrev 1358 version 0.80.3' Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Copyright (C) 2002-2006 MontaVista Software, Inc and contributors. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Copyright (C) 2006 Red Hat, Inc. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] AIS Executive Service: started and ready to provide service. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] openais component openais_cpg loaded. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Registering service handler 'openais cluster closed process group service v1.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] openais component openais_cfg loaded. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Registering service handler 'openais configuration service' Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] openais component openais_msg loaded. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Registering service handler 'openais message service B.01.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] openais component openais_lck loaded. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Registering service handler 'openais distributed locking service B.01.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] openais component openais_evt loaded. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Registering service handler 'openais event service B.01.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] openais component openais_ckpt loaded. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Registering service handler 'openais checkpoint service B.01.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] openais component openais_amf loaded. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Registering service handler 'openais availability management framework B.01.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] openais component openais_clm loaded. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Registering service handler 'openais cluster membership service B.01.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] openais component openais_evs loaded. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Registering service handler 'openais extended virtual synchrony service' Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] openais component openais_cman loaded. Sep 8 16:43:11 192.168.100.102 openais[3856]: [MAIN ] Registering service handler 'openais CMAN membership service 2.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Token Timeout (10000 ms) retransmit timeout (495 ms) Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] token hold (386 ms) retransmits before loss (20 retrans) Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] join (60 ms) send_join (0 ms) consensus (4800 ms) merge (200 ms) Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] downcheck (1000 ms) fail to recv const (50 msgs) Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] seqno unchanged const (30 rotations) Maximum network MTU 1500 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] window size per rotation (50 messages) maximum messages per rotation (17 messages) Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] send threads (0 threads) Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] RRP token expired timeout (495 ms) Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] RRP token problem counter (2000 ms) Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] RRP threshold (10 problem count) Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] RRP mode set to none. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] heartbeat_failures_allowed (0) Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] max_network_delay (50 ms) Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] HeartBeat is Disabled. To enable set heartbeat_failures_allowed > 0 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Receive multicast socket recv buffer size (262142 bytes). Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Transmit multicast socket send buffer size (262142 bytes). Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] The network interface [10.103.103.102] is now up. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Created or loaded sequence id 124.10.103.103.102 for this ring. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] entering GATHER state from 15. Sep 8 16:43:11 192.168.100.102 openais[3856]: [SERV ] Initialising service handler 'openais extended virtual synchrony service' Sep 8 16:43:11 192.168.100.102 openais[3856]: [SERV ] Initialising service handler 'openais cluster membership service B.01.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [SERV ] Initialising service handler 'openais availability management framework B.01.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [SERV ] Initialising service handler 'openais checkpoint service B.01.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [SERV ] Initialising service handler 'openais event service B.01.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [SERV ] Initialising service handler 'openais distributed locking service B.01.01' Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] entering GATHER state from 11. Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] entering GATHER state from 11. Sep 8 16:43:11 192.168.100.102 openais[3856]: [SERV ] Initialising service handler 'openais message service B.01.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [SERV ] Initialising service handler 'openais configuration service' Sep 8 16:43:11 192.168.100.102 openais[3856]: [SERV ] Initialising service handler 'openais cluster closed process group service v1.01' Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] entering GATHER state from 11. Sep 8 16:43:11 192.168.100.102 openais[3856]: [SERV ] Initialising service handler 'openais CMAN membership service 2.01' Sep 8 16:43:11 192.168.100.102 openais[3856]: [CMAN ] CMAN 2.0.98 (built Jan 21 2009 05:40:32) started Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] entering GATHER state from 11. Sep 8 16:43:11 192.168.100.102 openais[3856]: [SYNC ] Not using a virtual synchrony filter. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Creating commit token because I am the rep. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Saving state aru 0 high seq received 0 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Storing new sequence id for ring 80 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] entering COMMIT state. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] entering RECOVERY state. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] position [0] member 10.103.103.102: Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] previous ring seq 124 rep 10.103.103.102 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] aru 0 high delivered 0 received flag 1 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Sending initial ORF token Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.102 openais[3856]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] entering OPERATIONAL state. Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] entering GATHER state from 11. Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] Creating commit token because I am the rep. Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] Saving state aru 47 high seq received 47 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] Storing new sequence id for ring 88 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] entering COMMIT state. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Saving state aru a high seq received a Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Storing new sequence id for ring 88 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] entering COMMIT state. Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] Saving state aru 47 high seq received 47 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] Storing new sequence id for ring 88 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] entering COMMIT state. Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] Saving state aru 47 high seq received 47 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] Storing new sequence id for ring 88 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] entering COMMIT state. Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] Saving state aru 47 high seq received 47 Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] Storing new sequence id for ring 88 Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] entering COMMIT state. Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] entering RECOVERY state. Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] position [1] member 10.103.103.102: Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 128 rep 10.103.103.102 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] aru a high delivered a received flag 1 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] position [2] member 10.103.103.103: Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] entering RECOVERY state. Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] position [3] member 10.103.103.104: Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] position [4] member 10.103.103.105: Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] position [1] member 10.103.103.102: Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] previous ring seq 128 rep 10.103.103.102 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] aru a high delivered a received flag 1 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] position [2] member 10.103.103.103: Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] position [3] member 10.103.103.104: Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] entering RECOVERY state. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] position [4] member 10.103.103.105: Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] position [1] member 10.103.103.102: Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 128 rep 10.103.103.102 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] aru a high delivered a received flag 1 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] position [2] member 10.103.103.103: Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] position [3] member 10.103.103.104: Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] position [4] member 10.103.103.105: Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:43:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] entering RECOVERY state. Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] position [1] member 10.103.103.102: Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 128 rep 10.103.103.102 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] aru a high delivered a received flag 1 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] position [2] member 10.103.103.103: Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] position [3] member 10.103.103.104: Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] entering RECOVERY state. Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] position [0] member 10.103.103.101: Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] position [4] member 10.103.103.105: Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] position [1] member 10.103.103.102: Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 128 rep 10.103.103.102 Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] aru a high delivered a received flag 1 Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] position [2] member 10.103.103.103: Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] position [3] member 10.103.103.104: Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] Sending initial ORF token Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] position [4] member 10.103.103.105: Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] previous ring seq 132 rep 10.103.103.101 Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] aru 47 high delivered 47 received flag 1 Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:43:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:43:11 192.168.100.102 openais[3856]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:43:11 192.168.100.102 openais[3856]: [TOTEM] entering OPERATIONAL state. Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.103 openais[3762]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:11 192.168.100.103 openais[3762]: [TOTEM] entering OPERATIONAL state. Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:43:11 192.168.100.104 openais[4094]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.104 openais[4094]: [TOTEM] entering OPERATIONAL state. Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.105 openais[4052]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:43:11 192.168.100.105 openais[4052]: [TOTEM] entering OPERATIONAL state. Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] New Configuration: Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] Members Left: Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] Members Joined: Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:43:11 192.168.100.101 openais[3853]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:43:11 192.168.100.101 openais[3853]: [TOTEM] entering OPERATIONAL state. Sep 8 16:43:11 192.168.100.102 openais[3856]: [CMAN ] quorum regained, resuming activity Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.101 Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:43:11 192.168.100.105 openais[4052]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:43:11 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:43:11 192.168.100.102 openais[3856]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:43:11 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:43:11 192.168.100.101 openais[3853]: [CLM ] got nodejoin message 10.103.103.105 Sep 8 16:43:11 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 1 Sep 8 16:43:11 192.168.100.103 openais[3762]: [CPG ] got joinlist message from node 1 Sep 8 16:43:11 192.168.100.102 openais[3856]: [CPG ] got joinlist message from node 1 Sep 8 16:43:11 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 1 Sep 8 16:43:11 192.168.100.103 openais[3762]: [CPG ] got joinlist message from node 3 Sep 8 16:43:11 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 1 Sep 8 16:43:11 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 3 Sep 8 16:43:11 192.168.100.102 openais[3856]: [CPG ] got joinlist message from node 3 Sep 8 16:43:11 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 3 Sep 8 16:43:11 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 3 Sep 8 16:43:11 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 4 Sep 8 16:43:11 192.168.100.103 openais[3762]: [CPG ] got joinlist message from node 4 Sep 8 16:43:11 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 4 Sep 8 16:43:11 192.168.100.102 openais[3856]: [CPG ] got joinlist message from node 4 Sep 8 16:43:11 192.168.100.105 openais[4052]: [CPG ] got joinlist message from node 5 Sep 8 16:43:11 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 4 Sep 8 16:43:11 192.168.100.102 openais[3856]: [CPG ] got joinlist message from node 5 Sep 8 16:43:11 192.168.100.101 openais[3853]: [CPG ] got joinlist message from node 5 Sep 8 16:43:11 192.168.100.103 openais[3762]: [CPG ] got joinlist message from node 5 Sep 8 16:43:11 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 5 Sep 8 16:43:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:11 192.168.100.102 ccsd[3847]: Initial status:: Quorate Sep 8 16:43:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:14 pxe mountd[2162]: authenticated mount request from 192.168.100.102:728 for /opt/xenxml (/opt/xenxml) Sep 8 16:43:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:16 192.168.100.102 gpm[4065]: *** info [startup.c(95)]: Sep 8 16:43:16 192.168.100.102 gpm[4065]: Started gpm successfully. Entered daemon mode. Sep 8 16:43:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70). Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Successfully dropped root privileges. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: avahi-daemon 0.6.16 starting up. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Successfully called chroot(). Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Successfully dropped remaining capabilities. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Loading service file /services/sftp-ssh.service. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: New relevant interface eth3.IPv6 for mDNS. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Joining mDNS multicast group on interface eth3.IPv6 with address fe80::215:17ff:feb2:64a7. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: New relevant interface eth3.IPv4 for mDNS. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Joining mDNS multicast group on interface eth3.IPv4 with address 10.103.103.102. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: New relevant interface eth2.IPv4 for mDNS. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Joining mDNS multicast group on interface eth2.IPv4 with address 10.102.102.102. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: New relevant interface eth0.IPv6 for mDNS. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::230:48ff:fec1:36cc. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: New relevant interface eth0.IPv4 for mDNS. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.100.102. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Network interface enumeration completed. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Registering new address record for fe80::215:17ff:feb2:64a7 on eth3. Sep 8 16:43:17 192.168.100.102 avahi-daemon[4287]: Registering new address record for 10.103.103.102 on eth3. Sep 8 16:43:18 192.168.100.102 avahi-daemon[4287]: Registering new address record for 10.102.102.102 on eth2. Sep 8 16:43:18 192.168.100.102 avahi-daemon[4287]: Registering new address record for fe80::230:48ff:fec1:36cc on eth0. Sep 8 16:43:18 192.168.100.102 avahi-daemon[4287]: Registering new address record for 192.168.100.102 on eth0. Sep 8 16:43:18 192.168.100.102 avahi-daemon[4287]: Registering HINFO record with values 'X86_64'/'LINUX'. Sep 8 16:43:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:18 192.168.100.102 avahi-daemon[4287]: Server startup complete. Host name is xen2.local. Local service cookie is 315955903. Sep 8 16:43:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:19 192.168.100.102 avahi-daemon[4287]: Service "SFTP File Transfer on xen2" (/services/sftp-ssh.service) successfully established. Sep 8 16:43:19 192.168.100.102 xenstored: Checking store ... Sep 8 16:43:19 192.168.100.102 xenstored: Checking store complete. Sep 8 16:43:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 271 Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 272 Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 273 Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 277 Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 278 Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 279 Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 274 Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 275 Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 276 Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 268 Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 269 Sep 8 16:43:20 192.168.100.102 kernel: Breaking affinity for irq 270 Sep 8 16:43:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:21 192.168.100.102 smartd[4544]: smartd version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Sep 8 16:43:21 192.168.100.102 smartd[4544]: Home page is http://smartmontools.sourceforge.net/ Sep 8 16:43:21 192.168.100.102 smartd[4544]: Opened configuration file /etc/smartd.conf Sep 8 16:43:21 192.168.100.102 smartd[4544]: Configuration file /etc/smartd.conf parsed. Sep 8 16:43:21 192.168.100.102 smartd[4544]: Device: /dev/sda, No such device, open() failed Sep 8 16:43:21 192.168.100.102 smartd[4544]: Unable to register ATA device /dev/sda at line 32 of file /etc/smartd.conf Sep 8 16:43:21 192.168.100.102 smartd[4544]: Device /dev/sda not available Sep 8 16:43:21 192.168.100.102 smartd[4544]: Monitoring 0 ATA and 0 SCSI devices Sep 8 16:43:21 192.168.100.102 smartd[4546]: smartd has fork()ed into background mode. New PID=4546. Sep 8 16:43:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:43:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:43:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:25 192.168.100.102 kernel: eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 8 16:44:25 192.168.100.102 kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready Sep 8 16:44:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:26 192.168.100.102 avahi-daemon[4287]: New relevant interface eth2.IPv6 for mDNS. Sep 8 16:44:26 192.168.100.102 avahi-daemon[4287]: Joining mDNS multicast group on interface eth2.IPv6 with address fe80::215:17ff:feb2:64a6. Sep 8 16:44:26 192.168.100.102 avahi-daemon[4287]: Registering new address record for fe80::215:17ff:feb2:64a6 on eth2. Sep 8 16:44:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:37 192.168.100.103 kernel: eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 8 16:44:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:37 192.168.100.103 kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready Sep 8 16:44:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:38 192.168.100.103 avahi-daemon[4166]: New relevant interface eth2.IPv6 for mDNS. Sep 8 16:44:38 192.168.100.103 avahi-daemon[4166]: Joining mDNS multicast group on interface eth2.IPv6 with address fe80::215:17ff:fec3:c168. Sep 8 16:44:38 192.168.100.103 avahi-daemon[4166]: Registering new address record for fe80::215:17ff:fec3:c168 on eth2. Sep 8 16:44:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:42 192.168.100.102 iscsid: iscsid shutting down. Sep 8 16:44:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:43 192.168.100.102 kernel: Loading iSCSI transport class v2.0-724. Sep 8 16:44:43 192.168.100.102 kernel: iscsi: registered transport (tcp) Sep 8 16:44:43 192.168.100.102 kernel: iscsi: registered transport (iser) Sep 8 16:44:43 192.168.100.102 iscsid: iSCSI logger with pid=4891 started! Sep 8 16:44:43 192.168.100.102 kernel: scsi0 : iSCSI Initiator over TCP/IP Sep 8 16:44:43 192.168.100.102 kernel: scsi1 : iSCSI Initiator over TCP/IP Sep 8 16:44:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:44 192.168.100.102 iscsid: transport class version 2.0-724. iscsid version 2.0-868 Sep 8 16:44:44 192.168.100.102 iscsid: iSCSI daemon with pid=4893 started! Sep 8 16:44:44 192.168.100.102 kernel: Vendor: Promise Model: VTrak M610i Rev: 021C Sep 8 16:44:44 192.168.100.102 kernel: Type: Direct-Access ANSI SCSI revision: 05 Sep 8 16:44:44 192.168.100.102 kernel: Vendor: Promise Model: VTrak M610i Rev: 021C Sep 8 16:44:44 192.168.100.102 kernel: Type: Direct-Access ANSI SCSI revision: 05 Sep 8 16:44:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:44 192.168.100.102 kernel: scsi 0:0:0:0: Attached scsi generic sg0 type 0 Sep 8 16:44:44 192.168.100.102 kernel: scsi 1:0:0:0: Attached scsi generic sg1 type 0 Sep 8 16:44:44 192.168.100.102 kernel: sda : very big device. try to use READ CAPACITY(16). Sep 8 16:44:44 192.168.100.102 kernel: SCSI device sda: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 16:44:44 192.168.100.102 kernel: sda: Write Protect is off Sep 8 16:44:44 192.168.100.102 kernel: SCSI device sda: drive cache: write back w/ FUA Sep 8 16:44:44 192.168.100.102 kernel: sda : very big device. try to use READ CAPACITY(16). Sep 8 16:44:44 192.168.100.102 kernel: SCSI device sda: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 16:44:44 192.168.100.102 kernel: sda: Write Protect is off Sep 8 16:44:44 192.168.100.102 kernel: SCSI device sda: drive cache: write back w/ FUA Sep 8 16:44:45 192.168.100.102 kernel: sda: sda1 Sep 8 16:44:45 192.168.100.102 multipathd: sda: add path (uevent) Sep 8 16:44:45 192.168.100.102 kernel: sd 0:0:0:0: Attached scsi disk sda Sep 8 16:44:45 192.168.100.102 kernel: sdb : very big device. try to use READ CAPACITY(16). Sep 8 16:44:45 192.168.100.102 kernel: SCSI device sdb: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 16:44:45 192.168.100.102 kernel: sdb: Write Protect is off Sep 8 16:44:45 192.168.100.102 kernel: SCSI device sdb: drive cache: write back w/ FUA Sep 8 16:44:45 192.168.100.102 kernel: sdb : very big device. try to use READ CAPACITY(16). Sep 8 16:44:45 192.168.100.102 kernel: SCSI device sdb: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 16:44:45 192.168.100.102 kernel: sdb: Write Protect is off Sep 8 16:44:45 192.168.100.102 kernel: SCSI device sdb: drive cache: write back w/ FUA Sep 8 16:44:45 192.168.100.102 kernel: sdb: sdb1 Sep 8 16:44:45 192.168.100.102 kernel: sd 1:0:0:0: Attached scsi disk sdb Sep 8 16:44:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:45 192.168.100.102 iscsid: received iferror -38 Sep 8 16:44:45 192.168.100.102 iscsid: connection1:0 is operational now Sep 8 16:44:45 192.168.100.102 iscsid: received iferror -38 Sep 8 16:44:45 192.168.100.102 iscsid: connection2:0 is operational now Sep 8 16:44:45 192.168.100.102 kernel: device-mapper: multipath round-robin: version 1.0.0 loaded Sep 8 16:44:45 192.168.100.102 multipathd: xen: failed in domap for addition of new path sda Sep 8 16:44:45 192.168.100.102 multipathd: uevent trigger error Sep 8 16:44:45 192.168.100.102 multipathd: sdb: add path (uevent) Sep 8 16:44:45 192.168.100.102 multipathd: xen: failed in domap for addition of new path sdb Sep 8 16:44:45 192.168.100.102 multipathd: uevent trigger error Sep 8 16:44:45 192.168.100.102 multipathd: dm-0: add map (uevent) Sep 8 16:44:45 192.168.100.102 multipathd: xen: event checker started Sep 8 16:44:45 192.168.100.102 multipathd: dm-0: add map (uevent) Sep 8 16:44:45 192.168.100.102 multipathd: dm-0: devmap already registered Sep 8 16:44:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:46 192.168.100.102 multipathd: dm-1: add map (uevent) Sep 8 16:44:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:44:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:44:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:45:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:45:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:19 192.168.100.104 kernel: xenbr1: port 50(vif25.0) entering disabled state Sep 8 16:46:19 192.168.100.104 kernel: device vif25.0 left promiscuous mode Sep 8 16:46:19 192.168.100.104 kernel: xenbr1: port 50(vif25.0) entering disabled state Sep 8 16:46:19 192.168.100.104 avahi-daemon[4605]: Interface tap23.IPv6 no longer relevant for mDNS. Sep 8 16:46:19 192.168.100.104 avahi-daemon[4605]: Leaving mDNS multicast group on interface tap23.IPv6 with address fe80::a450:91ff:feb2:2c2b. Sep 8 16:46:19 192.168.100.104 avahi-daemon[4605]: Withdrawing address record for fe80::a450:91ff:feb2:2c2b on tap23. Sep 8 16:46:19 192.168.100.104 kernel: xenbr1: port 49(tap23) entering disabled state Sep 8 16:46:19 192.168.100.104 kernel: device tap23 left promiscuous mode Sep 8 16:46:19 192.168.100.104 kernel: xenbr1: port 49(tap23) entering disabled state Sep 8 16:46:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:46:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:46:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:47:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:47:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:48:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:48:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:49:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:49:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:50:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:50:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:51:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:51:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:52:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:52:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:53:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:53:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:25 192.168.100.103 iscsid: iscsid shutting down. Sep 8 16:54:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:25 192.168.100.103 kernel: Loading iSCSI transport class v2.0-724. Sep 8 16:54:25 192.168.100.103 kernel: iscsi: registered transport (tcp) Sep 8 16:54:25 192.168.100.103 kernel: iscsi: registered transport (iser) Sep 8 16:54:25 192.168.100.103 iscsid: iSCSI logger with pid=5836 started! Sep 8 16:54:26 192.168.100.103 kernel: scsi0 : iSCSI Initiator over TCP/IP Sep 8 16:54:26 192.168.100.103 kernel: scsi1 : iSCSI Initiator over TCP/IP Sep 8 16:54:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:26 192.168.100.103 iscsid: transport class version 2.0-724. iscsid version 2.0-868 Sep 8 16:54:26 192.168.100.103 iscsid: iSCSI daemon with pid=5837 started! Sep 8 16:54:27 192.168.100.103 kernel: Vendor: Promise Model: VTrak M610i Rev: 021C Sep 8 16:54:27 192.168.100.103 kernel: Type: Direct-Access ANSI SCSI revision: 05 Sep 8 16:54:27 192.168.100.103 kernel: Vendor: Promise Model: VTrak M610i Rev: 021C Sep 8 16:54:27 192.168.100.103 kernel: Type: Direct-Access ANSI SCSI revision: 05 Sep 8 16:54:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:27 192.168.100.103 kernel: scsi 0:0:0:0: Attached scsi generic sg0 type 0 Sep 8 16:54:27 192.168.100.103 kernel: scsi 1:0:0:0: Attached scsi generic sg1 type 0 Sep 8 16:54:27 192.168.100.103 kernel: sda : very big device. try to use READ CAPACITY(16). Sep 8 16:54:27 192.168.100.103 kernel: SCSI device sda: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 16:54:27 192.168.100.103 kernel: sda: Write Protect is off Sep 8 16:54:27 192.168.100.103 kernel: SCSI device sda: drive cache: write back w/ FUA Sep 8 16:54:27 192.168.100.103 kernel: sda : very big device. try to use READ CAPACITY(16). Sep 8 16:54:27 192.168.100.103 kernel: SCSI device sda: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 16:54:27 192.168.100.103 kernel: sda: Write Protect is off Sep 8 16:54:27 192.168.100.103 kernel: SCSI device sda: drive cache: write back w/ FUA Sep 8 16:54:27 192.168.100.103 kernel: sda: sda1 Sep 8 16:54:27 192.168.100.103 kernel: sd 0:0:0:0: Attached scsi disk sda Sep 8 16:54:27 192.168.100.103 multipathd: sda: add path (uevent) Sep 8 16:54:27 192.168.100.103 kernel: sdb : very big device. try to use READ CAPACITY(16). Sep 8 16:54:27 192.168.100.103 kernel: SCSI device sdb: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 16:54:27 192.168.100.103 kernel: sdb: Write Protect is off Sep 8 16:54:27 192.168.100.103 kernel: SCSI device sdb: drive cache: write back w/ FUA Sep 8 16:54:27 192.168.100.103 kernel: sdb : very big device. try to use READ CAPACITY(16). Sep 8 16:54:27 192.168.100.103 kernel: SCSI device sdb: 13671872256 512-byte hdwr sectors (6999999 MB) Sep 8 16:54:27 192.168.100.103 kernel: sdb: Write Protect is off Sep 8 16:54:27 192.168.100.103 kernel: SCSI device sdb: drive cache: write back w/ FUA Sep 8 16:54:27 192.168.100.103 kernel: sdb: sdb1 Sep 8 16:54:27 192.168.100.103 kernel: sd 1:0:0:0: Attached scsi disk sdb Sep 8 16:54:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:27 192.168.100.103 kernel: device-mapper: multipath round-robin: version 1.0.0 loaded Sep 8 16:54:27 192.168.100.103 iscsid: received iferror -38 Sep 8 16:54:27 192.168.100.103 iscsid: connection1:0 is operational now Sep 8 16:54:27 192.168.100.103 iscsid: received iferror -38 Sep 8 16:54:27 192.168.100.103 iscsid: connection2:0 is operational now Sep 8 16:54:27 192.168.100.103 multipathd: xen: failed in domap for addition of new path sda Sep 8 16:54:27 192.168.100.103 multipathd: uevent trigger error Sep 8 16:54:27 192.168.100.103 multipathd: sdb: add path (uevent) Sep 8 16:54:27 192.168.100.103 multipathd: xen: failed in domap for addition of new path sdb Sep 8 16:54:27 192.168.100.103 multipathd: uevent trigger error Sep 8 16:54:27 192.168.100.103 multipathd: dm-0: add map (uevent) Sep 8 16:54:27 192.168.100.103 multipathd: xen: event checker started Sep 8 16:54:27 192.168.100.103 multipathd: dm-0: add map (uevent) Sep 8 16:54:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:54:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:54:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:55:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:55:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:43 pxe xinetd[16078]: EXIT: tftp status=0 pid=29825 duration=909(sec) Sep 8 16:56:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:56:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:56:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:23 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:24 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:25 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:26 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:27 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:28 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:29 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:30 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:31 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:32 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:33 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:34 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:35 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:36 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:37 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:38 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:39 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:40 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:41 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:42 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:43 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:44 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:45 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:46 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:47 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:48 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:49 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:50 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:51 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:52 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:53 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:54 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:55 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:56 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:57 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:58 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:57:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:57:59 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:00 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:01 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:02 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:03 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:04 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:05 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:06 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:07 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:08 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:09 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:10 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:11 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:12 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:13 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:14 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:15 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:16 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:17 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:18 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:19 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:20 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:21 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Busy Sep 8 16:58:22 192.168.100.104 kernel: GFS2: fsid=xencluster1:xenclusterfs1.0: jid=4: Trying to acquire journal lock... Sep 8 16:58:31 192.168.100.102 openais[3856]: [TOTEM] The token was lost in the OPERATIONAL state. Sep 8 16:58:31 192.168.100.102 openais[3856]: [TOTEM] Receive multicast socket recv buffer size (262142 bytes). Sep 8 16:58:31 192.168.100.102 openais[3856]: [TOTEM] Transmit multicast socket send buffer size (262142 bytes). Sep 8 16:58:31 192.168.100.102 openais[3856]: [TOTEM] entering GATHER state from 2. Sep 8 16:58:31 192.168.100.104 openais[4094]: [TOTEM] entering GATHER state from 12. Sep 8 16:58:31 192.168.100.103 openais[3762]: [TOTEM] entering GATHER state from 12. Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] entering GATHER state from 0. Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] entering GATHER state from 11. Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] entering GATHER state from 11. Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] Creating commit token because I am the rep. Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] Saving state aru 5a high seq received 5a Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] Storing new sequence id for ring 8c Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] entering COMMIT state. Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] Saving state aru 5a high seq received 5a Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] Storing new sequence id for ring 8c Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] entering COMMIT state. Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] Saving state aru 5a high seq received 5a Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] Storing new sequence id for ring 8c Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] entering COMMIT state. Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] entering RECOVERY state. Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] position [0] member 10.103.103.102: Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] previous ring seq 136 rep 10.103.103.101 Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] aru 5a high delivered 5a received flag 1 Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] position [1] member 10.103.103.103: Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] previous ring seq 136 rep 10.103.103.101 Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] aru 5a high delivered 5a received flag 1 Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] position [2] member 10.103.103.104: Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] previous ring seq 136 rep 10.103.103.101 Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] aru 5a high delivered 5a received flag 1 Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] entering RECOVERY state. Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] position [0] member 10.103.103.102: Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 136 rep 10.103.103.101 Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] aru 5a high delivered 5a received flag 1 Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] position [1] member 10.103.103.103: Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 136 rep 10.103.103.101 Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] aru 5a high delivered 5a received flag 1 Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] position [2] member 10.103.103.104: Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] entering RECOVERY state. Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] previous ring seq 136 rep 10.103.103.101 Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] position [0] member 10.103.103.102: Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] aru 5a high delivered 5a received flag 1 Sep 8 16:58:36 192.168.100.103 openais[3762]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 136 rep 10.103.103.101 Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] aru 5a high delivered 5a received flag 1 Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] position [1] member 10.103.103.103: Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 136 rep 10.103.103.101 Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] Sending initial ORF token Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] aru 5a high delivered 5a received flag 1 Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] position [2] member 10.103.103.104: Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] previous ring seq 136 rep 10.103.103.101 Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] aru 5a high delivered 5a received flag 1 Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] Did not need to originate any messages in recovery. Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] New Configuration: Sep 8 16:58:36 192.168.100.103 kernel: dlm: closing connection to node 1 Sep 8 16:58:36 192.168.100.103 kernel: dlm: closing connection to node 5 Sep 8 16:58:36 192.168.100.104 kernel: dlm: closing connection to node 1 Sep 8 16:58:36 192.168.100.104 kernel: dlm: closing connection to node 5 Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] New Configuration: Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] Members Left: Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] Members Joined: Sep 8 16:58:36 192.168.100.104 openais[4094]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:58:36 192.168.100.104 openais[4094]: [TOTEM] entering OPERATIONAL state. Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] New Configuration: Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] Members Left: Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] Members Joined: Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] Members Left: Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] New Configuration: Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] Members Left: Sep 8 16:58:36 192.168.100.102 openais[3856]: [CLM ] Members Joined: Sep 8 16:58:36 192.168.100.102 openais[3856]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:58:36 192.168.100.102 openais[3856]: [TOTEM] entering OPERATIONAL state. Sep 8 16:58:36 192.168.100.102 kernel: dlm: closing connection to node 1 Sep 8 16:58:36 192.168.100.102 kernel: dlm: closing connection to node 5 Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.101) Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.105) Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] Members Joined: Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] CLM CONFIGURATION CHANGE Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] New Configuration: Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.102) Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.103) Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] r(0) ip(10.103.103.104) Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] Members Left: Sep 8 16:58:36 192.168.100.103 openais[3762]: [CLM ] Members Joined: Sep 8 16:58:36 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 16:58:37 192.168.100.102 openais[3856]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 16:58:37 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:58:37 192.168.100.104 openais[4094]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:58:37 192.168.100.102 openais[3856]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:58:37 192.168.100.103 openais[3762]: [SYNC ] This node is within the primary component and will provide service. Sep 8 16:58:37 192.168.100.103 openais[3762]: [TOTEM] entering OPERATIONAL state. Sep 8 16:58:37 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.102 Sep 8 16:58:37 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.103 Sep 8 16:58:37 192.168.100.102 openais[3856]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:58:37 192.168.100.103 openais[3762]: [CLM ] got nodejoin message 10.103.103.104 Sep 8 16:58:37 192.168.100.102 openais[3856]: [CPG ] got joinlist message from node 2 Sep 8 16:58:37 192.168.100.103 openais[3762]: [CPG ] got joinlist message from node 2 Sep 8 16:58:37 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 2 Sep 8 16:58:37 192.168.100.103 openais[3762]: [CPG ] got joinlist message from node 3 Sep 8 16:58:37 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 3 Sep 8 16:58:37 192.168.100.104 openais[4094]: [CPG ] got joinlist message from node 4 Sep 8 16:58:37 192.168.100.102 openais[3856]: [CPG ] got joinlist message from node 3 Sep 8 16:58:37 192.168.100.102 openais[3856]: [CPG ] got joinlist message from node 4 Sep 8 16:58:37 192.168.100.103 openais[3762]: [CPG ] got joinlist message from node 4 Sep 8 16:58:37 192.168.100.103 fenced[3785]: fencing deferred to xen2-cluster-if Sep 8 16:58:41 192.168.100.102 fenced[3876]: xen5-cluster-if not a cluster member after 5 sec post_fail_delay Sep 8 16:58:41 192.168.100.102 fenced[3876]: xen1-cluster-if not a cluster member after 5 sec post_fail_delay Sep 8 16:58:41 192.168.100.102 fenced[3876]: fencing node "xen5-cluster-if" Sep 8 16:58:41 192.168.100.102 fence_fibernet_cgi: http://pixie.fiber.net/cgi-bin/router-configurator.cgi?action=shutdown&router=bdr5.fbp.ore.fiber.net&port_ifDescr=GigabitEthernet9/35&redirect=no Sep 8 16:58:55 192.168.100.102 fence_fibernet_cgi: Fencing successful! Sep 8 16:58:55 192.168.100.102 fenced[3876]: fence "xen5-cluster-if" success Sep 8 16:58:55 192.168.100.102 fenced[3876]: fencing node "xen1-cluster-if" Sep 8 16:58:55 192.168.100.102 fence_fibernet_cgi: http://pixie.fiber.net/cgi-bin/router-configurator.cgi?action=shutdown&router=bdr5.fbp.ore.fiber.net&port_ifDescr=GigabitEthernet9/10&redirect=no Sep 8 16:59:07 pxe xinetd[16078]: START: tftp pid=1835 from=192.168.100.101 Sep 8 16:59:09 192.168.100.102 fence_fibernet_cgi: Fencing successful! Sep 8 16:59:09 192.168.100.102 fenced[3876]: fence "xen1-cluster-if" success Sep 8 16:59:37 pxe mountd[2162]: authenticated mount request from 192.168.100.105:876 for /opt/xen_5.3/root (/opt/xen_5.3/root) Sep 8 16:59:37 pxe mountd[2162]: authenticated mount request from 192.168.100.105:878 for /opt/xen_5.3/snapshot (/opt/xen_5.3/snapshot) Sep 8 16:59:40 pxe mountd[2162]: authenticated mount request from 192.168.100.101:875 for /opt/xen_5.3/root (/opt/xen_5.3/root) Sep 8 16:59:40 pxe mountd[2162]: authenticated mount request from 192.168.100.101:877 for /opt/xen_5.3/snapshot (/opt/xen_5.3/snapshot) Sep 8 16:59:55 192.168.100.105 syslogd 1.4.1: restart. Sep 8 16:59:55 192.168.100.105 kernel: klogd 1.4.1, log source = /proc/kmsg started. Sep 8 16:59:55 192.168.100.105 kernel: Bootdata ok (command line is root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen5 ) Sep 8 16:59:55 192.168.100.105 kernel: Linux version 2.6.18-128.1.6.el5xen (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Apr 1 09:53:14 EDT 2009 Sep 8 16:59:55 192.168.100.105 kernel: BIOS-provided physical RAM map: Sep 8 16:59:55 192.168.100.105 kernel: Xen: 0000000000000000 - 00000000a0800000 (usable) Sep 8 16:59:55 192.168.100.105 kernel: DMI present. Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x04] enabled) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] enabled) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x06] enabled) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) Sep 8 16:59:55 192.168.100.105 kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24]) Sep 8 16:59:55 192.168.100.105 kernel: IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Sep 8 16:59:55 192.168.100.105 kernel: Setting APIC routing to xen Sep 8 16:59:55 192.168.100.105 kernel: Using ACPI (MADT) for SMP configuration information Sep 8 16:59:55 192.168.100.105 kernel: Allocating PCI resources starting at d1000000 (gap: d0000000:10000000) Sep 8 16:59:55 192.168.100.105 kernel: Built 1 zonelists. Total pages: 657408 Sep 8 16:59:55 192.168.100.105 kernel: Kernel command line: root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen5 Sep 8 16:59:55 192.168.100.105 kernel: Initializing CPU#0 Sep 8 16:59:55 192.168.100.105 kernel: PID hash table entries: 4096 (order: 12, 32768 bytes) Sep 8 16:59:55 192.168.100.105 kernel: Xen reported: 2000.066 MHz processor. Sep 8 16:59:55 192.168.100.105 kernel: Console: colour VGA+ 80x25 Sep 8 16:59:55 192.168.100.105 kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Sep 8 16:59:55 192.168.100.105 kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Sep 8 16:59:55 192.168.100.105 kernel: Software IO TLB enabled: Sep 8 16:59:55 192.168.100.105 kernel: Aperture: 64 megabytes Sep 8 16:59:55 192.168.100.105 kernel: Kernel range: 0xffff8800057c5000 - 0xffff8800097c5000 Sep 8 16:59:55 192.168.100.105 kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Sep 8 16:59:55 192.168.100.105 kernel: Memory: 2467584k/2629632k available (2447k kernel code, 153292k reserved, 1366k data, 180k init) Sep 8 16:59:55 192.168.100.105 kernel: Calibrating delay using timer specific routine.. 5003.40 BogoMIPS (lpj=10006814) Sep 8 16:59:55 192.168.100.105 kernel: Security Framework v1.0.0 initialized Sep 8 16:59:55 192.168.100.105 kernel: SELinux: Initializing. Sep 8 16:59:55 192.168.100.105 kernel: selinux_register_security: Registering secondary module capability Sep 8 16:59:55 192.168.100.105 kernel: Capability LSM initialized as secondary Sep 8 16:59:55 192.168.100.105 kernel: Mount-cache hash table entries: 256 Sep 8 16:59:55 192.168.100.105 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Sep 8 16:59:55 192.168.100.105 kernel: CPU: L2 cache: 6144K Sep 8 16:59:55 192.168.100.105 kernel: CPU: Physical Processor ID: 0 Sep 8 16:59:55 192.168.100.105 kernel: CPU: Processor Core ID: 0 Sep 8 16:59:55 192.168.100.105 kernel: (SMP-)alternatives turned off Sep 8 16:59:55 192.168.100.105 kernel: ACPI: Core revision 20060707 Sep 8 16:59:55 192.168.100.105 kernel: Initializing CPU#1 Sep 8 16:59:55 192.168.100.105 kernel: Initializing CPU#2 Sep 8 16:59:55 192.168.100.105 kernel: Initializing CPU#3 Sep 8 16:59:55 192.168.100.105 kernel: Initializing CPU#4 Sep 8 16:59:55 192.168.100.105 kernel: Initializing CPU#5 Sep 8 16:59:55 192.168.100.105 kernel: Initializing CPU#6 Sep 8 16:59:55 192.168.100.105 kernel: Brought up 8 CPUs Sep 8 16:59:55 192.168.100.105 kernel: Initializing CPU#7 Sep 8 16:59:55 192.168.100.105 kernel: migration_cost=13068 Sep 8 16:59:55 192.168.100.105 kernel: checking if image is initramfs... it is Sep 8 16:59:55 192.168.100.105 kernel: Grant table initialized Sep 8 16:59:55 192.168.100.105 kernel: NET: Registered protocol family 16 Sep 8 16:59:55 192.168.100.105 kernel: No dock devices found. Sep 8 16:59:55 192.168.100.105 kernel: ACPI: bus type pci registered Sep 8 16:59:55 192.168.100.105 kernel: PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved Sep 8 16:59:55 192.168.100.105 kernel: PCI: Not using MMCONFIG. Sep 8 16:59:55 192.168.100.105 kernel: PCI: Using configuration type 1 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: Interpreter enabled Sep 8 16:59:55 192.168.100.105 kernel: ACPI: Using IOAPIC for interrupt routing Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Root Bridge [PCI0] (0000:00) Sep 8 16:59:55 192.168.100.105 kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 Sep 8 16:59:55 192.168.100.105 kernel: PCI: Transparent bridge - 0000:00:1e.0 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 *7 10 11 14 15) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 14 15) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 14 15) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 14 15) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:59:55 192.168.100.105 kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Sep 8 16:59:55 192.168.100.105 kernel: pnp: PnP ACPI init Sep 8 16:59:55 192.168.100.105 kernel: pnp: PnP ACPI: found 12 devices Sep 8 16:59:55 192.168.100.105 kernel: xen_mem: Initialising balloon driver. Sep 8 16:59:55 192.168.100.105 kernel: usbcore: registered new driver usbfs Sep 8 16:59:55 192.168.100.105 kernel: usbcore: registered new driver hub Sep 8 16:59:55 192.168.100.105 kernel: PCI: Using ACPI for IRQ routing Sep 8 16:59:55 192.168.100.105 kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Sep 8 16:59:55 192.168.100.105 kernel: NetLabel: Initializing Sep 8 16:59:55 192.168.100.105 kernel: NetLabel: domain hash size = 128 Sep 8 16:59:55 192.168.100.105 kernel: NetLabel: protocols = UNLABELED CIPSOv4 Sep 8 16:59:55 192.168.100.105 kernel: NetLabel: unlabeled traffic allowed by default Sep 8 16:59:55 192.168.100.105 kernel: PCI: Bridge: 0000:02:00.0 Sep 8 16:59:55 192.168.100.105 kernel: IO window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: MEM window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: PREFETCH window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: PCI: Bridge: 0000:02:01.0 Sep 8 16:59:55 192.168.100.105 kernel: IO window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: MEM window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: PREFETCH window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: PCI: Bridge: 0000:02:02.0 Sep 8 16:59:55 192.168.100.105 kernel: IO window: 2000-2fff Sep 8 16:59:55 192.168.100.105 kernel: MEM window: d8000000-d80fffff Sep 8 16:59:55 192.168.100.105 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:59:55 192.168.100.105 kernel: PCI: Bridge: 0000:01:00.0 Sep 8 16:59:55 192.168.100.105 kernel: IO window: 2000-2fff Sep 8 16:59:55 192.168.100.105 kernel: MEM window: d8000000-d80fffff Sep 8 16:59:55 192.168.100.105 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:59:55 192.168.100.105 kernel: PCI: Bridge: 0000:01:00.3 Sep 8 16:59:55 192.168.100.105 kernel: IO window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: MEM window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: PREFETCH window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: PCI: Bridge: 0000:00:02.0 Sep 8 16:59:55 192.168.100.105 kernel: IO window: 2000-2fff Sep 8 16:59:55 192.168.100.105 kernel: MEM window: d8000000-d81fffff Sep 8 16:59:55 192.168.100.105 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:59:55 192.168.100.105 kernel: PCI: Bridge: 0000:00:04.0 Sep 8 16:59:55 192.168.100.105 kernel: IO window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: MEM window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: PREFETCH window: disabled. Sep 8 16:59:55 192.168.100.105 kernel: PCI: Bridge: 0000:00:06.0 Sep 8 16:59:55 192.168.100.105 kernel: IO window: 3000-3fff Sep 8 16:59:55 192.168.100.105 kernel: MEM window: d8200000-d82fffff Sep 8 16:59:55 192.168.100.105 kernel: PREFETCH window: d8500000-d85fffff Sep 8 16:59:55 192.168.100.105 kernel: PCI: Bridge: 0000:00:1e.0 Sep 8 16:59:55 192.168.100.105 kernel: IO window: 4000-4fff Sep 8 16:59:55 192.168.100.105 kernel: MEM window: d8300000-d83fffff Sep 8 16:59:55 192.168.100.105 kernel: PREFETCH window: d0000000-d7ffffff Sep 8 16:59:55 192.168.100.105 kernel: GSI 16 sharing vector 0xA0 and IRQ 16 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:59:55 192.168.100.105 kernel: GSI 17 sharing vector 0xA8 and IRQ 17 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 16:59:55 192.168.100.105 kernel: GSI 18 sharing vector 0xB0 and IRQ 18 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:59:55 192.168.100.105 kernel: NET: Registered protocol family 2 Sep 8 16:59:55 192.168.100.105 kernel: IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) Sep 8 16:59:55 192.168.100.105 kernel: TCP established hash table entries: 262144 (order: 10, 4194304 bytes) Sep 8 16:59:55 192.168.100.105 kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) Sep 8 16:59:55 192.168.100.105 kernel: TCP: Hash tables configured (established 262144 bind 65536) Sep 8 16:59:55 192.168.100.105 kernel: TCP reno registered Sep 8 16:59:55 192.168.100.105 kernel: Simple Boot Flag at 0x38 set to 0x1 Sep 8 16:59:55 192.168.100.105 kernel: audit: initializing netlink socket (disabled) Sep 8 16:59:55 192.168.100.105 kernel: type=2000 audit(1252429176.336:1): initialized Sep 8 16:59:55 192.168.100.105 kernel: VFS: Disk quotas dquot_6.5.1 Sep 8 16:59:55 192.168.100.105 kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Sep 8 16:59:55 192.168.100.105 kernel: Initializing Cryptographic API Sep 8 16:59:55 192.168.100.105 kernel: alg: No test for crc32c (crc32c-generic) Sep 8 16:59:55 192.168.100.105 kernel: ksign: Installing public key data Sep 8 16:59:55 192.168.100.105 kernel: Loading keyring Sep 8 16:59:55 192.168.100.105 kernel: - Added public key 5535842996BF3A42 Sep 8 16:59:55 192.168.100.105 kernel: - User ID: CentOS (Kernel Module GPG key) Sep 8 16:59:55 192.168.100.105 kernel: io scheduler noop registered Sep 8 16:59:55 192.168.100.105 kernel: io scheduler anticipatory registered Sep 8 16:59:55 192.168.100.105 kernel: io scheduler deadline registered Sep 8 16:59:55 192.168.100.105 kernel: io scheduler cfq registered (default) Sep 8 16:59:55 192.168.100.105 kernel: assign_interrupt_mode Found MSI capability Sep 8 16:59:55 192.168.100.105 kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: Processor [CPU0] (supports 8 throttling states) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: Processor [CPU1] (supports 8 throttling states) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: Processor [CPU2] (supports 8 throttling states) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: Processor [CPU3] (supports 8 throttling states) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: Processor [CPU4] (supports 8 throttling states) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: Processor [CPU5] (supports 8 throttling states) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: Processor [CPU6] (supports 8 throttling states) Sep 8 16:59:55 192.168.100.105 kernel: ACPI: Processor [CPU7] (supports 8 throttling states) Sep 8 16:59:55 192.168.100.105 kernel: Real Time Clock Driver v1.12ac Sep 8 16:59:55 192.168.100.105 kernel: Non-volatile memory driver v1.2 Sep 8 16:59:55 192.168.100.105 kernel: Linux agpgart interface v0.101 (c) Dave Jones Sep 8 16:59:55 192.168.100.105 kernel: RAMDISK driver initialized: 16 RAM disks of 26403K size 4096 blocksize Sep 8 16:59:55 192.168.100.105 kernel: Xen virtual console successfully installed as ttyS0 Sep 8 16:59:55 192.168.100.105 kernel: Event-channel device installed. Sep 8 16:59:55 192.168.100.105 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Sep 8 16:59:55 192.168.100.105 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Sep 8 16:59:55 192.168.100.105 kernel: ESB2: IDE controller at PCI slot 0000:00:1f.1 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:59:55 192.168.100.105 kernel: ESB2: chipset revision 9 Sep 8 16:59:55 192.168.100.105 kernel: ESB2: not 100% native mode: will probe irqs later Sep 8 16:59:55 192.168.100.105 kernel: ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:pio, hdb:DMA Sep 8 16:59:55 192.168.100.105 kernel: hdb: DVD-ROM UJDA780, ATAPI CD/DVD-ROM drive Sep 8 16:59:55 192.168.100.105 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Sep 8 16:59:55 192.168.100.105 kernel: ide-floppy driver 0.99.newide Sep 8 16:59:55 192.168.100.105 kernel: usbcore: registered new driver hiddev Sep 8 16:59:55 192.168.100.105 kernel: usbcore: registered new driver usbhid Sep 8 16:59:55 192.168.100.105 kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver Sep 8 16:59:55 192.168.100.105 kernel: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12 Sep 8 16:59:55 192.168.100.105 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Sep 8 16:59:55 192.168.100.105 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Sep 8 16:59:55 192.168.100.105 kernel: mice: PS/2 mouse device common for all mice Sep 8 16:59:55 192.168.100.105 kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 Sep 8 16:59:55 192.168.100.105 kernel: md: bitmap version 4.39 Sep 8 16:59:55 192.168.100.105 kernel: TCP bic registered Sep 8 16:59:55 192.168.100.105 kernel: Initializing IPsec netlink socket Sep 8 16:59:55 192.168.100.105 kernel: NET: Registered protocol family 1 Sep 8 16:59:55 192.168.100.105 kernel: NET: Registered protocol family 17 Sep 8 16:59:55 192.168.100.105 kernel: Write protecting the kernel read-only data: 467k Sep 8 16:59:55 192.168.100.105 kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 Sep 8 16:59:55 192.168.100.105 kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation. Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:59:55 192.168.100.105 kernel: 0000:05:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:59:55 192.168.100.105 kernel: eth0: (PCI Express:2.5GB/s:Width x4) 00:30:48:c5:8d:50 Sep 8 16:59:55 192.168.100.105 kernel: eth0: Intel(R) PRO/1000 Network Connection Sep 8 16:59:55 192.168.100.105 kernel: eth0: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 16:59:55 192.168.100.105 kernel: GSI 19 sharing vector 0xB8 and IRQ 19 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:05:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 16:59:55 192.168.100.105 kernel: 0000:05:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:59:55 192.168.100.105 kernel: eth1: (PCI Express:2.5GB/s:Width x4) 00:30:48:c5:8d:51 Sep 8 16:59:55 192.168.100.105 kernel: eth1: Intel(R) PRO/1000 Network Connection Sep 8 16:59:55 192.168.100.105 kernel: eth1: MAC: 4, PHY: 5, PBA No: 2050ff-0ff Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:08:00.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:59:55 192.168.100.105 kernel: 0000:08:00.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:59:55 192.168.100.105 kernel: eth2: (PCI Express:2.5GB/s:Width x4) 00:15:17:b9:94:00 Sep 8 16:59:55 192.168.100.105 kernel: eth2: Intel(R) PRO/1000 Network Connection Sep 8 16:59:55 192.168.100.105 kernel: eth2: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:08:00.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 16:59:55 192.168.100.105 kernel: 0000:08:00.1: Failed to initialize MSI interrupts. Falling back to legacy interrupts. Sep 8 16:59:55 192.168.100.105 kernel: eth3: (PCI Express:2.5GB/s:Width x4) 00:15:17:b9:94:01 Sep 8 16:59:55 192.168.100.105 kernel: eth3: Intel(R) PRO/1000 Network Connection Sep 8 16:59:55 192.168.100.105 kernel: eth3: MAC: 0, PHY: 4, PBA No: d50868-003 Sep 8 16:59:55 192.168.100.105 kernel: FS-Cache: Loaded Sep 8 16:59:55 192.168.100.105 kernel: eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 8 16:59:55 192.168.100.105 kernel: NET: Registered protocol family 10 Sep 8 16:59:55 192.168.100.105 kernel: lo: Disabled Privacy Extensions Sep 8 16:59:55 192.168.100.105 kernel: IPv6 over IPv4 tunneling driver Sep 8 16:59:55 192.168.100.105 kernel: SELinux: Disabled at runtime. Sep 8 16:59:55 192.168.100.105 kernel: type=1404 audit(1252429185.756:2): selinux=0 auid=4294967295 ses=4294967295 Sep 8 16:59:55 192.168.100.105 kernel: hdb: ATAPI 24X DVD-ROM drive, 2048kB Cache, UDMA(33) Sep 8 16:59:55 192.168.100.105 kernel: Uniform CD-ROM driver Revision: 3.20 Sep 8 16:59:55 192.168.100.105 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Sep 8 16:59:55 192.168.100.105 kernel: 8250_pnp: Unknown symbol serial8250_unregister_port Sep 8 16:59:55 192.168.100.105 kernel: 8250_pnp: Unknown symbol serial8250_register_port Sep 8 16:59:55 192.168.100.105 kernel: 8250_pnp: Unknown symbol serial8250_unregister_port Sep 8 16:59:55 192.168.100.105 kernel: 8250_pnp: Unknown symbol serial8250_register_port Sep 8 16:59:55 192.168.100.105 kernel: USB Universal Host Controller Interface driver v3.0 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 16:59:55 192.168.100.105 kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller Sep 8 16:59:55 192.168.100.105 kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 Sep 8 16:59:55 192.168.100.105 kernel: uhci_hcd 0000:00:1d.0: irq 17, io base 0x00001800 Sep 8 16:59:55 192.168.100.105 kernel: usb usb1: configuration #1 chosen from 1 choice Sep 8 16:59:55 192.168.100.105 kernel: hub 1-0:1.0: USB hub found Sep 8 16:59:55 192.168.100.105 kernel: hub 1-0:1.0: 2 ports detected Sep 8 16:59:55 192.168.100.105 kernel: intel_rng: FWH not detected Sep 8 16:59:55 192.168.100.105 kernel: EDAC MC: Ver: 2.0.1 Apr 1 2009 Sep 8 16:59:55 192.168.100.105 kernel: input: PC Speaker as /class/input/input0 Sep 8 16:59:55 192.168.100.105 kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19 Sep 8 16:59:55 192.168.100.105 kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller Sep 8 16:59:55 192.168.100.105 kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 Sep 8 16:59:55 192.168.100.105 kernel: ehci_hcd 0000:00:1d.7: irq 17, io mem 0xd8600000 Sep 8 16:59:55 192.168.100.105 kernel: usb usb4: configuration #1 chosen from 1 choice Sep 8 16:59:55 192.168.100.105 kernel: device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel@redhat.com Sep 8 16:59:55 192.168.100.105 kernel: eth3: Link is Up 100 Mbps Full Duplex, Flow Control: None Sep 8 16:59:58 192.168.100.101 syslogd 1.4.1: restart. Sep 8 16:59:58 192.168.100.101 kernel: klogd 1.4.1, log source = /proc/kmsg started. Sep 8 16:59:58 192.168.100.101 kernel: Bootdata ok (command line is root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen1 ) Sep 8 16:59:58 192.168.100.101 kernel: Linux version 2.6.18-128.1.6.el5xen (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Apr 1 09:53:14 EDT 2009 Sep 8 16:59:58 192.168.100.101 kernel: BIOS-provided physical RAM map: Sep 8 16:59:58 192.168.100.101 kernel: Xen: 0000000000000000 - 00000000a0800000 (usable) Sep 8 16:59:58 192.168.100.101 kernel: DMI present. Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x04] enabled) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] enabled) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x06] enabled) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) Sep 8 16:59:58 192.168.100.101 kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 Sep 8 16:59:58 192.168.100.101 kernel: ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24]) Sep 8 16:59:58 192.168.100.101 kernel: IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47 Sep 8 16:59:58 192.168.100.101 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) Sep 8 16:59:58 192.168.100.101 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Sep 8 16:59:58 192.168.100.101 kernel: Setting APIC routing to xen Sep 8 16:59:58 192.168.100.101 kernel: Using ACPI (MADT) for SMP configuration information Sep 8 16:59:58 192.168.100.101 kernel: Allocating PCI resources starting at d1000000 (gap: d0000000:10000000) Sep 8 16:59:58 192.168.100.101 kernel: Built 1 zonelists. Total pages: 657408 Sep 8 16:59:58 192.168.100.101 kernel: Kernel command line: root=/dev/ram0 init=disklessrc NFSROOT=192.168.100.2:/opt/xen_5.3 ramdisk_size=26403 ETHERNET=eth0 SNAPSHOT=xen1 Sep 8 16:59:58 192.168.100.101 kernel: Initializing CPU#0 Sep 8 16:59:58 192.168.100.101 kernel: PID hash table entries: 4096 (order: 12, 32768 bytes) Sep 8 16:59:58 192.168.100.101 kernel: Xen reported: 2000.068 MHz processor. Sep 8 16:59:58 192.168.100.101 kernel: Console: colour VGA+ 80x25 Sep 8 16:59:58 192.168.100.101 kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Sep 8 16:59:58 192.168.100.101 kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Sep 8 16:59:58 192.168.100.101 kernel: Software IO TLB enabled: Sep 8 16:59:58 192.168.100.101 kernel: Aperture: 64 megabytes Sep 8 16:59:58 192.168.100.101 kernel: Kernel range: 0xffff8800057c5000 - 0xffff8800097c5000 Sep 8 16:59:58 192.168.100.101 kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Sep 8 16:59:58 192.168.100.101 kernel: Memory: 2467584k/2629632k available (2447k kernel code, 153292k reserved, 1366k data, 180k init) Sep 8 16:59:58 192.168.100.101 kernel: Calibrating delay using timer specific routine.. 5002.54 BogoMIPS (lpj=10005098) Sep 8 16:59:58 192.168.100.101 kernel: Security Framework v1.0.0 initialized Sep 8 16:59:58 192.168.100.101 kernel: SELinux: Initializing. Sep 8 16:59:58 192.168.100.101 kernel: selinux_register_security: Registering secondary module capability Sep 8 16:59:58 192.168.100.101 kernel: Capability LSM initialized as secondary Sep 8 16:59:58 192.168.100.101 kernel: Mount-cache hash table entries: 256 Sep 8 16:59:58 192.168.100.101 kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Sep 8 16:59:58 192.168.100.101 kernel: CPU: L2 cache: 6144K Sep 8 16:59:58 192.168.100.101 kernel: CPU: Physical Processor ID: 0 Sep 8 16:59:58 192.168.100.101 kernel: CPU: Processor Core ID: 0 Sep 8 16:59:58 192.168.100.101 kernel: (SMP-)alternatives turned off Sep 8 16:59:58 192.168.100.101 kernel: ACPI: Core revision 20060707 Sep 8 16:59:58 192.168.100.101 kernel: Initializing CPU#1 Sep 8 16:59:58 192.168.100.101 kernel: Initializing CPU#2 Sep 8 16:59:58 192.168.100.101 kernel: Initializing CPU#3 Sep 8 16:59:58 192.168.100.101 kernel: Initializing CPU#4 Sep 8 16:59:58 192.168.100.101 kernel: Initializing CPU#5 Sep 8 16:59:58 192.168.100.101 kernel: Initializing CPU#6 Sep 8 16:59:58 192.168.100.101 kernel: Brought up 8 CPUs Sep 8 16:59:58 192.168.100.101 kernel: Initializing CPU#7 Sep 8 16:59:58 192.168.100.101 kernel: migration_cost=6676 Sep 8 16:59:58 192.168.100.101 kernel: checking if image is initramfs... it is Sep 8 16:59:58 192.168.100.101 kernel: Grant table initialized Sep 8 16:59:58 192.168.100.101 kernel: NET: Registered protocol family 16 Sep 8 16:59:58 192.168.100.101 kernel: No dock devices found. Sep 8 16:59:58 192.168.100.101 kernel: ACPI: bus type pci registered Sep 8 16:59:59 192.168.100.101 kernel: PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved Sep 8 16:59:59 192.168.100.101 kernel: PCI: Not using MMCONFIG. Sep 8 16:59:59 192.168.100.101 kernel: PCI: Using configuration type 1 Sep 8 16:59:59 192.168.100.101 kernel: ACPI: Interpreter enabled Sep 8 16:59:59 192.168.100.101 kernel: ACPI: Using IOAPIC for interrupt routing Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Root Bridge [PCI0] (0000:00) Sep 8 16:59:59 192.168.100.101 kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 Sep 8 16:59:59 192.168.100.101 kernel: PCI: Transparent bridge - 0000:00:1e.0 Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 *7 10 11 14 15) Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 14 15) Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 14 15) Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 14 15) Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 6 7 10 11 14 15) *0, disabled. Sep 8 16:59:59 192.168.100.101 kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Sep 8 16:59:59 192.168.100.101 kernel: pnp: PnP ACPI init Sep 8 16:59:59 192.168.100.101 kernel: pnp: PnP ACPI: found 12 devices Sep 8 16:59:59 192.168.100.101 kernel: xen_mem: Initialising balloon driver. Sep 8 16:59:59 192.168.100.101 kernel: usbcore: registered new driver usbfs Sep 8 16:59:59 192.168.100.101 kernel: usbcore: registered new driver hub Sep 8 16:59:59 192.168.100.101 kernel: PCI: Using ACPI for IRQ routing Sep 8 16:59:59 192.168.100.101 kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Sep 8 16:59:59 192.168.100.101 kernel: NetLabel: Initializing Sep 8 16:59:59 192.168.100.101 kernel: NetLabel: domain hash size = 128 Sep 8 16:59:59 192.168.100.101 kernel: NetLabel: protocols = UNLABELED CIPSOv4 Sep 8 16:59:59 192.168.100.101 kernel: NetLabel: unlabeled traffic allowed by default Sep 8 16:59:59 192.168.100.101 kernel: PCI: Bridge: 0000:02:00.0 Sep 8 16:59:59 192.168.100.101 kernel: IO window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: MEM window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: PREFETCH window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: PCI: Bridge: 0000:02:01.0 Sep 8 16:59:59 192.168.100.101 kernel: IO window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: MEM window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: PREFETCH window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: PCI: Bridge: 0000:02:02.0 Sep 8 16:59:59 192.168.100.101 kernel: IO window: 2000-2fff Sep 8 16:59:59 192.168.100.101 kernel: MEM window: d8000000-d80fffff Sep 8 16:59:59 192.168.100.101 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:59:59 192.168.100.101 kernel: PCI: Bridge: 0000:01:00.0 Sep 8 16:59:59 192.168.100.101 kernel: IO window: 2000-2fff Sep 8 16:59:59 192.168.100.101 kernel: MEM window: d8000000-d80fffff Sep 8 16:59:59 192.168.100.101 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:59:59 192.168.100.101 kernel: PCI: Bridge: 0000:01:00.3 Sep 8 16:59:59 192.168.100.101 kernel: IO window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: MEM window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: PREFETCH window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: PCI: Bridge: 0000:00:02.0 Sep 8 16:59:59 192.168.100.101 kernel: IO window: 2000-2fff Sep 8 16:59:59 192.168.100.101 kernel: MEM window: d8000000-d81fffff Sep 8 16:59:59 192.168.100.101 kernel: PREFETCH window: d8400000-d84fffff Sep 8 16:59:59 192.168.100.101 kernel: PCI: Bridge: 0000:00:04.0 Sep 8 16:59:59 192.168.100.101 kernel: IO window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: MEM window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: PREFETCH window: disabled. Sep 8 16:59:59 192.168.100.101 kernel: PCI: Bridge: 0000:00:06.0 Sep 8 16:59:59 192.168.100.101 kernel: IO window: 3000-3fff Sep 8 16:59:59 192.168.100.101 kernel: MEM window: d8200000-d82fffff Sep 8 16:59:59 192.168.100.101 kernel: PREFETCH window: d8500000-d85fffff Sep 8 16:59:59 192.168.100.101 kernel: PCI: Bridge: 0000:00:1e.0 Sep 8 16:59:59 192.168.100.101 kernel: IO window: 4000-4fff Sep 8 16:59:59 192.168.100.101 kernel: MEM window: d8300000-d83fffff Sep 8 16:59:59 192.168.100.101 kernel: PREFETCH window: d0000000-d7ffffff Sep 8 16:59:59 192.168.100.101 kernel: GSI 16 sharing vector 0xA0 and IRQ 16 Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:59:59 192.168.100.101 kernel: GSI 17 sharing vector 0xA8 and IRQ 17 Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 17 (level, low) -> IRQ 17 Sep 8 16:59:59 192.168.100.101 kernel: GSI 18 sharing vector 0xB0 and IRQ 18 Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 16 Sep 8 16:59:59 192.168.100.101 kernel: ACPI: PCI Interrupt 0000