[ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.0-7.9-debug (green@centos7-base) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Sat Mar 26 23:28:42 EDT 2022 [ 0.000000] Command line: rd.shell root=nbd:192.168.200.253:centos7:ext4:ro:-p,-b4096 ro crashkernel=128M panic=1 nomodeset ipmtu=9000 ip=dhcp rd.neednet=1 init_on_free=off mitigations=off console=ttyS1,115200 audit=0 [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bffcdfff] usable [ 0.000000] BIOS-e820: [mem 0x00000000bffce000-0x00000000bfffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000013edfffff] usable [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] SMBIOS 3.0.0 present. [ 0.000000] DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-1.fc39 04/01/2014 [ 0.000000] Hypervisor detected: KVM [ 0.000000] e820: last_pfn = 0x13ee00 max_arch_pfn = 0x400000000 [ 0.000000] PAT configuration [0-7]: WB WC UC- UC WB WP UC- UC [ 0.000000] e820: last_pfn = 0xbffce max_arch_pfn = 0x400000000 [ 0.000000] found SMP MP-table at [mem 0x000f53f0-0x000f53ff] mapped at [ffffffffff2003f0] [ 0.000000] Using GB pages for direct mapping [ 0.000000] RAMDISK: [mem 0xbc2e2000-0xbffbffff] [ 0.000000] Early table checksum verification disabled [ 0.000000] ACPI: RSDP 00000000000f5200 00014 (v00 BOCHS ) [ 0.000000] ACPI: RSDT 00000000bffe1d87 00034 (v01 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: FACP 00000000bffe1c23 00074 (v01 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: DSDT 00000000bffe0040 01BE3 (v01 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: FACS 00000000bffe0000 00040 [ 0.000000] ACPI: APIC 00000000bffe1c97 00090 (v03 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: HPET 00000000bffe1d27 00038 (v01 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] ACPI: WAET 00000000bffe1d5f 00028 (v01 BOCHS BXPC 00000001 BXPC 00000001) [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000013edfffff] [ 0.000000] NODE_DATA(0) allocated [mem 0x13e5e3000-0x13e609fff] [ 0.000000] Reserving 128MB of memory at 768MB for crashkernel (System RAM: 4077MB) [ 0.000000] kvm-clock: cpu 0, msr 1:3e592001, primary cpu clock [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 [ 0.000000] kvm-clock: using sched offset of 335055893 cycles [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x00001000-0x00ffffff] [ 0.000000] DMA32 [mem 0x01000000-0xffffffff] [ 0.000000] Normal [mem 0x100000000-0x13edfffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00001000-0x0009efff] [ 0.000000] node 0: [mem 0x00100000-0xbffcdfff] [ 0.000000] node 0: [mem 0x100000000-0x13edfffff] [ 0.000000] Initmem setup node 0 [mem 0x00001000-0x13edfffff] [ 0.000000] ACPI: PM-Timer IO Port: 0x608 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level) [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs [ 0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff] [ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000effff] [ 0.000000] PM: Registered nosave memory: [mem 0x000f0000-0x000fffff] [ 0.000000] PM: Registered nosave memory: [mem 0xbffce000-0xbfffffff] [ 0.000000] PM: Registered nosave memory: [mem 0xc0000000-0xfeffbfff] [ 0.000000] PM: Registered nosave memory: [mem 0xfeffc000-0xfeffffff] [ 0.000000] PM: Registered nosave memory: [mem 0xff000000-0xfffbffff] [ 0.000000] PM: Registered nosave memory: [mem 0xfffc0000-0xffffffff] [ 0.000000] e820: [mem 0xc0000000-0xfeffbfff] available for PCI devices [ 0.000000] Booting paravirtualized kernel on KVM [ 0.000000] setup_percpu: NR_CPUS:5120 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1 [ 0.000000] percpu: Embedded 38 pages/cpu s115176 r8192 d32280 u524288 [ 0.000000] KVM setup async PF for cpu 0 [ 0.000000] kvm-stealtime: cpu 0, msr 13e2135c0 [ 0.000000] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes) [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 1027487 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: rd.shell root=nbd:192.168.200.253:centos7:ext4:ro:-p,-b4096 ro crashkernel=128M panic=1 nomodeset ipmtu=9000 ip=dhcp rd.neednet=1 init_on_free=off mitigations=off console=ttyS1,115200 audit=0 [ 0.000000] audit: disabled (until reboot) [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] x86/fpu: xstate_offset[2]: 0240, xstate_sizes[2]: 0100 [ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form [ 0.000000] Memory: 3820268k/5224448k available (8172k kernel code, 1049168k absent, 355012k reserved, 5773k data, 2532k init) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU restricting CPUs from NR_CPUS=5120 to nr_cpu_ids=4. [ 0.000000] Offload RCU callbacks from all CPUs [ 0.000000] Offload RCU callbacks from CPUs: 0-3. [ 0.000000] NR_IRQS:327936 nr_irqs:456 0 [ 0.000000] Console: colour *CGA 80x25 [ 0.000000] console [ttyS1] enabled [ 0.000000] allocated 25165824 bytes of page_cgroup [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.000000] kmemleak: Kernel memory leak detector disabled [ 0.000000] tsc: Detected 2399.998 MHz processor [ 0.423117] Calibrating delay loop (skipped) preset value.. 4799.99 BogoMIPS (lpj=2399998) [ 0.425421] pid_max: default: 32768 minimum: 301 [ 0.426737] Security Framework initialized [ 0.427775] SELinux: Initializing. [ 0.430449] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) [ 0.434828] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 0.437615] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes) [ 0.439717] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes) [ 0.442235] Initializing cgroup subsys memory [ 0.443263] Initializing cgroup subsys devices [ 0.444454] Initializing cgroup subsys freezer [ 0.445623] Initializing cgroup subsys net_cls [ 0.447030] Initializing cgroup subsys blkio [ 0.448662] Initializing cgroup subsys perf_event [ 0.450417] Initializing cgroup subsys hugetlb [ 0.452025] Initializing cgroup subsys pids [ 0.453451] Initializing cgroup subsys net_prio [ 0.455457] x86/cpu: User Mode Instruction Prevention (UMIP) activated [ 0.458748] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0 [ 0.460506] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0 [ 0.462272] tlb_flushall_shift: 6 [ 0.463191] FEATURE SPEC_CTRL Present [ 0.464220] FEATURE IBPB_SUPPORT Present [ 0.465283] Spectre V2 : Enabling Indirect Branch Prediction Barrier [ 0.467262] Spectre V2 : Vulnerable [ 0.468335] Speculative Store Bypass: Vulnerable [ 0.470368] debug: unmapping init [mem 0xffffffff82019000-0xffffffff8201ffff] [ 0.478137] ACPI: Core revision 20130517 [ 0.481316] ACPI: All ACPI Tables successfully acquired [ 0.482919] ftrace: allocating 30294 entries in 119 pages [ 0.539761] Enabling x2apic [ 0.540836] Enabled x2apic [ 0.542197] Switched APIC routing to physical x2apic. [ 0.545793] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.547623] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz (fam: 06, model: 3e, stepping: 04) [ 0.551291] Performance Events: IvyBridge events, full-width counters, Intel PMU driver. [ 0.554806] ... version: 2 [ 0.555855] ... bit width: 48 [ 0.557032] ... generic registers: 4 [ 0.557896] ... value mask: 0000ffffffffffff [ 0.559298] ... max period: 00007fffffffffff [ 0.561033] ... fixed-purpose events: 3 [ 0.562252] ... event mask: 000000070000000f [ 0.563742] KVM setup paravirtual spinlock [ 0.566683] smpboot: Booting Node 0, Processors #1[ 0.568257] kvm-clock: cpu 1, msr 1:3e592041, secondary cpu clock [ 0.571325] KVM setup async PF for cpu 1 [ 0.572508] kvm-stealtime: cpu 1, msr 13e2935c0 #2[ 0.574858] kvm-clock: cpu 2, msr 1:3e592081, secondary cpu clock [ 0.577505] KVM setup async PF for cpu 2 [ 0.578150] kvm-clock: cpu 3, msr 1:3e5920c1, secondary cpu clock #3 OK [ 0.580264] kvm-stealtime: cpu 2, msr 13e3135c0 [ 0.581496] Brought up 4 CPUs [ 0.581508] KVM setup async PF for cpu 3 [ 0.581515] kvm-stealtime: cpu 3, msr 13e3935c0 [ 0.583934] smpboot: Max logical packages: 1 [ 0.585004] smpboot: Total of 4 processors activated (19199.98 BogoMIPS) [ 0.588984] devtmpfs: initialized [ 0.590034] x86/mm: Memory block size: 128MB [ 0.593980] EVM: security.selinux [ 0.594949] EVM: security.ima [ 0.596014] EVM: security.capability [ 0.599542] atomic64 test passed for x86-64 platform with CX8 and with SSE [ 0.602323] NET: Registered protocol family 16 [ 0.604231] cpuidle: using governor haltpoll [ 0.606824] ACPI: bus type PCI registered [ 0.607545] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.609781] PCI: Using configuration type 1 for base access [ 0.611634] core: PMU erratum BJ122, BV98, HSD29 worked around, HT is on [ 0.620070] ACPI: Added _OSI(Module Device) [ 0.621109] ACPI: Added _OSI(Processor Device) [ 0.622057] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.623823] ACPI: Added _OSI(Processor Aggregator Device) [ 0.625028] ACPI: Added _OSI(Linux-Dell-Video) [ 0.629871] ACPI: Interpreter enabled [ 0.630627] ACPI: (supports S0 S3 S4 S5) [ 0.631382] ACPI: Using IOAPIC for interrupt routing [ 0.632322] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.634766] ACPI: Enabled 2 GPEs in block 00 to 0F [ 0.640685] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.642468] acpi PNP0A03:00: _OSC: OS supports [ASPM ClockPM Segments MSI] [ 0.644925] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM [ 0.647048] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge. [ 0.651129] acpiphp: Slot [2] registered [ 0.652122] acpiphp: Slot [5] registered [ 0.653427] acpiphp: Slot [6] registered [ 0.654650] acpiphp: Slot [7] registered [ 0.655935] acpiphp: Slot [8] registered [ 0.657172] acpiphp: Slot [9] registered [ 0.658589] acpiphp: Slot [10] registered [ 0.659938] acpiphp: Slot [3] registered [ 0.661164] acpiphp: Slot [4] registered [ 0.662589] acpiphp: Slot [11] registered [ 0.663429] acpiphp: Slot [12] registered [ 0.664662] acpiphp: Slot [13] registered [ 0.665727] acpiphp: Slot [14] registered [ 0.666884] acpiphp: Slot [15] registered [ 0.667708] acpiphp: Slot [16] registered [ 0.669056] acpiphp: Slot [17] registered [ 0.669881] acpiphp: Slot [18] registered [ 0.670926] acpiphp: Slot [19] registered [ 0.672368] acpiphp: Slot [20] registered [ 0.673883] acpiphp: Slot [21] registered [ 0.675011] acpiphp: Slot [22] registered [ 0.676750] acpiphp: Slot [23] registered [ 0.678370] acpiphp: Slot [24] registered [ 0.679680] acpiphp: Slot [25] registered [ 0.680847] acpiphp: Slot [26] registered [ 0.682330] acpiphp: Slot [27] registered [ 0.683959] acpiphp: Slot [28] registered [ 0.685366] acpiphp: Slot [29] registered [ 0.686371] acpiphp: Slot [30] registered [ 0.687265] acpiphp: Slot [31] registered [ 0.688262] PCI host bridge to bus 0000:00 [ 0.689091] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] [ 0.690687] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 0.692341] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] [ 0.694032] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window] [ 0.695800] pci_bus 0000:00: root bus resource [mem 0x380000000000-0x38007fffffff window] [ 0.697732] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.711013] pci 0000:00:01.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7] [ 0.713466] pci 0000:00:01.1: legacy IDE quirk: reg 0x14: [io 0x03f6] [ 0.715548] pci 0000:00:01.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177] [ 0.717802] pci 0000:00:01.1: legacy IDE quirk: reg 0x1c: [io 0x0376] [ 0.721602] pci 0000:00:01.3: quirk: [io 0x0600-0x063f] claimed by PIIX4 ACPI [ 0.724410] pci 0000:00:01.3: quirk: [io 0x0700-0x070f] claimed by PIIX4 SMB [ 0.918458] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11) [ 0.922602] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11) [ 0.924648] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11) [ 0.926731] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11) [ 0.928801] ACPI: PCI Interrupt Link [LNKS] (IRQs *9) [ 0.931591] vgaarb: loaded [ 0.933333] SCSI subsystem initialized [ 0.934678] ACPI: bus type USB registered [ 0.936015] usbcore: registered new interface driver usbfs [ 0.937875] usbcore: registered new interface driver hub [ 0.939710] usbcore: registered new device driver usb [ 0.941659] PCI: Using ACPI for IRQ routing [ 0.943610] NetLabel: Initializing [ 0.944685] NetLabel: domain hash size = 128 [ 0.946069] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.947790] NetLabel: unlabeled traffic allowed by default [ 0.950001] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0 [ 0.951628] hpet0: 3 comparators, 64-bit 100.000000 MHz counter [ 0.955300] amd_nb: Cannot enumerate AMD northbridges [ 0.956333] Switched to clocksource kvm-clock [ 0.974857] pnp: PnP ACPI init [ 0.975916] ACPI: bus type PNP registered [ 0.977892] pnp: PnP ACPI: found 6 devices [ 0.978966] ACPI: bus type PNP unregistered [ 0.989241] NET: Registered protocol family 2 [ 0.990957] TCP established hash table entries: 32768 (order: 6, 262144 bytes) [ 0.993214] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes) [ 0.996210] TCP: Hash tables configured (established 32768 bind 32768) [ 0.998384] TCP: reno registered [ 0.999615] UDP hash table entries: 2048 (order: 5, 196608 bytes) [ 1.001635] UDP-Lite hash table entries: 2048 (order: 5, 196608 bytes) [ 1.003914] NET: Registered protocol family 1 [ 1.005942] RPC: Registered named UNIX socket transport module. [ 1.007003] RPC: Registered udp transport module. [ 1.008065] RPC: Registered tcp transport module. [ 1.009364] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.011202] pci 0000:00:00.0: Limiting direct PCI/PCI transfers [ 1.012793] pci 0000:00:01.0: PIIX3: Enabling Passive Release [ 1.014576] pci 0000:00:01.0: Activating ISA DMA hang workarounds [ 1.016847] Unpacking initramfs... [ 2.440602] debug: unmapping init [mem 0xffff8800bc2e2000-0xffff8800bffbffff] [ 2.444309] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 2.446337] software IO TLB [mem 0xb82e2000-0xbc2e2000] (64MB) mapped at [ffff8800b82e2000-ffff8800bc2e1fff] [ 2.448451] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 10737418240 ms ovfl timer [ 2.451162] RAPL PMU: hw unit of domain pp0-core 2^-0 Joules [ 2.453166] RAPL PMU: hw unit of domain package 2^-0 Joules [ 2.454450] RAPL PMU: hw unit of domain dram 2^-0 Joules [ 2.457566] cryptomgr_test (51) used greatest stack depth: 14128 bytes left [ 2.458105] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 2.458139] Initialise system trusted keyring [ 2.488995] HugeTLB registered 1 GB page size, pre-allocated 0 pages [ 2.491150] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 2.496535] zpool: loaded [ 2.497577] zbud: loaded [ 2.498844] VFS: Disk quotas dquot_6.6.0 [ 2.500472] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 2.505163] NFS: Registering the id_resolver key type [ 2.506967] Key type id_resolver registered [ 2.508929] Key type id_legacy registered [ 2.512613] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 2.514702] Key type big_key registered [ 2.520382] cryptomgr_test (57) used greatest stack depth: 13904 bytes left [ 2.523938] cryptomgr_test (60) used greatest stack depth: 13664 bytes left [ 2.525733] NET: Registered protocol family 38 [ 2.525744] Key type asymmetric registered [ 2.525748] Asymmetric key parser 'x509' registered [ 2.525877] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250) [ 2.526107] io scheduler noop registered [ 2.526112] io scheduler deadline registered (default) [ 2.526186] io scheduler cfq registered [ 2.526192] io scheduler mq-deadline registered [ 2.526196] io scheduler kyber registered [ 2.528383] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 2.528398] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [ 2.545725] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 [ 2.548491] ACPI: Power Button [PWRF] [ 2.551829] GHES: HEST is not enabled! [ 2.611709] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 [ 2.674050] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [ 2.803515] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [ 2.864323] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10 [ 3.010188] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 3.039917] 00:03: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 3.070221] 00:04: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 3.077881] Non-volatile memory driver v1.3 [ 3.081329] Linux agpgart interface v0.103 [ 3.083822] crash memory driver: version 1.1 [ 3.085887] nbd: registered device at major 43 [ 3.101298] virtio_blk virtio1: [vda] 57680 512-byte logical blocks (29.5 MB/28.1 MiB) [ 3.121582] virtio_blk virtio2: [vdb] 2097152 512-byte logical blocks (1.07 GB/1.00 GiB) [ 3.136057] virtio_blk virtio3: [vdc] 5120000 512-byte logical blocks (2.62 GB/2.44 GiB) [ 3.152910] virtio_blk virtio4: [vdd] 5120000 512-byte logical blocks (2.62 GB/2.44 GiB) [ 3.170087] virtio_blk virtio5: [vde] 8388608 512-byte logical blocks (4.29 GB/4.00 GiB) [ 3.183841] virtio_blk virtio6: [vdf] 8388608 512-byte logical blocks (4.29 GB/4.00 GiB) [ 3.191994] rdac: device handler registered [ 3.194673] hp_sw: device handler registered [ 3.196220] emc: device handler registered [ 3.198008] libphy: Fixed MDIO Bus: probed [ 3.202972] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 3.205171] ehci-pci: EHCI PCI platform driver [ 3.206638] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 3.208572] ohci-pci: OHCI PCI platform driver [ 3.210000] uhci_hcd: USB Universal Host Controller Interface driver [ 3.212295] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12 [ 3.215084] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 3.216487] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 3.218645] mousedev: PS/2 mouse device common for all mice [ 3.221695] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1 [ 3.222094] rtc_cmos 00:05: RTC can wake from S4 [ 3.224785] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0 [ 3.225849] rtc_cmos 00:05: alarms up to one day, y3k, 242 bytes nvram, hpet irqs [ 3.232023] hidraw: raw HID events driver (C) Jiri Kosina [ 3.232282] usbcore: registered new interface driver usbhid [ 3.232283] usbhid: USB HID core driver [ 3.232395] drop_monitor: Initializing network drop monitor service [ 3.232459] Netfilter messages via NETLINK v0.30. [ 3.232542] TCP: cubic registered [ 3.232550] Initializing XFRM netlink socket [ 3.232851] NET: Registered protocol family 10 [ 3.234657] NET: Registered protocol family 17 [ 3.234700] Key type dns_resolver registered [ 3.235215] mce: Using 10 MCE banks [ 3.235731] Loading compiled-in X.509 certificates [ 3.236808] Loaded X.509 cert 'Magrathea: Glacier signing key: e34d0e1b7fcf5b414cce75d36d8482945c781ed6' [ 3.236847] registered taskstats version 1 [ 3.239233] modprobe (71) used greatest stack depth: 13456 bytes left [ 3.244653] Key type trusted registered [ 3.247217] modprobe (77) used greatest stack depth: 13136 bytes left [ 3.250432] Key type encrypted registered [ 3.250482] IMA: No TPM chip found, activating TPM-bypass! (rc=-19) [ 3.253489] BERT: Boot Error Record Table support is disabled. Enable it by using bert_enable as kernel parameter. [ 3.256496] rtc_cmos 00:05: setting system clock to 2024-06-05 03:03:15 UTC (1717556595) [ 3.282944] debug: unmapping init [mem 0xffffffff81da0000-0xffffffff82018fff] [ 3.285974] Write protecting the kernel read-only data: 12288k [ 3.288389] debug: unmapping init [mem 0xffff8800017fe000-0xffff8800017fffff] [ 3.291033] debug: unmapping init [mem 0xffff880001b9b000-0xffff880001bfffff] [ 3.302063] random: systemd: uninitialized urandom read (16 bytes read) [ 3.305891] random: systemd: uninitialized urandom read (16 bytes read) [ 3.309033] random: systemd: uninitialized urandom read (16 bytes read) [ 3.315465] systemd[1]: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [ 3.322383] systemd[1]: Detected virtualization kvm. [ 3.324434] systemd[1]: Detected architecture x86-64. [ 3.326120] systemd[1]: Running in initial RAM disk. Welcome to CentOS Linux 7 (Core) dracut-033-572.el7 (Initramfs)! [ 3.336879] systemd[1]: No hostname configured. [ 3.338618] systemd[1]: Set hostname to . [ 3.341697] random: systemd: uninitialized urandom read (16 bytes read) [ 3.343741] systemd[1]: Initializing machine ID from random generator. [ 3.410328] random: systemd: uninitialized urandom read (16 bytes read) [ 3.412716] random: systemd: uninitialized urandom read (16 bytes read) [ 3.416946] random: systemd: uninitialized urandom read (16 bytes read) [ 3.420284] random: systemd: uninitialized urandom read (16 bytes read) [ 3.424704] random: systemd: uninitialized urandom read (16 bytes read) [ 3.427016] random: systemd: uninitialized urandom read (16 bytes read) [ 3.436952] systemd[1]: Reached target Local File Systems. [ OK ] Reached target Local File Systems. [ 3.440853] systemd[1]: Created slice Root Slice. [ OK ] Created slice Root Slice. [ 3.443758] systemd[1]: Listening on udev Control Socket. [ OK ] Listening on udev Control Socket. [ 3.448437] systemd[1]: Listening on Journal Socket. [ OK ] Listening on Journal Socket. [ 3.453294] systemd[1]: Created slice System Slice. [ OK ] Created slice System Slice. [ 3.457680] tsc: Refined TSC clocksource calibration: 2399.962 MHz [ 3.461848] systemd[1]: Starting dracut cmdline hook... Starting dracut cmdline hook... [ 3.465371] systemd[1]: Reached target Timers. [ OK ] Reached target Timers. [ 3.472082] systemd[1]: Starting Setup Virtual Console... Starting Setup Virtual Console... [ 3.478486] systemd[1]: Starting Journal Service... Starting Journal Service... [ 3.490470] systemd[1]: Reached target Swap. [ OK ] Reached target Swap. [ 3.496714] systemd[1]: Reached target Slices. [ OK ] Reached target Slices. [ 3.502487] systemd[1]: Starting Load Kernel Modules... Starting Load Kernel Modules... [ 3.511992] systemd[1]: Starting Create list of required static device nodes for the current kernel... Starting Create list of required st... nodes for the current kernel... [ 3.523678] systemd[1]: Listening on udev Kernel Socket. [ OK ] Listening on udev Kernel Socket. [ 3.528789] systemd[1]: Reached target Sockets. [ OK ] Reached target Sockets. [ 3.540893] systemd[1]: Started Setup Virtual Console. [ OK ] Started Setup Virtual Console. [ 3.548858] systemd[1]: Started Load Kernel Modules. [ OK ] Started Load Kernel Modules. [ 3.553689] systemd[1]: Started Create list of required static device nodes for the current kernel. [ OK ] Started Create list of required sta...ce nodes for the current kernel. [ 3.560739] systemd[1]: Started Journal Service. [ OK ] Started Journal Service. Starting Create Static Device Nodes in /dev... Starting Apply Kernel Variables... [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Started Apply Kernel Variables. [ OK ] Started dracut cmdline hook. Starting dracut pre-udev hook... [ OK ] [ 4.064421] random: fast init done Started dracut pre-udev hook. Starting udev Kernel Device Manager... [ OK ] Started udev Kernel Device Manager. Starting dracut pre-trigger hook... [ 4.099484] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input2 [ OK ] Started dracut pre-trigger hook. Starting udev Coldplug all Devices... Mounting Configuration File System... [ OK ] Mounted Configuration File System. [ OK ] Started udev Coldplug all Devices. Starting dracut initqueue hook... Starting Show Plymouth Boot Screen... [ OK ] Reached target System Initialization. [ 4.250243] scsi host0: ata_piix [ 4.256764] scsi host1: ata_piix [ 4.267919] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc320 irq 14 [ 4.270826] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc328 irq 15 [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Paths. [ OK ] Started Forward Password Requests to Plymouth Directory Watch. [ OK ] Reached target Basic System. %G[ 4.336648] ip (319) used greatest stack depth: 13080 bytes left [ 4.404530] ip (346) used greatest stack depth: 12336 bytes left [ 6.712345] dracut-initqueue[281]: RTNETLINK answers: File exists [ 6.958573] dracut-initqueue[281]: bs=4096, sz=32212254720 bytes [ OK ] Started dracut initqueue hook. Mounting /sysroot... [ OK ] Reached target Initrd Root File System. Starting Reload Configuration from the Real Root... [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ 7.706195] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ OK ] Mounted /sysroot. [ OK ] Started Reload Configuration from the Real Root. [ OK ] Reached target Initrd File Systems. [ OK ] Reached target Initrd Default Target. Starting dracut pre-pivot and cleanup hook... [ OK ] Started dracut pre-pivot and cleanup hook. Starting Cleaning Up and Shutting Down Daemons... [ OK ] Stopped target Timers. Starting Plymouth switch root service... [ OK ] Stopped dracut pre-pivot and cleanup hook. [ OK ] Stopped target Remote File Systems. [ OK ] Stopped target Remote File Systems (Pre). [ OK ] Stopped dracut initqueue hook. [ OK ] Stopped target Initrd Default Target. [ OK ] Stopped target Basic System. [ OK ] Stopped target System Initialization. [ OK ] Stopped udev Coldplug all Devices. [ OK ] Stopped dracut pre-trigger hook. Stopping udev Kernel Device Manager... [ OK ] Stopped target Local File Systems. [ OK ] Stopped target Swap. [ OK ] Stopped Apply Kernel Variables. [ OK ] Stopped Load Kernel Modules. [ OK ] Stopped target Sockets. [ OK ] Stopped target Paths. [ OK ] Stopped target Slices. [ OK ] Stopped udev Kernel Device Manager. [ OK ] Started Cleaning Up and Shutting Down Daemons. [ OK ] Stopped Create Static Device Nodes in /dev. [ OK ] Stopped Create list of required sta...ce nodes for the current kernel. [ OK ] Stopped dracut pre-udev hook. [ OK ] Stopped dracut cmdline hook. [ OK ] Closed udev Kernel Socket. [ OK ] Closed udev Control Socket. Starting Cleanup udevd DB... [ OK ] Started Cleanup udevd DB. [ OK ] Reached target Switch Root. [ OK ] Started Plymouth switch root service. Starting Switch Root... [ 8.331557] systemd-journald[106]: Received SIGTERM from PID 1 (systemd). [ 8.683665] SELinux: Disabled at runtime. [ 8.818700] ip_tables: (C) 2000-2006 Netfilter Core Team [ 8.829942] systemd[1]: Inserted module 'ip_tables' Welcome to CentOS Linux 7 (Core)! [ OK ] Stopped Switch Root. [ OK ] Stopped Journal Service. Starting Journal Service... Starting Create list of required st... nodes for the current kernel... [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Created slice system-selinux\x2dpol...grate\x2dlocal\x2dchanges.slice. Mounting Debug File System... [ OK ] Stopped target Switch Root. [ OK ] Stopped target Initrd File Systems. Mounting POSIX Message Queue File System... [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Set up automount Arbitrary Executab...ats File System Automount Point. [ OK ] Created slice system-getty.slice. Mounting Huge Pages File System... Starting Remount Root and Kernel File Systems... Starting Set Up Additional Binary Formats... [ OK ] Listening on udev Kernel Socket. Starting Load Kernel Modules... [ OK ] Stopped target Initrd Root File System. [ OK ] Created slice User and Session Slice. [ OK ] Reached target Slices. [ OK ] Listening on Delayed Shutdown Socket. [ OK ] Reached target rpc_pipefs.target. Starting Read and set NIS domainname from /etc/sysconfig/network... [ OK ] Listening on udev Control Socket. Starting udev Coldplug all Devices... [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Started Create list of required sta...ce nodes for the current kernel. Mounting Arbitrary Executable File Formats File System... Starting Create Static Device Nodes in /dev... [ OK ] Mounted Huge Pages File System. [ OK ] Mounted Debug File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Started Load Kernel Modules. Starting Apply Kernel Variables... [ OK ] Mounted Arbitrary Executable File Formats File System. [ OK ] Started Read and set NIS domainname from /etc/sysconfig/network. [ OK ] Started Journal Service. [ OK ] Started Apply Kernel Variables. [ OK ] Started udev Coldplug all Devices. [ OK ] Started Set Up Additional Binary Formats. [FAILED] Failed to start Remount Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. Starting Flush Journal to Persistent Storage... Starting Configure read-only root support... [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Reached target Local File Systems (Pre). Mounting /mnt... Starting udev Kernel Device Manager... [ OK ] Mounted /mnt. [ 9.970088] systemd-journald[568]: Received request to flush runtime journal from PID 1 [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Started udev Kernel Device Manager. [ 10.328657] input: PC Speaker as /devices/platform/pcspkr/input/input3 [ OK ] Found device /dev/ttyS1. [ OK ] Found device /dev/ttyS0. [ 10.411423] piix4_smbus 0000:00:01.3: SMBus Host Controller at 0x700, revision 0 [ OK ] Found device /dev/vda. [ 10.466451] cryptd: max_cpu_qlen set to 1000 Mounting /home/green/git/lustre-release... [ OK ] Found device /dev/disk/by-label/SWAP. Activating swap /dev/disk/by-label/SWAP... [ 10.522172] AVX version of gcm_enc/dec engaged. [ 10.524576] AES CTR mode by8 optimization enabled [ 10.527297] Adding 1048572k swap on /dev/vdb. Priority:-2 extents:1 across:1048572k FS [ OK ] Activated swap /dev/disk/by-label/SWAP. [ OK ] Reached target Swap. [ 10.556153] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ OK ] Mounted /home/green/git/lustre-release. [ 10.581852] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [ 10.586296] alg: No test for __generic-gcm-aes-aesni (__driver-generic-gcm-aes-aesni) %G[ 10.751794] EDAC MC: Ver: 3.0.0 [ 10.776236] EDAC sbridge: Ver: 1.1.2 [ 13.668173] mount.nfs (774) used greatest stack depth: 10704 bytes left [ OK ] Started Configure read-only root support. Starting Load/Save Random Seed... [ OK ] Reached target Local File Systems. Starting Mark the need to relabel after reboot... Starting Rebuild Journal Catalog... Starting Tell Plymouth To Write Out Runtime Data... Starting Preprocess NFS configuration... Starting Create Volatile Files and Directories... [ OK ] Started Load/Save Random Seed. [ OK ] Started Mark the need to relabel after reboot. [FAILED] Failed to start Rebuild Journal Catalog. See 'systemctl status systemd-journal-catalog-update.service' for details. Starting Update is Completed... [ OK ] Started Tell Plymouth To Write Out Runtime Data. [FAILED] Failed to start Create Volatile Files and Directories. See 'systemctl status systemd-tmpfiles-setup.service' for details. Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Preprocess NFS configuration. [ OK ] Started Update is Completed. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Reached target System Initialization. [ OK ] Listening on RPCbind Server Activation Socket. [ OK ] Started Flexible branding. [ OK ] Reached target Paths. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. Starting Dump dmesg to /var/log/dmesg... Starting GSSAPI Proxy Daemon... [ OK ] Started D-Bus System Message Bus. Starting Network Manager... Starting Login Service... [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Reached target Timers. [ OK ] Started Dump dmesg to /var/log/dmesg. [ OK ] Started GSSAPI Proxy Daemon. [ OK ] Reached target NFS client services. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. Starting Permit User Sessions... [ OK ] Started Permit User Sessions. [ OK ] Started Login Service. [ OK ] Started Network Manager. Starting Network Manager Wait Online... [ OK ] Reached target Network. Starting OpenSSH server daemon... Starting /etc/rc.d/rc.local Compatibility... Starting Hostname Service... [ OK ] Started OpenSSH server daemon. [ OK ] Started /etc/rc.d/rc.local Compatibility. [ OK ] Started Hostname Service. Starting Network Manager Script Dispatcher Service... Starting Terminate Plymouth Boot Screen... Starting Wait for Plymouth Boot Screen to Quit... [ OK ] Started Network Manager Script Dispatcher Service. CentOS Linux 7 (Core) Kernel 3.10.0-7.9-debug on an x86_64 oleg148-server login: [ 23.120369] device-mapper: uevent: version 1.0.3 [ 23.121923] device-mapper: ioctl: 4.37.1-ioctl (2018-04-03) initialised: dm-devel@redhat.com [ 27.512547] libcfs: loading out-of-tree module taints kernel. [ 27.514156] libcfs: module verification failed: signature and/or required key missing - tainting kernel [ 27.538792] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_hostid [ 32.221715] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing load_modules_local[ 32.430542] alg: No test for adler32 (adler32-zlib) [ 33.181425] libcfs: HW NUMA nodes: 1, HW CPU cores: 4, npartitions: 1 [ 35.010475] Key type lgssc registered [ 38.251860] icp: module license 'CDDL' taints kernel. [ 38.253927] Disabling lock debugging due to kernel taint [ 40.935518] ZFS: Loaded module v0.8.6-1, ZFS pool version 5000, ZFS filesystem version 5 [ 44.066532] LDISKFS-fs (vdc): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 48.946001] LDISKFS-fs (vdd): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 51.118491] LDISKFS-fs (vde): file extents enabled, maximum tree depth=5 [ 51.122534] LDISKFS-fs (vde): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 53.301257] LDISKFS-fs (vdf): file extents enabled, maximum tree depth=5 [ 53.304659] LDISKFS-fs (vdf): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 56.274530] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing load_modules_local[ 59.301153] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 59.316672] Lustre: lustre-MDT0000: mounting server target with '-t lustre' deprecated, use '-t lustre_tgt'[ 59.322801] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 60.413389] Lustre: lustre-MDT0000: new disk, initializing[ 60.454579] mount.lustre (7100) used greatest stack depth: 10184 bytes left [ 61.161065] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug vfstrace rpctrace dlmtrace neterror ha config ioctl super lfsck all[ 65.128595] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 65.146248] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 65.197805] Lustre: lustre-MDT0001: new disk, initializing [ 65.882242] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug vfstrace rpctrace dlmtrace neterror ha config ioctl super lfsck allLDISKFS-fs (dm-2): file extents enabled, maximum tree depth=5 [ 70.144628] LDISKFS-fs (dm-2): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 70.166341] LDISKFS-fs (dm-2): file extents enabled, maximum tree depth=5 [ 70.169533] LDISKFS-fs (dm-2): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 70.230098] Lustre: lustre-OST0000: new disk, initializing [ 71.424470] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug vfstrace rpctrace dlmtrace neterror ha config ioctl super lfsck allLDISKFS-fs (dm-3): file extents enabled, maximum tree depth=5 [ 75.556934] LDISKFS-fs (dm-3): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 75.571698] LDISKFS-fs (dm-3): file extents enabled, maximum tree depth=5 [ 75.574385] LDISKFS-fs (dm-3): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 75.596963] Lustre: lustre-OST0001: new disk, initializing [ 76.794477] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug vfstrace rpctrace dlmtrace neterror ha config ioctl super lfsck allLustre: DEBUG MARKER: Using TIMEOUT=20[ 86.232427] random: crng init done [ 91.928030] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing check_logdir /tmp/testlogs/Lustre: DEBUG MARKER: oleg148-server.virtnet: executing yml_node [ 93.853992] Lustre: DEBUG MARKER: Client: 2.15.63.95Lustre: DEBUG MARKER: MDS: 2.15.63.95 [ 95.359038] Lustre: DEBUG MARKER: OSS: 2.15.63.95Lustre: DEBUG MARKER: -----============= acceptance-small: replay-dual ============----- Tue Jun 4 23:04:48 EDT 2024 [ 100.806533] Lustre: DEBUG MARKER: excepting tests: 14b 21bLustre: DEBUG MARKER: skipping tests SLOW=no: 21b [ 102.214837] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing check_config_client /mnt/lustreLustre: DEBUG MARKER: Using TIMEOUT=20 [ 109.783921] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 allLustre: DEBUG MARKER: == replay-dual test 0a: expired recovery with lost client ========================================================== 23:05:03 (1717556703) [ 113.482482] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000Lustre: Failing over lustre-MDT0000 [ 114.688371] Lustre: server umount lustre-MDT0000 completeLustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 115.292004] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 116.040080] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server.Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 116.040494] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 116.040499] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 116.041134] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 116.041235] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 116.506419] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 116.512005] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 121.048234] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 121.048236] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 121.048274] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 121.048306] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 121.507698] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 121.507714] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 126.055674] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 126.055732] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 126.055836] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 126.055877] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 126.512773] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 126.512804] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 128.851176] LDISKFS-fs (dm-0): recovery complete [ 128.852935] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 128.866537] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 128.972753] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 128.972753] mount.lustre (16840) used greatest stack depth: 10120 bytes left [ 130.023743] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 131.522189] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnectLustre: lustre-MDT0000: recovery is timed out, evict stale exports [ 201.522846] Lustre: 16869:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-MDT0000: disconnect stale client e27953ae-e9cc-4c2f-9951-afd93ada10ad@192.168.201.48@tcpLustre: lustre-MDT0000: disconnecting 1 stale clients [ 201.534542] Lustre: 16869:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2874:target_recovery_thread()) too long recovery - read logs[ 201.541105] LustreError: dumping log to /tmp/lustre-log.1717556793.16869 [ 214.934031] Lustre: DEBUG MARKER: == replay-dual test 0b: lost client during waiting for next transno ========================================================== 23:06:47 (1717556807) [ 217.156155] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000Lustre: Failing over lustre-MDT0000 [ 217.860319] Lustre: server umount lustre-MDT0000 completeLustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete[ 219.080184] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 219.101317] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 219.112238] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 222.935829] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 224.088159] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 224.088211] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 224.088213] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 224.088250] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 227.935936] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 227.936156] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 229.095878] Lustre: lustre-MDT0001: haven't heard from client e27953ae-e9cc-4c2f-9951-afd93ada10ad (at 192.168.201.48@tcp) in 32 seconds. I think it's dead, and I am evicting it. exp ffff88012c87c000, cur 1717556820 expire 1717556790 last 1717556788 [ 229.095880] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 229.095923] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 229.095991] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 231.118117] LDISKFS-fs (dm-0): recovery complete [ 231.119660] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 231.152582] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 232.022743] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 236.233489] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 242.735931] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 247.744728] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 1:02 [ 252.753271] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:57 [ 257.761382] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:52 [ 259.239725] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:47 [ 261.271974] Lustre: lustre-OST0000: haven't heard from client 00e1da05-2ee8-481d-87da-ad718c36766d (at 192.168.201.48@tcp) in 31 seconds. I think it's dead, and I am evicting it. exp ffff88009238d800, cur 1717556851 expire 1717556821 last 1717556820 [ 261.279317] Lustre: lustre-MDT0001: haven't heard from client 00e1da05-2ee8-481d-87da-ad718c36766d (at 192.168.201.48@tcp) in 33 seconds. I think it's dead, and I am evicting it. exp ffff88009238f800, cur 1717556853 expire 1717556823 last 1717556820 [ 262.768462] Lustre: lustre-OST0001: haven't heard from client 00e1da05-2ee8-481d-87da-ad718c36766d (at 192.168.201.48@tcp) in 33 seconds. I think it's dead, and I am evicting it. exp ffff88012ded6800, cur 1717556853 expire 1717556823 last 1717556820 [ 267.775821] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:42 [ 272.783682] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:37 [ 277.792012] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:32 [ 282.800179] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:27 [ 287.808180] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:22 [ 292.818402] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:17 [ 297.824242] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:12 [ 302.832701] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:07 [ 305.520475] Lustre: lustre-MDT0000: Denying connection for new client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp), waiting for 3 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 0:02 [ 305.528211] Lustre: lustre-MDT0000: recovery is timed out, evict stale exports [ 305.532068] Lustre: 19064:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-MDT0000: disconnect stale client 54d9dd0e-3b73-4c3d-a150-e9e73188ede9@ [ 305.540434] Lustre: 19064:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-MDT0000: disconnect stale client 00e1da05-2ee8-481d-87da-ad718c36766d@ [ 309.689987] Lustre: lustre-MDT0000: disconnecting 2 stale clients [ 312.079269] Lustre: DEBUG MARKER: == replay-dual test 1: |X| simple create ================= 23:08:22 (1717556902) [ 312.666989] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 312.726380] Lustre: Failing over lustre-MDT0000 [ 312.970720] Lustre: server umount lustre-MDT0000 complete [ 312.976177] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 315.576186] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 315.582516] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 315.586784] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 316.360611] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 316.361462] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 316.361514] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 316.362570] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 316.362571] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 316.391017] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 317.968419] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 317.968438] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 321.367777] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 321.367873] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 321.367885] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 321.367929] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 322.977167] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 322.977176] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 326.375934] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 326.375939] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 326.375988] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 326.375994] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 326.660138] LDISKFS-fs (dm-0): recovery complete [ 326.662109] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 326.716562] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 327.908915] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 327.985158] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 332.591145] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 333.077042] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 336.113768] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 338.903211] Lustre: DEBUG MARKER: == replay-dual test 2: |X| mkdir adir ==================== 23:08:48 (1717556928) [ 339.618881] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 341.688357] Lustre: Failing over lustre-MDT0000 [ 341.831967] Lustre: server umount lustre-MDT0000 complete [ 341.832080] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 341.832165] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 341.832207] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 341.832292] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 341.832296] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 341.832352] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 341.867382] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 343.016686] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 343.021004] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 346.839831] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 346.839842] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 346.839890] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 346.839902] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 348.016264] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 348.019926] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 351.849491] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 351.849609] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 351.849613] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 351.849664] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 353.024454] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 353.024460] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 355.264722] LDISKFS-fs (dm-0): recovery complete [ 355.266044] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 355.304290] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 356.234834] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 358.031913] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 361.105744] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 361.569533] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 364.639493] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 366.861028] Lustre: DEBUG MARKER: == replay-dual test 3: |X| mkdir adir, mkdir adir/bdir === 23:09:17 (1717556957) [ 367.437303] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 367.489035] Lustre: Failing over lustre-MDT0000 [ 368.054486] Lustre: server umount lustre-MDT0000 complete [ 368.059765] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 370.408056] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 370.408400] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 370.408467] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 370.408507] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 370.408529] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 370.408598] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 370.408667] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 370.443034] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 373.056111] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 373.056126] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 375.416849] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 375.416904] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 375.416954] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 375.416996] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 378.063792] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 378.063854] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 380.424165] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 380.424220] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 380.424270] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 380.424314] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 380.859179] LDISKFS-fs (dm-0): recovery complete [ 380.862034] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 380.900212] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 381.864330] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 383.072142] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 386.647771] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 387.090143] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 390.016365] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 392.231939] Lustre: DEBUG MARKER: == replay-dual test 4: |X| mkdir adir (-EEXIST), mkdir adir/bdir ========================================================== 23:09:42 (1717556982) [ 392.750950] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 392.806055] Lustre: Failing over lustre-MDT0000 [ 393.095047] Lustre: server umount lustre-MDT0000 complete [ 393.099899] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 395.991856] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 395.991862] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 395.991888] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 395.992007] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 395.997367] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 396.013575] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 396.013767] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 396.022612] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 398.095916] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 398.095925] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 400.999907] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 400.999910] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 400.999959] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 401.000067] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 403.103748] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 403.103807] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 405.953044] LDISKFS-fs (dm-0): recovery complete [ 405.954775] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 405.986191] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 406.848796] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 408.111865] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 411.613302] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 411.986866] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 414.773821] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 416.896014] Lustre: DEBUG MARKER: == replay-dual test 5: open, unlink |X| close ============ 23:10:07 (1717557007) [ 417.432654] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 417.478597] Lustre: Failing over lustre-MDT0000 [ 418.135616] Lustre: server umount lustre-MDT0000 complete [ 418.141580] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 421.063911] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 421.064030] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 421.064167] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 421.079083] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 421.079312] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 421.088527] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 421.088764] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 421.098023] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 423.135702] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 423.135737] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 426.071703] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 426.071795] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 426.071814] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 426.071831] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 428.143756] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 428.143810] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 430.346092] LDISKFS-fs (dm-0): recovery complete [ 430.347854] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 430.374353] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 431.143176] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 433.152026] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 435.928517] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 436.263656] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 438.791590] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 440.784426] Lustre: DEBUG MARKER: == replay-dual test 6: open1, open2, unlink |X| close1 [fail mds1] close2 ========================================================== 23:10:31 (1717557031) [ 441.306657] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 441.359555] Lustre: Failing over lustre-MDT0000 [ 443.171518] Lustre: server umount lustre-MDT0000 complete [ 443.176940] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 445.448125] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 445.448400] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 445.448469] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 445.448521] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 445.448559] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 445.463795] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 445.463800] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 445.463988] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 445.486627] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 448.175728] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 448.175731] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 450.455733] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 450.455834] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 450.455841] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 450.455894] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 453.183403] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 453.183482] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 454.228983] LDISKFS-fs (dm-0): recovery complete [ 454.230613] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 454.255050] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 454.994854] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 458.191659] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 459.905061] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 460.294777] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 462.974940] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 465.008656] Lustre: DEBUG MARKER: == replay-dual test 8: replay of resent request ========== 23:10:55 (1717557055) [ 465.249254] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 481.262876] LustreError: 11744:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff8800a1471180 x1800988651528960/t38654705670(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:18/0 lens 512/448 e 0 to 0 dl 1717557068 ref 1 fl Interpret:/200/0 rc 0/0 job:'mcreate.0' uid:0 gid:0 [ 481.274321] Lustre: lustre-MDT0000: Client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp) reconnecting [ 482.004180] Lustre: 7121:0:(/home/green/git/lustre-release/lustre/mdt/mdt_recovery.c:148:mdt_req_from_lrd()) @@@ restoring transno req@ffff88007c6ce680 x1800988651528960/t38654705670(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:34/0 lens 512/2880 e 0 to 0 dl 1717557084 ref 1 fl Interpret:/202/0 rc 0/0 job:'mcreate.0' uid:0 gid:0 [ 482.073785] Lustre: Failing over lustre-MDT0000 [ 484.359821] Lustre: server umount lustre-MDT0000 complete [ 484.359894] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 484.359917] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 484.359974] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 484.360034] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 484.360043] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 484.360076] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 484.390965] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 486.276823] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 486.281861] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 489.367754] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 489.373605] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 489.373610] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 489.373620] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 491.279709] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 491.279714] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 494.375681] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 494.375698] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 494.375754] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 494.375763] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 495.142603] LDISKFS-fs (dm-0): recovery complete [ 495.145052] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 495.175077] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 496.084157] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 496.287718] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 500.789273] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 501.138272] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 503.738960] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 505.648019] Lustre: DEBUG MARKER: == replay-dual test 9: resending a replayed create ======= 23:11:36 (1717557096) [ 506.382533] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 506.436736] Lustre: Failing over lustre-MDT0000 [ 510.263757] Lustre: server umount lustre-MDT0000 complete [ 510.263929] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 510.263941] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 510.263987] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 510.264103] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 510.264202] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 510.264205] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 510.290179] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 510.295509] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 511.323675] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 511.323679] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 515.271759] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 515.271825] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 515.271835] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 515.271870] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 516.319801] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 516.319807] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 519.482793] LDISKFS-fs (dm-0): recovery complete [ 519.484536] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 519.514848] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 520.320134] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 521.327724] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 524.588940] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 537.356057] LustreError: 4854:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff8800a162b800 x1800988651535424/t42949672962(42949672962) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:74/0 lens 528/448 e 0 to 0 dl 1717557124 ref 1 fl Complete:/204/0 rc 0/0 job:'mcreate.0' uid:0 gid:0 [ 537.942871] Lustre: lustre-MDT0000: Client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp) reconnected, waiting for 3 clients in recovery for 0:53 [ 538.331996] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 541.173103] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 542.981100] Lustre: DEBUG MARKER: == replay-dual test 10: resending a replayed unlink ====== 23:12:14 (1717557134) [ 543.684655] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 543.732358] Lustre: Failing over lustre-MDT0000 [ 544.615722] Lustre: server umount lustre-MDT0000 complete [ 544.615756] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 544.615829] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 544.615884] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 544.616005] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 544.634185] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 544.634344] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 544.643042] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 546.371146] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 546.374464] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 549.623755] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 549.623927] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 549.623941] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 549.624002] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 551.375675] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 551.375681] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 554.631767] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 554.631893] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 554.631933] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 554.631960] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 556.383719] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 556.383721] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 556.734205] LDISKFS-fs (dm-0): recovery complete [ 556.735864] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 556.767210] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 557.543165] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 561.391621] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 561.835860] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 577.419906] LustreError: 7275:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff880084acea00 x1800988651542784/t47244640260(47244640260) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:114/0 lens 528/448 e 0 to 0 dl 1717557164 ref 1 fl Complete:/204/0 rc 0/0 job:'mcreate.0' uid:0 gid:0 [ 578.006947] Lustre: lustre-MDT0000: Client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp) reconnected, waiting for 3 clients in recovery for 0:53 [ 578.396046] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 581.221953] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 583.068582] Lustre: DEBUG MARKER: == replay-dual test 11: both clients timeout during replay ========================================================== 23:12:54 (1717557174) [ 583.781555] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 583.827096] Lustre: Failing over lustre-MDT0000 [ 586.436490] Lustre: server umount lustre-MDT0000 complete [ 586.441923] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 586.871727] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 586.871820] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 586.871849] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 586.871883] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 586.871983] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 586.872042] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 586.872057] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 586.906418] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 591.439684] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 591.439689] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 591.879705] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 591.879768] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 591.879777] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 591.879799] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 596.447532] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 596.447534] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 596.591450] LDISKFS-fs (dm-0): recovery complete [ 596.592670] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 596.620932] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 597.396672] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 598.453207] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 601.455714] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount FULL mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 601.455714] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 601.692151] LustreError: 9711:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff88012fd97b80 x1800988651549696/t51539607554(51539607554) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:154/0 lens 528/448 e 0 to 0 dl 1717557204 ref 1 fl Complete:/204/0 rc 0/0 job:'mcreate.0' uid:0 gid:0Lustre: lustre-MDT0000: Client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp) reconnected, waiting for 3 clients in recovery for 0:53 [ 618.135039] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 19 secLustre: DEBUG MARKER: == replay-dual test 12: open resend timeout ============== 23:13:32 (1717557212) [ 621.950516] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000Lustre: Failing over lustre-MDT0000 [ 622.792590] Lustre: server umount lustre-MDT0000 completeLustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 626.508071] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server.Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete[ 626.727849] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server.Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 631.504216] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 631.504287] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 631.736031] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 631.736040] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 631.736074] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 631.736084] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 635.783123] LDISKFS-fs (dm-0): recovery complete [ 635.784713] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 635.819992] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 636.511961] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 636.666231] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 642.252286] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 644.143760] Lustre: DEBUG MARKER: == replay-dual test 13: close resend timeout ============= 23:13:55 (1717557235) [ 644.861951] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 644.911565] Lustre: Failing over lustre-MDT0000 [ 645.895889] Lustre: server umount lustre-MDT0000 complete [ 645.895896] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 645.895985] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 645.896021] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 645.896138] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 645.913238] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 645.913410] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 645.922201] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 646.536407] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 646.536409] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 650.903725] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 650.903888] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 650.903920] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 650.903924] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 651.535773] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 651.535775] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 655.911637] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 655.911652] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 655.911662] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 655.911727] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 656.543601] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 656.543607] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 657.790947] LDISKFS-fs (dm-0): recovery complete [ 657.792501] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 657.819617] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 658.681178] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 661.551782] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 664.439811] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 664.836790] Lustre: DEBUG MARKER: SKIP: replay-dual test_14b skipping ALWAYS excluded test 14b [ 666.953689] Lustre: DEBUG MARKER: == replay-dual test 15a: timeout waiting for lost client during replay, 1 client completes ========================================================== 23:14:17 (1717557257) [ 667.647026] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 667.702772] Lustre: Failing over lustre-MDT0000 [ 667.895787] Lustre: server umount lustre-MDT0000 complete [ 667.895831] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 667.895910] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 667.895949] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 667.896033] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 667.896055] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 667.896079] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 667.923963] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 671.574414] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 672.903858] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 672.903998] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 672.904008] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 672.904043] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 676.575639] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 677.911734] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 677.911938] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 677.911943] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 677.911988] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 680.773502] LDISKFS-fs (dm-0): recovery complete [ 680.774943] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 680.803641] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 681.583610] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 681.665296] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 751.520407] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 751.523150] Lustre: lustre-MDT0000: recovery is timed out, evict stale exports [ 751.525649] Lustre: 16634:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-MDT0000: disconnect stale client 09550690-d377-44ad-9076-058689380776@ [ 752.421775] Lustre: lustre-MDT0000: disconnecting 1 stale clients [ 752.805516] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 755.644605] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 757.516681] Lustre: DEBUG MARKER: == replay-dual test 15c: remove multiple OST orphans ===== 23:15:48 (1717557348) [ 769.718886] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 769.792457] Lustre: Failing over lustre-MDT0000 [ 771.015866] Lustre: server umount lustre-MDT0000 complete [ 771.015875] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 771.015935] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 771.016013] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 771.016063] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 771.016234] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 771.016431] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 771.043657] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 774.213148] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 776.023677] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 776.023804] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 776.023852] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 776.023864] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 779.215850] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 781.031927] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 781.032021] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 781.032061] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 781.032078] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 782.638813] LDISKFS-fs (dm-0): recovery complete [ 782.640774] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 782.668765] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 783.419616] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 784.223802] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 853.520416] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 853.524312] Lustre: lustre-MDT0000: recovery is timed out, evict stale exports [ 853.526893] Lustre: 18952:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-MDT0000: disconnect stale client 3f634507-86e4-4217-8350-787312c31466@ [ 854.082170] Lustre: lustre-MDT0000: disconnecting 1 stale clients [ 854.449642] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 857.181678] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 859.073883] Lustre: DEBUG MARKER: == replay-dual test 16: fail MDS during recovery (3571) == 23:17:30 (1717557450) [ 859.675068] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 859.724656] Lustre: Failing over lustre-MDT0000 [ 860.740589] Lustre: server umount lustre-MDT0000 complete [ 862.855908] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 862.855929] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 862.856040] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 862.872484] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 862.872657] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 862.883087] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 862.883269] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 862.893430] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 865.743797] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 867.863823] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 867.871164] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 867.871176] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 867.871255] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 870.751296] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 872.582274] LDISKFS-fs (dm-0): recovery complete [ 872.584377] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 872.609123] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 873.379440] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 875.759686] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 894.371057] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 894.377108] Lustre: Failing over lustre-MDT0000 [ 894.378245] LustreError: 21785:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2927:target_stop_recovery_thread()) lustre-MDT0000: Aborting recovery [ 894.383486] Lustre: 21263:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2310:target_recovery_overseer()) recovery is aborted, evict exports in recovery [ 894.386836] Lustre: 21263:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:1824:abort_req_replay_queue()) @@@ aborted: req@ffff88012c38a300 x1800988652751680/t0(73014444033) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:441/0 lens 528/0 e 1 to 0 dl 1717557491 ref 1 fl Complete:/204/ffffffff rc 0/-1 job:'mcreate.0' uid:0 gid:0 [ 894.397396] Lustre: 21263:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2310:target_recovery_overseer()) recovery is aborted, evict exports in recovery [ 894.406212] Lustre: 21263:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2310:target_recovery_overseer()) recovery is aborted, evict exports in recovery [ 894.412246] LustreError: 21263:0:(/home/green/git/lustre-release/lustre/ptlrpc/client.c:1281:ptlrpc_import_delay_req()) @@@ IMP_CLOSED req@ffff8800a23c2d80 x1800988655922112/t0(0) o1000->lustre-MDT0001-osp-MDT0000@0@lo:24/4 lens 336/33016 e 0 to 0 dl 0 ref 2 fl Rpc:QU/200/ffffffff rc 0/-1 job:'tgt_recover_0.0' uid:0 gid:0 [ 894.419351] LustreError: 21263:0:(/home/green/git/lustre-release/lustre/obdclass/llog_osd.c:983:llog_osd_next_block()) lustre-MDT0001-osp-MDT0000: can't read llog block from log [0x240000401:0x1:0x0] offset 32768: rc = -5 [ 894.425437] LustreError: 21263:0:(/home/green/git/lustre-release/lustre/obdclass/llog.c:805:llog_process_thread()) lustre-MDT0001-osp-MDT0000 retry remote llog process [ 894.431821] LustreError: 21263:0:(/home/green/git/lustre-release/lustre/ptlrpc/client.c:1281:ptlrpc_import_delay_req()) @@@ IMP_CLOSED req@ffff8800a23c2d80 x1800988655922176/t0(0) o700->lustre-MDT0001-osp-MDT0000@0@lo:30/10 lens 264/248 e 0 to 0 dl 0 ref 2 fl Rpc:QU/200/ffffffff rc 0/-1 job:'tgt_recover_0.0' uid:0 gid:0 [ 894.443945] LustreError: 21263:0:(/home/green/git/lustre-release/lustre/fid/fid_request.c:233:seq_client_alloc_seq()) cli-cli-lustre-MDT0001-osp-MDT0000: Cannot allocate new meta-sequence: rc = -5 [ 894.461491] LustreError: 21263:0:(/home/green/git/lustre-release/lustre/fid/fid_request.c:335:seq_client_alloc_fid()) cli-cli-lustre-MDT0001-osp-MDT0000: Can't allocate new sequence: rc = -5 [ 894.513915] Lustre: 21263:0:(/home/green/git/lustre-release/lustre/mdt/mdt_handler.c:7962:mdt_postrecov()) lustre-MDT0000: auto trigger paused LFSCK failed: rc = -6 [ 897.703939] Lustre: server umount lustre-MDT0000 complete [ 897.705376] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 897.705479] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 897.714024] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 897.714128] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 897.721388] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 899.407733] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 902.712041] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 902.712067] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 902.712106] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 904.415692] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 905.711397] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 905.716667] Lustre: 3681:0:(/home/green/git/lustre-release/lustre/ptlrpc/client.c:2343:ptlrpc_expire_one_request()) @@@ Request sent has timed out for slow reply: [sent 1717557469/real 1717557469] req@ffff88012c389180 x1800988655918656/t0(0) o400->lustre-MDT0000-osp-MDT0001@0@lo:24/4 lens 224/224 e 1 to 1 dl 1717557497 ref 1 fl Rpc:XQr/2c0/ffffffff rc 0/-1 job:'ldlm_l [ 905.723675] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 905.723934] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 905.723938] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 906.461228] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 906.486030] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 907.235576] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 909.423843] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 978.520424] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 978.523415] Lustre: lustre-MDT0000: recovery is timed out, evict stale exports [ 978.525019] Lustre: 22355:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-MDT0000: disconnect stale client bce4acfa-5704-40ff-84cf-0ac904bc2ad5@ [ 979.378762] Lustre: lustre-MDT0000: disconnecting 1 stale clients [ 979.741740] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 982.634920] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 984.778804] Lustre: DEBUG MARKER: == replay-dual test 17: fail OST during recovery (3571) == 23:19:35 (1717557575) [ 985.312792] Lustre: DEBUG MARKER: ost1 REPLAY BARRIER on lustre-OST0000 [ 985.328260] Lustre: Failing over lustre-OST0000 [ 985.399670] Lustre: server umount lustre-OST0000 complete [ 985.400982] LustreError: 11-0: lustre-OST0000-osc-MDT0001: operation ost_statfs to node 0@lo failed: rc = -107 [ 985.404432] Lustre: lustre-OST0000-osc-MDT0001: Connection to lustre-OST0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 986.132712] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 986.680036] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 986.680049] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 986.680180] Lustre: lustre-OST0000-osc-MDT0000: Connection to lustre-OST0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 991.136305] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 991.688003] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 991.688022] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 996.143771] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 996.695957] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 996.695964] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 998.275572] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 998.280757] LDISKFS-fs (dm-2): file extents enabled, maximum tree depth=5 [ 998.324791] LDISKFS-fs (dm-2): recovery complete [ 998.326076] LDISKFS-fs (dm-2): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 998.353464] mount.lustre (24637) used greatest stack depth: 9944 bytes left [ 999.490673] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 999.822442] Lustre: lustre-OST0000: Will be in recovery for at least 1:00, or until 4 clients reconnectLustre: Failing over lustre-OST0000 [ 1020.461214] LustreError: 25296:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2927:target_stop_recovery_thread()) lustre-OST0000: Aborting recoveryLustre: 24650:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2310:target_recovery_overseer()) recovery is aborted, evict exports in recovery [ 1020.469984] Lustre: 24650:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2310:target_recovery_overseer()) recovery is aborted, evict exports in recoveryLustre: 24650:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2310:target_recovery_overseer()) recovery is aborted, evict exports in recovery [ 1020.478256] Lustre: 24650:0:(/home/green/git/lustre-release/lustre/ofd/ofd_obd.c:557:ofd_postrecov()) lustre-OST0000: auto trigger paused LFSCK failed: rc = -6Lustre: server umount lustre-OST0000 complete [ 1032.452257] LDISKFS-fs (dm-2): file extents enabled, maximum tree depth=5 [ 1032.455971] LDISKFS-fs (dm-2): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 1033.702088] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1040.170366] Lustre: lustre-OST0000: Will be in recovery for at least 1:00, or until 4 clients reconnectLustre: 3681:0:(/home/green/git/lustre-release/lustre/ptlrpc/client.c:2343:ptlrpc_expire_one_request()) @@@ Request sent has timed out for slow reply: [sent 1717557592/real 1717557592] req@ffff88012c774000 x1800988655951552/t0(0) o400->lustre-OST0000-osc-MDT0000@0@lo:28/4 lens 224/224 e 2 to 1 dl 1717557632 ref 1 fl Rpc:XQr/2c0/ffffffff rc 0/-1 job:'ldlm_l [ 1040.497685] Lustre: 3681:0:(/home/green/git/lustre-release/lustre/ptlrpc/client.c:2343:ptlrpc_expire_one_request()) @@@ Request sent has timed out for slow reply: [sent 1717557592/real 1717557592] req@ffff88013998aa00 x1800988655951488/t0(0) o400->lustre-OST0000-osc-MDT0001@0@lo:28/4 lens 224/224 e 2 to 1 dl 1717557632 ref 1 fl Rpc:XQr/2c0/ffffffff rc 0/-1 job:'ldlm_lLustre: lustre-OST0000: recovery is timed out, evict stale exports [ 1109.521982] Lustre: 25848:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-OST0000: disconnect stale client 7440a304-071b-40ff-a114-2424d3041d65@Lustre: lustre-OST0000: disconnecting 1 stale clients [ 1110.040899] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) osc.lustre-OST0000-osc-[-0-9a-f]*.ost_server_uuidLustre: DEBUG MARKER: osc.lustre-OST0000-osc-[-0-9a-f]*.ost_server_uuid in FULL state after 0 sec [ 1113.183961] Lustre: DEBUG MARKER: == replay-dual test 18: ldlm_handle_enqueue succeeds on evicted export (3822) ========================================================== 23:21:46 (1717557706)LustreError: 11744:0:(/home/green/git/lustre-release/libcfs/libcfs/fail.c:141:__cfs_fail_timeout_set()) cfs_fail_timeout id 30b sleeping for 40000ms [ 1155.037505] LustreError: 11744:0:(/home/green/git/lustre-release/libcfs/libcfs/fail.c:154:__cfs_fail_timeout_set()) cfs_fail_timeout id 30b awakeLustre: DEBUG MARKER: == replay-dual test 19: resend of open request =========== 23:22:29 (1717557749) [ 1158.731072] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000LustreError: 11744:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff8800a1595880 x1800988652806656/t0(0) o101->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:27/0 lens 576/688 e 0 to 0 dl 1717557832 ref 1 fl Interpret:/200/0 rc 0/0 job:'createmany.0' uid:0 gid:0 [ 1245.050732] Lustre: lustre-MDT0000: Client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp) reconnectingLustre: Failing over lustre-MDT0000 [ 1245.831857] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1245.836791] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1245.868738] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1250.065069] Lustre: server umount lustre-MDT0000 complete [ 1250.068842] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1250.839998] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1250.840078] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1250.840160] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1250.840186] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1255.072055] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1255.072114] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1255.847833] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1255.847941] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1255.847946] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1255.848002] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1258.813310] LDISKFS-fs (dm-0): recovery complete [ 1258.815181] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 1258.839300] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1259.609837] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 1260.079563] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1264.429237] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1264.809504] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 1267.540700] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1269.508079] Lustre: DEBUG MARKER: == replay-dual test 20: recovery time is not increasing == 23:24:20 (1717557860) [ 1270.042601] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 1270.092453] Lustre: Failing over lustre-MDT0000 [ 1270.097634] Lustre: server umount lustre-MDT0000 complete [ 1273.927787] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1273.927841] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1273.927852] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1273.927923] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1273.927986] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1273.928050] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1273.928068] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1273.949344] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1275.103872] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1278.935800] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1278.935907] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1278.935937] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1278.935991] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1280.111687] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1283.068529] LDISKFS-fs (dm-0): recovery complete [ 1283.070034] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 1283.095152] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1283.899535] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 1285.119829] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1424.520501] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1424.524217] Lustre: lustre-MDT0000: recovery is timed out, evict stale exports [ 1424.526467] Lustre: 31351:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-MDT0000: disconnect stale client a99e50ed-5027-44ba-b389-ed5bff168c97@ [ 1424.540603] Lustre: lustre-MDT0000: disconnecting 1 stale clients [ 1424.546141] Lustre: 31351:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:1992:extend_recovery_timer()) lustre-MDT0000: extended recovery timer reached hard limit: 180, extend: 1 [ 1424.555797] Lustre: 31351:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:1992:extend_recovery_timer()) lustre-MDT0000: extended recovery timer reached hard limit: 180, extend: 1 [ 1424.564844] Lustre: 31351:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:1992:extend_recovery_timer()) lustre-MDT0000: extended recovery timer reached hard limit: 180, extend: 1 [ 1424.572532] Lustre: 31351:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:1992:extend_recovery_timer()) lustre-MDT0000: extended recovery timer reached hard limit: 180, extend: 1 [ 1425.157214] Lustre: 31351:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:1992:extend_recovery_timer()) lustre-MDT0000: extended recovery timer reached hard limit: 180, extend: 1 [ 1425.520955] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 1428.687758] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1429.232091] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 1429.285582] Lustre: Failing over lustre-MDT0000 [ 1429.591807] Lustre: server umount lustre-MDT0000 complete [ 1429.593044] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 1429.596305] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1431.795622] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1433.399891] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1433.399949] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1433.400033] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1433.400040] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1433.400104] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1433.405115] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1433.405327] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1436.799887] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1438.407699] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1438.407792] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1438.407797] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1438.407810] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1441.807440] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1442.156081] LDISKFS-fs (dm-0): recovery complete [ 1442.157669] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 1442.182988] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1442.973879] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 1446.815787] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1586.520380] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1586.524187] Lustre: lustre-MDT0000: recovery is timed out, evict stale exports [ 1586.526974] Lustre: 1032:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-MDT0000: disconnect stale client abb743e1-2e93-4cf8-ac90-cafc579fa62b@ [ 1586.537056] Lustre: lustre-MDT0000: disconnecting 1 stale clients [ 1586.539050] Lustre: 1032:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:1992:extend_recovery_timer()) lustre-MDT0000: extended recovery timer reached hard limit: 180, extend: 1 [ 1586.543565] Lustre: 1032:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:1992:extend_recovery_timer()) lustre-MDT0000: extended recovery timer reached hard limit: 180, extend: 1 [ 1586.548055] Lustre: 1032:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:1992:extend_recovery_timer()) lustre-MDT0000: extended recovery timer reached hard limit: 180, extend: 1 [ 1586.551711] Lustre: 1032:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:1992:extend_recovery_timer()) lustre-MDT0000: extended recovery timer reached hard limit: 180, extend: 1 [ 1587.059571] Lustre: 1032:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:1992:extend_recovery_timer()) lustre-MDT0000: extended recovery timer reached hard limit: 180, extend: 1 [ 1587.418776] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 1590.031778] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1592.113906] Lustre: DEBUG MARKER: == replay-dual test 21a: commit on sharing =============== 23:29:42 (1717558182) [ 1592.623664] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 1592.669063] Lustre: Failing over lustre-MDT0000 [ 1593.698536] Lustre: server umount lustre-MDT0000 complete [ 1596.567802] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1596.571433] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 1596.573697] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1597.495890] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1597.495924] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1597.495930] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1597.496053] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1597.496111] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1597.509982] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1598.703694] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1602.503736] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1602.503873] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1602.503932] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1602.503987] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1603.711388] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1605.562517] LDISKFS-fs (dm-0): recovery complete [ 1605.564680] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 1605.603179] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1606.363156] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 1608.719669] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1748.520449] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1748.525053] Lustre: lustre-MDT0000: recovery is timed out, evict stale exports [ 1748.528593] Lustre: 3468:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-MDT0000: disconnect stale client 96e5458a-5579-4750-8fa0-07feba6abdcc@ [ 1751.339454] Lustre: lustre-MDT0000: disconnecting 1 stale clients [ 1751.817463] Lustre: DEBUG MARKER: SKIP: replay-dual test_21b skipping SLOW test 21b [ 1752.227098] Lustre: DEBUG MARKER: == replay-dual test 22a: c1 lfs mkdir -i 1 dir1, M1 drop reply [ 1753.870530] LustreError: 9474:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff8800962ffb80 x1800988652857024/t4294967313(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:619/0 lens 560/448 e 0 to 0 dl 1717558424 ref 1 fl Interpret:/200/0 rc 0/0 job:'lfs.0' uid:0 gid:0 [ 1753.950031] Lustre: Failing over lustre-MDT0001 [ 1755.896019] Lustre: server umount lustre-MDT0001 complete [ 1755.900405] LustreError: 11-0: lustre-MDT0001-osp-MDT0000: operation mds_statfs to node 0@lo failed: rc = -107 [ 1755.907257] Lustre: lustre-MDT0001-osp-MDT0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1755.912045] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1755.912244] Lustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1755.912350] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1755.912465] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1758.675043] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1758.686942] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1760.920107] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1760.920170] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1760.920271] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1763.680427] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1763.680498] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1765.927988] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1765.928018] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1765.928030] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1766.654857] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 1767.558771] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1768.128850] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1771.792161] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1772.599944] Lustre: 9474:0:(/home/green/git/lustre-release/lustre/mdt/mdt_recovery.c:148:mdt_req_from_lrd()) @@@ restoring transno req@ffff880084ad7100 x1800988652857024/t4294967313(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:639/0 lens 560/2880 e 0 to 0 dl 1717558444 ref 1 fl Interpret:/202/0 rc 0/0 job:'lfs.0' uid:0 gid:0 [ 1773.220257] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 1776.653850] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1777.230730] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 1777.277424] Lustre: Failing over lustre-MDT0000 [ 1778.709149] Lustre: server umount lustre-MDT0000 complete [ 1778.718679] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1781.784020] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1781.791678] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 1781.796508] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1781.800234] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1781.800297] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1781.800312] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1781.800472] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1781.800531] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1781.800567] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1783.712364] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1783.712371] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1786.807937] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1786.807993] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1786.808069] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1786.808200] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1788.720165] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1788.720256] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1791.093842] LDISKFS-fs (dm-0): recovery complete [ 1791.096592] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 1791.143734] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1792.234318] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 1793.727858] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1796.960673] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1797.492794] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 1800.504979] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1800.923680] Lustre: DEBUG MARKER: == replay-dual test 22b: c1 lfs mkdir -i 1 d1, M1 drop reply [ 1802.565468] LustreError: 11744:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff88012dfa8e00 x1800988652872320/t8589934616(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:668/0 lens 560/448 e 0 to 0 dl 1717558473 ref 1 fl Interpret:/200/0 rc 0/0 job:'lfs.0' uid:0 gid:0 [ 1802.678256] Lustre: Failing over lustre-MDT0000 [ 1803.758446] Lustre: server umount lustre-MDT0000 complete [ 1803.761691] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1804.025213] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1804.026870] LustreError: 8784:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558396 with bad export cookie 2307922713183084998 [ 1804.026891] LustreError: 7109:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558396 with bad export cookie 2307922713183084998 [ 1804.026962] LustreError: 9468:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558396 with bad export cookie 2307922713183084998 [ 1804.027192] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 1804.029717] Lustre: Failing over lustre-MDT0001 [ 1804.029838] LustreError: 7110:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558396 with bad export cookie 2307922713183085082 [ 1804.029906] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1804.030210] LustreError: 9468:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558396 with bad export cookie 2307922713183085082 [ 1806.248082] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1806.248157] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1806.248169] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1806.248310] Lustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1806.248533] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1806.281605] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1808.752311] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1808.752428] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1809.255648] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1809.255778] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1809.319904] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1821.696054] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 1821.701351] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 1829.256007] Lustre: server umount lustre-MDT0001 complete [ 1829.405048] LustreError: 3681:0:(/home/green/git/lustre-release/lustre/ptlrpc/client.c:1291:ptlrpc_import_delay_req()) @@@ invalidate in flight req@ffff88012dffc000 x1800988656153984/t0(0) o250->MGC192.168.201.148@tcp@0@lo:26/25 lens 520/544 e 0 to 0 dl 0 ref 1 fl Rpc:NQU/200/ffffffff rc 0/-1 job:'kworker.0' uid:0 gid:0 [ 1829.424625] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1829.508542] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1830.462712] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 2 clients reconnect [ 1830.523140] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1833.528137] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1847.840406] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1848.699739] Lustre: 9385:0:(/home/green/git/lustre-release/lustre/mdt/mdt_recovery.c:148:mdt_req_from_lrd()) @@@ restoring transno req@ffff88009103b800 x1800988652872320/t8589934616(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:715/0 lens 560/2880 e 0 to 0 dl 1717558520 ref 1 fl Interpret:/202/0 rc 0/0 job:'lfs.0' uid:0 gid:0 [ 1849.265481] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid,mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 1849.680033] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1853.672133] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1854.232655] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 1854.279390] Lustre: Failing over lustre-MDT0000 [ 1857.842903] Lustre: server umount lustre-MDT0000 complete [ 1857.847492] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1858.567904] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1858.567910] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1858.568018] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1858.568432] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1858.568494] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1858.568583] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1858.568601] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1858.605640] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1862.848515] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1862.848529] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1863.576154] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1863.576188] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1863.576319] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1863.576393] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1867.738111] LDISKFS-fs (dm-0): recovery complete [ 1867.742280] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 1867.789816] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1868.981972] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 1869.019030] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1873.740432] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1874.345866] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 1877.229918] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1877.511325] Lustre: DEBUG MARKER: == replay-dual test 22c: c1 lfs mkdir -i 1 d1, M1 drop update [ 1879.495830] LustreError: 9461:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff88009f9b4380 x1800988656182528/t107374182411(0) o1000->lustre-MDT0001-mdtlov_UUID@0@lo:675/0 lens 2264/4320 e 0 to 0 dl 1717558480 ref 1 fl Interpret:/200/0 rc 0/0 job:'osp_up0-1.0' uid:0 gid:0 [ 1879.599080] Lustre: Failing over lustre-MDT0000 [ 1879.879239] Lustre: server umount lustre-MDT0000 complete [ 1879.888892] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1881.225012] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1881.229299] LustreError: 7108:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558473 with bad export cookie 2307922713183089177 [ 1881.233578] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1882.887703] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1882.887760] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1882.892423] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1882.892468] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1882.892557] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1882.892559] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1882.912639] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1884.880317] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1884.880331] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1887.896019] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1887.896029] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1887.896033] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1887.896082] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1889.888718] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1889.888763] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1892.264984] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 1892.292788] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1893.354699] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 1893.510489] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1894.896130] Lustre: 9405:0:(/home/green/git/lustre-release/lustre/ptlrpc/client.c:2343:ptlrpc_expire_one_request()) @@@ Request sent has timed out for slow reply: [sent 1717558469/real 1717558469] req@ffff88009f9b4e00 x1800988656182528/t0(0) o1000->lustre-MDT0000-osp-MDT0001@0@lo:24/4 lens 2264/4320 e 0 to 1 dl 1717558485 ref 2 fl Rpc:XQr/200/ffffffff rc 0/-1 job:'osp [ 1898.167282] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1898.733063] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 1902.783881] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1903.625041] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 1903.676421] Lustre: Failing over lustre-MDT0000 [ 1904.929693] Lustre: server umount lustre-MDT0000 complete [ 1904.929712] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1907.368231] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1907.368267] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1907.368749] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1907.368754] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1907.369062] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1907.411084] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1907.411382] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1907.427292] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1909.920019] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1909.920028] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1912.376114] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1912.376158] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1912.376166] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1912.387706] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1914.928186] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1914.928196] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1917.383839] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1917.383899] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1917.383974] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1917.384063] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1917.818850] LDISKFS-fs (dm-0): recovery complete [ 1917.821540] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 1917.865200] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1918.916384] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 1919.936813] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1923.679865] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1924.235982] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 1927.952932] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1930.817044] Lustre: DEBUG MARKER: == replay-dual test 22d: c1 lfs mkdir -i 1 d1, M1 drop update [ 1932.793108] LustreError: 10230:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff8800a1d84380 x1800988656210176/t115964117001(0) o1000->lustre-MDT0001-mdtlov_UUID@0@lo:729/0 lens 2264/4320 e 0 to 0 dl 1717558534 ref 1 fl Interpret:/200/0 rc 0/0 job:'osp_up0-1.0' uid:0 gid:0 [ 1932.855000] Lustre: Failing over lustre-MDT0000 [ 1932.951691] Lustre: server umount lustre-MDT0000 complete [ 1932.951704] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1932.951785] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1932.951794] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1932.951917] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1932.969960] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1932.970187] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1932.982057] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1934.039194] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1934.040520] LustreError: 7109:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558526 with bad export cookie 2307922713183092565 [ 1934.040777] Lustre: Failing over lustre-MDT0001 [ 1934.040784] LustreError: 8784:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558526 with bad export cookie 2307922713183092565 [ 1934.040877] LustreError: 7108:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558526 with bad export cookie 2307922713183092565 [ 1934.040883] LustreError: 7108:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558526 with bad export cookie 2307922713183092565 [ 1934.040925] LustreError: 7110:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558526 with bad export cookie 2307922713183092565 [ 1934.976399] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 1934.982099] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1937.959838] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1937.960079] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1937.960120] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1937.965171] Lustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1938.961900] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1938.961956] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1939.378072] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1952.228277] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 1952.239166] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 1955.005686] Lustre: server umount lustre-MDT0001 complete [ 1955.006203] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1955.006317] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1956.008201] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1956.008210] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1956.008320] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1958.961930] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1959.054976] LustreError: 3681:0:(/home/green/git/lustre-release/lustre/ptlrpc/client.c:1291:ptlrpc_import_delay_req()) @@@ invalidate in flight req@ffff8800961a8700 x1800988656213376/t0(0) o250->MGC192.168.201.148@tcp@0@lo:26/25 lens 520/544 e 0 to 0 dl 0 ref 1 fl Rpc:NQU/200/ffffffff rc 0/-1 job:'kworker.0' uid:0 gid:0 [ 1959.075760] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1959.142848] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1960.008046] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 2 clients reconnect [ 1960.094390] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1960.156031] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1964.186451] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1965.055594] Lustre: 17794:0:(/home/green/git/lustre-release/lustre/mdt/mdt_recovery.c:148:mdt_req_from_lrd()) @@@ restoring transno req@ffff88012e65b800 x1800988652906688/t12884901936(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:76/0 lens 560/2880 e 0 to 0 dl 1717558636 ref 1 fl Interpret:/202/0 rc 0/0 job:'lfs.0' uid:0 gid:0 [ 1965.670368] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid,mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 1966.231525] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1970.419039] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1971.222109] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 1971.291681] Lustre: Failing over lustre-MDT0000 [ 1974.167962] Lustre: server umount lustre-MDT0000 complete [ 1974.168033] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1974.168255] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1974.168634] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1974.168870] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1974.185243] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1974.185248] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 1974.185473] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 1974.217586] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1975.054100] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1975.054185] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1979.176017] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1979.176162] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1979.176176] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1979.176299] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1980.048439] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1980.048448] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1984.183649] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1984.183684] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1984.183708] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1984.183729] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1985.001247] LDISKFS-fs (dm-0): recovery complete [ 1985.004597] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 1985.048085] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1985.055942] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 1985.055963] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1986.179087] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 1986.668725] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 1991.009224] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 1991.618212] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 1995.112701] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 1995.497691] Lustre: DEBUG MARKER: == replay-dual test 23a: c1 rmdir d1, M1 drop reply and fail, client2 mkdir d1 ========================================================== 23:36:27 (1717558587) [ 1997.521192] LustreError: 17795:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff88009c3f4e00 x1800988652924288/t17179869209(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:107/0 lens 496/456 e 0 to 0 dl 1717558667 ref 1 fl Interpret:/200/0 rc 0/0 job:'rmdir.0' uid:0 gid:0 [ 2000.135780] Lustre: Failing over lustre-MDT0001 [ 2000.135796] Lustre: lustre-MDT0001-osp-MDT0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2000.135924] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2000.137182] Lustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2003.326420] LustreError: 11-0: lustre-MDT0001-osp-MDT0000: operation mds_statfs to node 0@lo failed: rc = -107 [ 2005.144180] Lustre: server umount lustre-MDT0001 complete [ 2005.144216] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2005.144270] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2006.096920] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2006.096929] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2010.151752] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2010.151758] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2010.151811] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2011.104602] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2011.104630] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2015.160059] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2015.160153] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2015.160280] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2016.092524] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2016.112053] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2016.112109] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2017.373384] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2017.999218] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2021.247423] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2021.981196] Lustre: 17793:0:(/home/green/git/lustre-release/lustre/mdt/mdt_recovery.c:148:mdt_req_from_lrd()) @@@ restoring transno req@ffff8800a6a71500 x1800988652924288/t17179869209(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:133/0 lens 496/2888 e 0 to 0 dl 1717558693 ref 1 fl Interpret:/202/0 rc 0/0 job:'rmdir.0' uid:0 gid:0 [ 2022.562317] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 2026.417505] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2027.137691] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 2027.184902] Lustre: Failing over lustre-MDT0000 [ 2028.134080] Lustre: server umount lustre-MDT0000 complete [ 2028.142679] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2031.239660] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2031.243705] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 2031.246207] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2031.255686] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2031.255733] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2031.255789] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2031.255829] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2031.255859] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2031.273605] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2033.136687] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2033.136703] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2036.264212] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2036.264222] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2036.264289] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2036.264509] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2038.144370] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2038.144397] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2041.130941] LDISKFS-fs (dm-0): recovery complete [ 2041.133646] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2041.181502] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2041.981022] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2043.152736] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2047.140389] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2047.622586] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 2050.647889] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2051.025097] Lustre: DEBUG MARKER: == replay-dual test 23b: c1 rmdir d1, M1 drop reply and fail M0/M1, c2 mkdir d1 ========================================================== 23:37:23 (1717558643) [ 2052.818682] LustreError: 17793:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff880088e7d180 x1800988652938432/t21474836482(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:163/0 lens 496/456 e 0 to 0 dl 1717558723 ref 1 fl Interpret:/200/0 rc 0/0 job:'rmdir.0' uid:0 gid:0 [ 2052.893448] Lustre: Failing over lustre-MDT0000 [ 2053.174758] Lustre: server umount lustre-MDT0000 complete [ 2053.180517] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2054.072895] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2054.073836] LustreError: 8784:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558646 with bad export cookie 2307922713183099705 [ 2054.074081] Lustre: Failing over lustre-MDT0001 [ 2054.074153] LustreError: 7110:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558646 with bad export cookie 2307922713183099705 [ 2054.074163] LustreError: 9468:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558646 with bad export cookie 2307922713183099705 [ 2054.074191] LustreError: 7110:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558646 with bad export cookie 2307922713183099705 [ 2054.074227] LustreError: 8262:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558646 with bad export cookie 2307922713183099705 [ 2054.075536] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2054.075638] LustreError: 8262:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558646 with bad export cookie 2307922713183099789 [ 2054.075728] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2056.295761] LustreError: 3681:0:(/home/green/git/lustre-release/lustre/ptlrpc/client.c:1281:ptlrpc_import_delay_req()) @@@ IMP_CLOSED req@ffff8800a2000380 x1800988656266176/t0(0) o38->lustre-MDT0000-osp-MDT0001@0@lo:24/4 lens 520/544 e 0 to 0 dl 0 ref 1 fl Rpc:NQU/200/ffffffff rc 0/-1 job:'ptlrpcd_00_01.0' uid:0 gid:0 [ 2056.295763] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2056.295768] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2056.295804] Lustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2056.295891] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2056.316778] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2058.176843] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2058.176954] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2059.330811] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2071.927589] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2071.933997] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2074.304750] Lustre: server umount lustre-MDT0001 complete [ 2074.304920] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2074.304966] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2074.304993] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2078.208686] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2078.208695] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2079.208453] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2079.208456] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2079.305093] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2079.305105] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2079.305206] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2079.305217] Lustre: Evicted from MGS (at 192.168.201.148@tcp) after server handle changed from 0x0 to 0x2007637ad055a27f [ 2079.305277] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2079.385468] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2079.403375] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2079.462662] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2080.400716] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 2 clients reconnect [ 2080.450098] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2083.214252] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2084.508552] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2085.378896] Lustre: 26126:0:(/home/green/git/lustre-release/lustre/mdt/mdt_recovery.c:148:mdt_req_from_lrd()) @@@ restoring transno req@ffff8800a1595880 x1800988652938432/t21474836482(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:196/0 lens 496/2888 e 0 to 0 dl 1717558756 ref 1 fl Interpret:/202/0 rc 0/0 job:'rmdir.0' uid:0 gid:0 [ 2085.962678] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid,mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 2086.520489] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2090.636766] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2091.364757] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 2091.431794] Lustre: Failing over lustre-MDT0000 [ 2094.504070] Lustre: server umount lustre-MDT0000 complete [ 2094.504081] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2094.504117] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2094.504120] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2094.504407] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2094.504449] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2094.504474] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2094.557148] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2096.246394] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2096.255600] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2099.512061] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2099.512218] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2099.512389] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2099.512406] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2101.248244] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2101.248280] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2104.519893] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2104.519917] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2104.520000] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2104.520205] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2105.555907] LDISKFS-fs (dm-0): recovery complete [ 2105.559171] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2105.606407] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2106.256130] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2106.723212] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2111.593445] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2112.166610] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 2115.200913] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2115.508289] Lustre: DEBUG MARKER: == replay-dual test 23c: c1 rmdir d1, M0 drop update reply and fail M0, c2 mkdir d1 ========================================================== 23:38:28 (1717558708) [ 2117.540987] LustreError: 18635:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff88012c41e680 x1800988656292416/t137438953491(0) o1000->lustre-MDT0001-mdtlov_UUID@0@lo:158/0 lens 1488/4320 e 0 to 0 dl 1717558718 ref 1 fl Interpret:/200/0 rc 0/0 job:'osp_up0-1.0' uid:0 gid:0 [ 2117.606600] Lustre: Failing over lustre-MDT0000 [ 2120.712257] Lustre: server umount lustre-MDT0000 complete [ 2120.712291] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2120.712508] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2120.712704] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2120.712721] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2120.712883] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2120.713129] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2120.772271] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2121.284717] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2121.288453] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2125.719825] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2125.719884] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2125.719924] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2125.719946] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2126.287616] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2126.287631] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2130.476049] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2130.523990] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2131.295768] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2131.340383] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2131.507406] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2136.439144] Lustre: 26138:0:(/home/green/git/lustre-release/lustre/ptlrpc/client.c:2343:ptlrpc_expire_one_request()) @@@ Request sent has timed out for slow reply: [sent 1717558707/real 1717558707] req@ffff88012c41d180 x1800988656292416/t0(0) o1000->lustre-MDT0000-osp-MDT0001@0@lo:24/4 lens 1488/4320 e 0 to 1 dl 1717558723 ref 2 fl Rpc:XQr/200/ffffffff rc 0/-1 job:'osp [ 2136.859013] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 2140.836780] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2141.447834] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 2141.522209] Lustre: Failing over lustre-MDT0000 [ 2145.607805] Lustre: server umount lustre-MDT0000 complete [ 2145.607812] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2145.607847] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2145.607895] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2145.607965] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2145.607974] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2145.607986] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2145.631781] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2146.325702] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2146.333851] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2150.616061] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2150.616080] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2150.616202] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2150.616206] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2151.328784] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2151.328836] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2155.296996] LDISKFS-fs (dm-0): recovery complete [ 2155.298163] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2155.332501] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2156.311971] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2156.336069] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2161.101877] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2161.574755] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 2165.138809] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2168.019052] Lustre: DEBUG MARKER: == replay-dual test 23d: c1 rmdir d1, M0 drop update reply and fail M0/M1, c2 mkdir d1 ========================================================== 23:39:17 (1717558757) [ 2170.021160] LustreError: 10230:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff88008ade4700 x1800988656317696/t146028888081(0) o1000->lustre-MDT0001-mdtlov_UUID@0@lo:211/0 lens 1728/4320 e 0 to 0 dl 1717558771 ref 1 fl Interpret:/200/0 rc 0/0 job:'osp_up0-1.0' uid:0 gid:0 [ 2170.096762] Lustre: Failing over lustre-MDT0000 [ 2170.424115] Lustre: server umount lustre-MDT0000 complete [ 2170.424119] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2170.424296] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2170.440876] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2170.441060] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2170.451602] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2170.451698] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2170.460164] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2171.368301] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2171.368303] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2171.380995] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2171.382227] LustreError: 8784:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558763 with bad export cookie 2307922713183106880 [ 2171.382677] Lustre: Failing over lustre-MDT0001 [ 2171.382684] LustreError: 9468:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558763 with bad export cookie 2307922713183106880 [ 2171.382700] LustreError: 8262:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558763 with bad export cookie 2307922713183106880 [ 2171.382750] LustreError: 7110:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558763 with bad export cookie 2307922713183106880 [ 2171.382830] LustreError: 9468:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717558763 with bad export cookie 2307922713183106880 [ 2175.432044] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2175.432089] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2175.432137] Lustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2175.438288] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2176.368772] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2176.368880] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2176.433938] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2176.434023] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2177.371976] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2190.133980] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2190.152397] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2196.404566] Lustre: server umount lustre-MDT0001 complete [ 2196.433835] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2196.516990] LustreError: 3681:0:(/home/green/git/lustre-release/lustre/ptlrpc/client.c:1291:ptlrpc_import_delay_req()) @@@ invalidate in flight req@ffff88013998b800 x1800988656320768/t0(0) o250->MGC192.168.201.148@tcp@0@lo:26/25 lens 520/544 e 0 to 0 dl 0 ref 1 fl Rpc:NQU/200/ffffffff rc 0/-1 job:'kworker.0' uid:0 gid:0 [ 2196.531591] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2196.548815] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2196.622300] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2197.488692] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 2 clients reconnect [ 2197.521268] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2201.409783] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2201.674536] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2202.514979] Lustre: 2064:0:(/home/green/git/lustre-release/lustre/mdt/mdt_recovery.c:148:mdt_req_from_lrd()) @@@ restoring transno req@ffff88012b52df80 x1800988652967744/t25769803780(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:313/0 lens 496/2888 e 0 to 0 dl 1717558873 ref 1 fl Interpret:/202/0 rc 0/0 job:'rmdir.0' uid:0 gid:0 [ 2203.100453] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid,mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 2203.649007] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2207.698400] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2208.486874] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 2208.569721] Lustre: Failing over lustre-MDT0000 [ 2211.656135] Lustre: server umount lustre-MDT0000 complete [ 2211.656157] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2211.656261] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2211.656483] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2211.656526] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2211.687619] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2211.687949] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 2211.700308] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2211.707953] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2212.445179] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2212.445232] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2216.663876] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2216.664008] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2216.664032] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2216.664051] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2217.440476] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2217.440521] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2221.671661] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2221.671718] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2221.671725] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2221.671732] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2222.448241] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2222.448245] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2222.623631] LDISKFS-fs (dm-0): recovery complete [ 2222.626170] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2222.669372] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2223.908875] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2227.456583] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2228.679182] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2229.269483] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 2232.774726] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2233.190230] Lustre: DEBUG MARKER: == replay-dual test 24: reconstruct on non-existing object ========================================================== 23:40:25 (1717558825) [ 2318.213120] LustreError: 2062:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:3271:target_send_reply_msg()) @@@ dropping reply req@ffff8800987db480 x1800988652982592/t154618822673(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:345/0 lens 488/456 e 0 to 0 dl 1717558905 ref 1 fl Interpret:/200/0 rc 0/0 job:'truncate.0' uid:0 gid:0 [ 2318.230130] Lustre: lustre-MDT0000: Client 59afe7b9-24b1-4923-9376-c1a91598a39a (at 192.168.201.48@tcp) reconnecting [ 2320.297489] Lustre: 5623:0:(/home/green/git/lustre-release/lustre/mdt/mdt_recovery.c:148:mdt_req_from_lrd()) @@@ restoring transno req@ffff8800a5304a80 x1800988652982592/t154618822673(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:430/0 lens 488/3152 e 0 to 0 dl 1717558990 ref 1 fl Interpret:/202/0 rc 0/0 job:'truncate.0' uid:0 gid:0 [ 2322.428554] Lustre: DEBUG MARKER: == replay-dual test 25: replay|resend ==================== 23:41:52 (1717558912) [ 2322.457643] Lustre: Failing over lustre-OST0000 [ 2322.920389] Lustre: server umount lustre-OST0000 complete [ 2322.921467] Lustre: lustre-OST0000-osc-MDT0000: Connection to lustre-OST0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2322.921739] Lustre: lustre-OST0000-osc-MDT0001: Connection to lustre-OST0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2322.937889] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2323.239144] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2323.248514] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2327.928123] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2327.928132] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2328.240617] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2328.240626] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2332.936002] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2332.936019] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2333.248210] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2333.248464] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2335.300427] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2335.309025] LDISKFS-fs (dm-2): file extents enabled, maximum tree depth=5 [ 2335.315670] LDISKFS-fs (dm-2): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2336.959772] Lustre: lustre-OST0000: Will be in recovery for at least 1:00, or until 4 clients reconnect [ 2337.041975] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 allLustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) osc.lustre-OST0000-osc-[-0-9a-f]*.ost_server_uuid [ 2340.473646] Lustre: DEBUG MARKER: osc.lustre-OST0000-osc-[-0-9a-f]*.ost_server_uuid in FULL state after 0 secLustre: DEBUG MARKER: == replay-dual test 26: dbench and tar with mds failover ========================================================== 23:42:17 (1717558937) [ 2349.035871] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000Lustre: DEBUG MARKER: test_26 fail mds1 1 times [ 2352.251247] Lustre: Failing over lustre-MDT0000Lustre: server umount lustre-MDT0000 complete [ 2353.031802] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2353.044901] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server.LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server.[ 2353.280824] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2355.415995] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2355.425049] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2355.425179] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2355.431813] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2358.288280] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2358.288386] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2360.424076] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2360.424162] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2360.424182] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2360.424244] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2363.295802] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2363.295840] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2365.431704] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2365.431709] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2365.431744] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2365.431775] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2366.160873] LDISKFS-fs (dm-0): recovery complete [ 2366.163646] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2366.209436] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2367.374821] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2368.304054] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2376.222582] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2376.602311] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 2382.279318] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2384.856455] Lustre: DEBUG MARKER: mds2 REPLAY BARRIER on lustre-MDT0001 [ 2385.610682] Lustre: DEBUG MARKER: test_26 fail mds2 2 times [ 2385.696378] Lustre: Failing over lustre-MDT0001 [ 2386.295729] Lustre: server umount lustre-MDT0001 complete [ 2386.298011] LustreError: 11-0: lustre-MDT0001-osp-MDT0000: operation mds_statfs to node 0@lo failed: rc = -107 [ 2386.305110] Lustre: lustre-MDT0001-osp-MDT0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2386.311883] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2386.311888] Lustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2386.312132] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2386.312250] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2387.969409] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2388.347140] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2391.319795] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2391.319804] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2391.319819] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2393.345230] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2393.345413] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2396.327943] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2396.327966] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2396.327981] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2398.352445] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2398.352467] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2399.689408] LDISKFS-fs (dm-1): recovery complete [ 2399.691649] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2399.795708] mount.lustre (11324) used greatest stack depth: 9824 bytes left [ 2400.902905] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2401.548053] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2406.149568] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2406.530508] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 2412.150443] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2414.579642] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 2415.017722] Lustre: DEBUG MARKER: test_26 fail mds1 3 times [ 2415.080277] Lustre: Failing over lustre-MDT0000 [ 2416.384508] Lustre: server umount lustre-MDT0000 complete [ 2416.384603] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2419.800050] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2419.807166] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 2419.811998] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2419.816175] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2419.816238] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2419.816307] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2419.816382] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2419.816469] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2419.816521] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2421.392329] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2421.392488] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2424.824239] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2424.824269] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2424.824272] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2424.824429] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2426.400720] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2426.400807] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2429.202603] LDISKFS-fs (dm-0): recovery complete [ 2429.204235] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2429.230852] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2430.450324] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2431.408772] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2436.082561] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2436.596922] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 2442.576304] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2445.082459] Lustre: DEBUG MARKER: mds2 REPLAY BARRIER on lustre-MDT0001 [ 2445.658355] Lustre: DEBUG MARKER: test_26 fail mds2 4 times [ 2445.754962] Lustre: Failing over lustre-MDT0001 [ 2446.432011] Lustre: server umount lustre-MDT0001 complete [ 2446.442518] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2449.304315] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2449.315311] LustreError: 11-0: lustre-MDT0001-osp-MDT0000: operation mds_statfs to node 0@lo failed: rc = -107 [ 2449.320007] Lustre: lustre-MDT0001-osp-MDT0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2449.320235] Lustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2449.320494] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2449.320505] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2449.367088] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2451.440673] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2451.440724] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2454.376162] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2454.376237] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2454.382622] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2456.448154] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2456.448237] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2459.383914] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2459.383924] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2459.384139] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2459.983266] LDISKFS-fs (dm-1): recovery complete [ 2459.984877] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2461.248487] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2461.456225] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2466.142772] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2466.627089] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 2472.765465] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2475.299697] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 2475.790876] Lustre: DEBUG MARKER: test_26 fail mds1 5 times [ 2480.120154] Lustre: Failing over lustre-MDT0000 [ 2480.122899] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 2480.136057] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2480.136094] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2480.150223] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2481.308308] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2481.488117] Lustre: server umount lustre-MDT0000 complete [ 2481.488131] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2485.144219] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2485.144478] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2485.144699] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2485.144946] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2486.496431] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2486.496450] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2490.151714] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2490.151716] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2490.151753] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2490.151820] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2491.504428] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2491.504491] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2495.159841] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2495.159900] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2495.160020] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2495.160170] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2495.621658] LDISKFS-fs (dm-0): recovery complete [ 2495.622839] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2495.657990] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2496.512603] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2496.849122] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2503.680032] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2504.290039] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 2510.507725] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2513.063735] Lustre: DEBUG MARKER: mds2 REPLAY BARRIER on lustre-MDT0001 [ 2513.679618] Lustre: DEBUG MARKER: test_26 fail mds2 6 times [ 2513.749368] Lustre: Failing over lustre-MDT0001 [ 2515.751909] Lustre: server umount lustre-MDT0001 complete [ 2515.755113] LustreError: 11-0: lustre-MDT0001-osp-MDT0000: operation mds_statfs to node 0@lo failed: rc = -107 [ 2515.762013] Lustre: lustre-MDT0001-osp-MDT0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2515.768117] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2515.768178] Lustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2515.768464] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2515.768491] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2516.544064] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2516.555223] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2520.775811] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2520.775849] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2520.776023] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2521.551948] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2521.552004] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2525.784221] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2525.784267] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2525.784302] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2526.559866] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2526.559910] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2527.866327] LDISKFS-fs (dm-1): recovery complete [ 2527.870432] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2529.036987] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2529.518480] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2533.955987] tgt_recover_1 (19599) used greatest stack depth: 9608 bytes left [ 2534.861705] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2535.341924] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 2540.866578] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2543.490731] Lustre: DEBUG MARKER: mds1 REPLAY BARRIER on lustre-MDT0000 [ 2544.145050] Lustre: DEBUG MARKER: test_26 fail mds1 7 times [ 2547.975984] Lustre: Failing over lustre-MDT0000 [ 2547.978252] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 2547.992119] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2547.999797] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2548.012228] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2549.332275] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2549.600254] Lustre: server umount lustre-MDT0000 complete [ 2549.600287] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2553.000079] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2553.000103] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2553.000181] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2553.000225] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2554.608011] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2554.608117] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2558.008020] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2558.008078] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2558.008147] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2558.008297] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2559.616815] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2559.616882] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2563.016032] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2563.016045] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2563.016057] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2563.016098] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2563.570321] LDISKFS-fs (dm-0): recovery complete [ 2563.571591] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2563.599874] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2564.624577] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2564.783619] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2570.165854] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2570.754633] Lustre: 5623:0:(/home/green/git/lustre-release/lustre/mdt/mdt_recovery.c:148:mdt_req_from_lrd()) @@@ restoring transno req@ffff88008ade4380 x1800988661747968/t167503733792(0) o36->59afe7b9-24b1-4923-9376-c1a91598a39a@192.168.201.48@tcp:682/0 lens 496/2888 e 0 to 0 dl 1717559242 ref 1 fl Interpret:/202/0 rc 0/0 job:'rm.0' uid:0 gid:0 [ 2571.172258] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 2594.017108] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2597.401620] Lustre: DEBUG MARKER: == replay-dual test 28: lock replay should be ordered: waiting after granted ========================================================== 23:46:26 (1717559186) [ 2597.410900] Lustre: Failing over lustre-OST0000 [ 2597.413174] LustreError: 11-0: lustre-OST0000-osc-MDT0001: operation ost_destroy to node 0@lo failed: rc = -19 [ 2597.413181] LustreError: 11-0: lustre-OST0000-osc-MDT0001: operation ost_destroy to node 0@lo failed: rc = -19 [ 2597.413274] Lustre: lustre-OST0000-osc-MDT0001: Connection to lustre-OST0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2597.413293] LustreError: 11-0: lustre-OST0000-osc-MDT0001: operation ost_destroy to node 0@lo failed: rc = -19 [ 2597.413309] LustreError: 11-0: lustre-OST0000-osc-MDT0001: operation ost_destroy to node 0@lo failed: rc = -19 [ 2597.440595] LustreError: 11-0: lustre-OST0000-osc-MDT0001: operation ost_destroy to node 0@lo failed: rc = -19 [ 2597.445609] LustreError: 11-0: lustre-OST0000-osc-MDT0001: operation ost_destroy to node 0@lo failed: rc = -19 [ 2597.450734] LustreError: 11-0: lustre-OST0000-osc-MDT0001: operation ost_destroy to node 0@lo failed: rc = -19 [ 2598.714779] LustreError: 11-0: lustre-OST0000-osc-MDT0001: operation ost_destroy to node 0@lo failed: rc = -19 [ 2598.715056] LustreError: 11-0: lustre-OST0000-osc-MDT0000: operation ost_destroy to node 0@lo failed: rc = -107 [ 2598.715063] LustreError: 11-0: lustre-OST0000-osc-MDT0000: operation ost_destroy to node 0@lo failed: rc = -107 [ 2598.715128] Lustre: lustre-OST0000-osc-MDT0000: Connection to lustre-OST0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2598.715145] LustreError: 11-0: lustre-OST0000-osc-MDT0000: operation ost_destroy to node 0@lo failed: rc = -107 [ 2598.715162] LustreError: 11-0: lustre-OST0000-osc-MDT0000: operation ost_destroy to node 0@lo failed: rc = -107 [ 2598.747741] LustreError: 11-0: lustre-OST0000-osc-MDT0000: operation ost_destroy to node 0@lo failed: rc = -107 [ 2598.752378] LustreError: 11-0: lustre-OST0000-osc-MDT0000: operation ost_destroy to node 0@lo failed: rc = -107 [ 2598.757310] LustreError: 11-0: lustre-OST0000-osc-MDT0000: operation ost_destroy to node 0@lo failed: rc = -107 [ 2603.462684] LustreError: 11-0: lustre-OST0000-osc-MDT0000: operation ost_destroy to node 0@lo failed: rc = -107 [ 2603.735758] Lustre: server umount lustre-OST0000 complete [ 2603.735760] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2604.688691] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2604.688719] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2608.744164] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2608.744191] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2609.696644] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2609.696698] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2613.752504] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2613.752523] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2614.704310] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2614.704319] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2616.181593] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2616.188410] LDISKFS-fs (dm-2): file extents enabled, maximum tree depth=5 [ 2616.193601] LDISKFS-fs (dm-2): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2617.672295] Lustre: lustre-OST0000: Will be in recovery for at least 1:00, or until 4 clients reconnect [ 2617.914065] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 allLustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) osc.lustre-OST0000-osc-[-0-9a-f]*.ost_server_uuid [ 2621.194553] Lustre: DEBUG MARKER: osc.lustre-OST0000-osc-[-0-9a-f]*.ost_server_uuid in FULL state after 0 secLustre: DEBUG MARKER: == replay-dual test 29: replay vs update with the same xid ========================================================== 23:46:59 (1717559219) [ 2627.084614] Lustre: DEBUG MARKER: SKIP: replay-dual test_29 needs >= 2 clientsLustre: DEBUG MARKER: == replay-dual test 30: layout lock replay is not blocked on IO ========================================================== 23:47:00 (1717559220) [ 2629.437822] Lustre: Failing over lustre-MDT0000Lustre: server umount lustre-MDT0000 complete [ 2629.739050] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server.LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2630.264042] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2630.291230] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server.LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server.[ 2631.288578] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server.LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server.LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server.LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2636.263444] Lustre: ll_ost00_008: service thread pid 26431 was inactive for 40.027 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes: [ 2636.263451] Lustre: ll_ost00_012: service thread pid 8416 was inactive for 40.028 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes: [ 2636.263452] Pid: 8416, comm: ll_ost00_012 3.10.0-7.9-debug #1 SMP Sat Mar 26 23:28:42 EDT 2022 [ 2636.263453] Call Trace: [ 2636.263598] [<0>] ldlm_completion_ast+0x6b3/0x990 [ptlrpc] [ 2636.263660] [<0>] ldlm_cli_enqueue_local+0x23d/0x5e0 [ptlrpc] [ 2636.263677] [<0>] ofd_destroy_by_fid+0x18a/0x3a0 [ofd] [ 2636.263686] [<0>] ofd_destroy_hdl+0x1be/0x870 [ofd] [ 2636.263780] [<0>] tgt_request_handle+0x43e/0xfa0 [ptlrpc] [ 2636.263848] [<0>] ptlrpc_server_handle_request+0x26a/0xad0 [ptlrpc] [ 2636.263940] [<0>] ptlrpc_main+0x879/0x1020 [ptlrpc] [ 2636.263958] [<0>] kthread+0xe4/0xf0 [ 2636.263965] [<0>] ret_from_fork_nospec_begin+0x7/0x21 [ 2636.264005] [<0>] 0xfffffffffffffffe [ 2636.264011] Lustre: ll_ost00_019: service thread pid 16037 was inactive for 40.027 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes: [ 2636.264011] Pid: 16037, comm: ll_ost00_019 3.10.0-7.9-debug #1 SMP Sat Mar 26 23:28:42 EDT 2022 [ 2636.264012] Call Trace: [ 2636.264164] [<0>] ldlm_completion_ast+0x6b3/0x990 [ptlrpc] [ 2636.264224] [<0>] ldlm_cli_enqueue_local+0x23d/0x5e0 [ptlrpc] [ 2636.264240] [<0>] ofd_destroy_by_fid+0x18a/0x3a0 [ofd] [ 2636.264246] [<0>] ofd_destroy_hdl+0x1be/0x870 [ofd] [ 2636.264318] [<0>] tgt_request_handle+0x43e/0xfa0 [ptlrpc] [ 2636.264375] [<0>] ptlrpc_server_handle_request+0x26a/0xad0 [ptlrpc] [ 2636.264459] [<0>] ptlrpc_main+0x879/0x1020 [ptlrpc] [ 2636.264472] [<0>] kthread+0xe4/0xf0 [ 2636.264480] [<0>] ret_from_fork_nospec_begin+0x7/0x21 [ 2636.264498] [<0>] 0xfffffffffffffffe [ 2636.296320] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2636.296422] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2636.296567] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2636.354916] Pid: 26431, comm: ll_ost00_008 3.10.0-7.9-debug #1 SMP Sat Mar 26 23:28:42 EDT 2022 [ 2636.356767] Call Trace: [ 2636.357446] [<0>] ldlm_completion_ast+0x6b3/0x990 [ptlrpc] [ 2636.359780] [<0>] ldlm_cli_enqueue_local+0x23d/0x5e0 [ptlrpc] [ 2636.361480] [<0>] ofd_destroy_by_fid+0x18a/0x3a0 [ofd] [ 2636.362953] [<0>] ofd_destroy_hdl+0x1be/0x870 [ofd] [ 2636.364453] [<0>] tgt_request_handle+0x43e/0xfa0 [ptlrpc] [ 2636.365971] [<0>] ptlrpc_server_handle_request+0x26a/0xad0 [ptlrpc] [ 2636.367746] [<0>] ptlrpc_main+0x879/0x1020 [ptlrpc] [ 2636.369150] [<0>] kthread+0xe4/0xf0 [ 2636.370280] [<0>] ret_from_fork_nospec_begin+0x7/0x21 [ 2636.371774] [<0>] 0xfffffffffffffffe [ 2636.372907] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2636.377128] Lustre: ll_ost00_013: service thread pid 8417 was inactive for 40.137 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one. [ 2636.381083] Lustre: ll_ost00_017: service thread pid 10484 was inactive for 40.141 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one. [ 2636.385021] Lustre: ll_ost00_003: service thread pid 10275 was inactive for 40.145 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one. [ 2636.389083] Lustre: ll_ost00_010: service thread pid 8236 was inactive for 40.149 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one. [ 2639.744485] Lustre: ll_ost00_016: service thread pid 9806 was inactive for 40.153 seconds. Watchdog stack traces are limited to 3 per 300 seconds, skipping this one. [ 2639.744589] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2641.304127] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2641.304177] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2641.304220] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2641.304533] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2642.451037] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2642.502083] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2643.692531] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2644.752627] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2649.705292] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2650.297564] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 2653.760805] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2654.729706] Lustre: DEBUG MARKER: == replay-dual test 31: deadlock on file_remove_privs and occupied mod rpc slots ========================================================== 23:47:26 (1717559246) [ 2654.759127] Lustre: Failing over lustre-OST0000 [ 2654.778192] Lustre: server umount lustre-OST0000 complete [ 2655.936864] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2655.946168] LustreError: 11-0: lustre-OST0000-osc-MDT0000: operation ost_create to node 0@lo failed: rc = -107 [ 2655.952518] Lustre: lustre-OST0000-osc-MDT0000: Connection to lustre-OST0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2657.592182] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2657.597615] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2657.597908] Lustre: lustre-OST0000-osc-MDT0001: Connection to lustre-OST0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2659.776560] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2662.600125] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2662.600175] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2664.784458] LustreError: 137-5: lustre-OST0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2667.503943] LustreError: 137-5: lustre-OST0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2667.512631] LDISKFS-fs (dm-2): file extents enabled, maximum tree depth=5 [ 2667.518557] LDISKFS-fs (dm-2): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2669.211652] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2669.237296] Lustre: lustre-OST0000: Will be in recovery for at least 1:00, or until 3 clients reconnectLustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) osc.lustre-OST0000-osc-[-0-9a-f]*.ost_server_uuid [ 2672.619682] Lustre: DEBUG MARKER: osc.lustre-OST0000-osc-[-0-9a-f]*.ost_server_uuid in IDLELustre: DEBUG MARKER: == replay-dual test 32: gap in update llog shouldn't break recovery ========================================================== 23:47:49 (1717559269) [ 2677.895825] Lustre: Failing over lustre-MDT0001Lustre: server umount lustre-MDT0001 complete [ 2679.379676] Lustre: Failing over lustre-MDT0000Lustre: server umount lustre-MDT0000 complete[ 2682.274034] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2682.319292] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will failLustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server.[ 2682.465550] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to completeLustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server.LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server.Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 allLustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 2 clients reconnect [ 2684.855802] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server.[ 2686.380804] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2686.514627] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2687.365869] LustreError: 29566:0:(/home/green/git/lustre-release/lustre/obdclass/llog.c:711:llog_process_thread()) lustre-MDT0000-osp-MDT0001: [0x2000134b1:0x2:0x0] rec type=106a0000 idx=366 len=1256, gap in index, expected 365 [ 2687.582577] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2693.784127] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2696.631769] Lustre: DEBUG MARKER: == replay-dual test 33: Check for OBD_INCOMPAT_MULTI_RPCS in last_rcvd after abort_recovery ========================================================== 23:48:06 (1717559286) [ 2696.718523] Lustre: Failing over lustre-MDT0001 [ 2697.527778] Lustre: server umount lustre-MDT0001 complete [ 2697.527974] Lustre: lustre-MDT0001-osp-MDT0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2697.527992] Lustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2697.528113] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2697.528122] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2697.546385] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2697.846651] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2699.844604] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2702.536095] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2702.536114] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2702.536128] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2704.848533] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2707.544164] LustreError: 137-5: lustre-MDT0001: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2707.544250] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2707.544437] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2709.782064] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2709.903875] LustreError: 137-5: lustre-MDT0001: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2710.980061] LustreError: 31086:0:(/home/green/git/lustre-release/lustre/obdclass/llog.c:711:llog_process_thread()) lustre-MDT0000-osp-MDT0001: [0x2000134b1:0x2:0x0] rec type=106a0000 idx=366 len=1256, gap in index, expected 365 [ 2711.024516] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 3 clients reconnect [ 2712.608568] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2713.204487] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount REPLAY_WAIT mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 2713.498894] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in REPLAY_WAIT state after 0 sec [ 2713.504203] Lustre: lustre-MDT0001: Aborting client recovery [ 2713.507271] LustreError: 31647:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2927:target_stop_recovery_thread()) lustre-MDT0001: Aborting recovery [ 2713.515188] Lustre: 31087:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2310:target_recovery_overseer()) recovery is aborted, evict exports in recovery [ 2713.522794] Lustre: 31087:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-MDT0001: disconnect stale client e5216cbf-f424-415e-9b55-fb0a458e8297@ [ 2713.531826] Lustre: 31087:0:(/home/green/git/lustre-release/lustre/obdclass/genops.c:1533:class_disconnect_stale_exports()) lustre-MDT0001: disconnect stale client lustre-MDT0000-mdtlov_UUID@ [ 2713.544289] Lustre: lustre-MDT0001: disconnecting 2 stale clients [ 2713.548667] Lustre: 31087:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2310:target_recovery_overseer()) recovery is aborted, evict exports in recovery [ 2714.420175] Lustre: 31087:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lib.c:2310:target_recovery_overseer()) recovery is aborted, evict exports in recovery [ 2714.944669] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount FULL mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 2715.768371] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2721.412605] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing _wait_recovery_complete *.lustre-MDT0001.recovery_status 1475 [ 2721.504037] Lustre: Failing over lustre-MDT0001 [ 2724.604146] LDISKFS-fs (dm-1): mounted filesystem with ordered data mode. Opts: user_xattr,acl,no_mbcache,nodelalloc [ 2724.702868] Lustre: server umount lustre-MDT0001 complete [ 2724.702884] Lustre: lustre-MDT0001-lwp-OST0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2724.702914] Lustre: lustre-OST0001: haven't heard from client e5216cbf-f424-415e-9b55-fb0a458e8297 (at 192.168.201.48@tcp) in 31 seconds. I think it's dead, and I am evicting it. exp ffff8800a501e000, cur 1717559316 expire 1717559286 last 1717559285 [ 2724.702964] Lustre: lustre-MDT0001-osp-MDT0000: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2724.703278] Lustre: lustre-MDT0000: haven't heard from client e5216cbf-f424-415e-9b55-fb0a458e8297 (at 192.168.201.48@tcp) in 31 seconds. I think it's dead, and I am evicting it. exp ffff88012e8f2000, cur 1717559316 expire 1717559286 last 1717559285 [ 2724.703293] Lustre: 16037:0:(/home/green/git/lustre-release/lustre/ptlrpc/service.c:2359:ptlrpc_server_handle_request()) @@@ Request took longer than estimated (111/17s); client may timeout req@ffff88009fa5ce00 x1800988658858304/t4294977669(0) o6->lustre-MDT0001-mdtlov_UUID@0@lo:739/0 lens 544/432 e 4 to 0 dl 1717559299 ref 1 fl Complete:/200/0 rc 0/0 job:'osp-syn-1-1.0' u [ 2724.703312] Lustre: ll_ost00_019: service thread pid 16037 completed after 128.467s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources). [ 2724.703362] Lustre: 9806:0:(/home/green/git/lustre-release/lustre/ptlrpc/service.c:2359:ptlrpc_server_handle_request()) @@@ Request took longer than estimated (111/17s); client may timeout req@ffff880088d62680 x1800988658857920/t4294977670(0) o6->lustre-MDT0001-mdtlov_UUID@0@lo:739/0 lens 544/432 e 4 to 0 dl 1717559299 ref 1 fl Complete:/200/0 rc 0/0 job:'osp-syn-1-1.0' u [ 2724.705033] Lustre: ll_ost00_016: service thread pid 9806 completed after 128.468s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources). [ 2724.887247] Lustre: lustre-MDT0001-lwp-OST0001: Connection to lustre-MDT0001 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2725.828540] Lustre: lustre-MDT0001: Will be in recovery for at least 1:00, or until 2 clients reconnect [ 2726.479610] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug -1 all [ 2727.083276] Lustre: lustre-MDT0001: Denying connection for new client 087f70f1-413c-43dc-8e8a-c76be3895b95 (at 192.168.201.48@tcp), waiting for 2 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 2:18 [ 2729.488725] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount FULL mdc.lustre-MDT0001-mdc-*.mds_server_uuid [ 2730.705443] Lustre: lustre-MDT0001: Denying connection for new client 087f70f1-413c-43dc-8e8a-c76be3895b95 (at 192.168.201.48@tcp), waiting for 2 known clients (1 recovered, 0 in progress, and 0 evicted) to recover in 2:15 [ 2731.509097] Lustre: DEBUG MARKER: mdc.lustre-MDT0001-mdc-*.mds_server_uuid in DISCONN [ 2734.286765] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing _wait_recovery_complete *.lustre-MDT0001.recovery_status 1475 [ 2736.363841] Lustre: DEBUG MARKER: == replay-dual test complete, duration 2637 sec ========== 23:48:46 (1717559326) [ 2736.434054] Lustre: Failing over lustre-MDT0000 [ 2739.509074] Lustre: server umount lustre-MDT0000 complete [ 2739.736360] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2739.744388] LustreError: 11-0: lustre-MDT0000-osp-MDT0001: operation mds_statfs to node 0@lo failed: rc = -107 [ 2739.749481] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2739.783983] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2739.784020] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2739.784066] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2739.784196] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2739.784275] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2739.811760] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2744.512711] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2744.792106] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2744.792110] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2744.792120] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2744.792132] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2749.520246] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2749.799767] LustreError: 137-5: lustre-MDT0000: not available for connect from 192.168.201.48@tcp (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2749.799801] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2749.799811] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2749.799901] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2752.177757] LDISKFS-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc [ 2752.225517] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2753.453998] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2754.528537] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing set_default_debug vfstrace rpctrace dlmtrace neterror ha config ioctl super lfsck all [ 2758.120220] Lustre: lustre-MDT0000: Will be in recovery for at least 1:00, or until 2 clients reconnect [ 2758.699529] Lustre: DEBUG MARKER: oleg148-client.virtnet: executing wait_import_state_mount (FULL|IDLE) mdc.lustre-MDT0000-mdc-*.mds_server_uuid [ 2760.187421] Lustre: DEBUG MARKER: mdc.lustre-MDT0000-mdc-*.mds_server_uuid in FULL state after 0 sec [ 2760.187454] Lustre: 10484:0:(/home/green/git/lustre-release/lustre/ptlrpc/service.c:2359:ptlrpc_server_handle_request()) @@@ Request took longer than estimated (111/53s); client may timeout req@ffff88009fa5dc00 x1800988658857984/t4294977704(0) o6->lustre-MDT0001-mdtlov_UUID@0@lo:739/0 lens 544/432 e 4 to 0 dl 1717559299 ref 1 fl Complete:/200/0 rc 0/0 job:'osp-syn-1-1.0' u [ 2760.187474] Lustre: 8417:0:(/home/green/git/lustre-release/lustre/ptlrpc/service.c:2359:ptlrpc_server_handle_request()) @@@ Request took longer than estimated (111/53s); client may timeout req@ffff88009fa5ed80 x1800988658858240/t4294977705(0) o6->lustre-MDT0001-mdtlov_UUID@0@lo:739/0 lens 544/432 e 4 to 0 dl 1717559299 ref 1 fl Complete:/200/0 rc 0/0 job:'osp-syn-1-1.0' u [ 2760.187671] Lustre: ll_ost00_013: service thread pid 8417 completed after 163.951s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources). [ 2760.187693] Lustre: 26431:0:(/home/green/git/lustre-release/lustre/ptlrpc/service.c:2359:ptlrpc_server_handle_request()) @@@ Request took longer than estimated (111/53s); client may timeout req@ffff88009fa5f800 x1800988658858048/t4294977706(0) o6->lustre-MDT0001-mdtlov_UUID@0@lo:739/0 lens 544/432 e 4 to 0 dl 1717559299 ref 1 fl Complete:/200/0 rc 0/0 job:'osp-syn-1-1.0' u [ 2760.187844] Lustre: ll_ost00_008: service thread pid 26431 completed after 163.951s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources). [ 2760.187872] Lustre: 8416:0:(/home/green/git/lustre-release/lustre/ptlrpc/service.c:2359:ptlrpc_server_handle_request()) @@@ Request took longer than estimated (111/53s); client may timeout req@ffff880088d60a80 x1800988658858176/t4294977707(0) o6->lustre-MDT0001-mdtlov_UUID@0@lo:739/0 lens 544/432 e 4 to 0 dl 1717559299 ref 1 fl Complete:/200/0 rc 0/0 job:'osp-syn-1-1.0' u [ 2760.187984] Lustre: ll_ost00_012: service thread pid 8416 completed after 163.952s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources). [ 2760.188004] Lustre: 10275:0:(/home/green/git/lustre-release/lustre/ptlrpc/service.c:2359:ptlrpc_server_handle_request()) @@@ Request took longer than estimated (111/53s); client may timeout req@ffff88008bad2680 x1800988658858112/t4294977708(0) o6->lustre-MDT0001-mdtlov_UUID@0@lo:739/0 lens 544/432 e 4 to 0 dl 1717559299 ref 1 fl Complete:/200/0 rc 0/0 job:'osp-syn-1-1.0' u [ 2760.188956] Lustre: ll_ost00_003: service thread pid 10275 completed after 163.952s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources). [ 2760.189111] Lustre: 8236:0:(/home/green/git/lustre-release/lustre/ptlrpc/service.c:2359:ptlrpc_server_handle_request()) @@@ Request took longer than estimated (111/53s); client may timeout req@ffff88008bad3800 x1800988658857856/t4294977709(0) o6->lustre-MDT0001-mdtlov_UUID@0@lo:739/0 lens 544/432 e 4 to 0 dl 1717559299 ref 1 fl Complete:/200/0 rc 0/0 job:'osp-syn-1-1.0' u [ 2760.289766] Lustre: ll_ost00_010: service thread pid 8236 completed after 163.953s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources). [ 2762.328010] Lustre: ll_ost00_017: service thread pid 10484 completed after 164.053s. This likely indicates the system was overloaded (too many service threads, or not enough hardware resources). [ 2762.328020] Lustre: lustre-MDT0000-osp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2762.328220] Lustre: lustre-MDT0000-lwp-MDT0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2762.349083] Lustre: lustre-MDT0000-lwp-OST0000: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2767.005640] Lustre: lustre-MDT0000-lwp-OST0001: Connection to lustre-MDT0000 (at 0@lo) was lost; in progress operations using this service will wait for recovery to complete [ 2767.336075] Lustre: server umount lustre-MDT0000 complete [ 2767.336085] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2767.336090] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2767.336112] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2770.097272] LustreError: 137-5: lustre-MDT0000: not available for connect from 0@lo (no target). If you are running an HA pair check that the target is mounted on the other server. [ 2770.098763] LustreError: 7109:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717559362 with bad export cookie 2307922713184600694 [ 2770.098818] LustreError: 8262:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717559362 with bad export cookie 2307922713184600694 [ 2770.098830] LustreError: 8262:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717559362 with bad export cookie 2307922713184600694 [ 2770.098844] LustreError: 7108:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717559362 with bad export cookie 2307922713184600694 [ 2770.098864] LustreError: 8784:0:(/home/green/git/lustre-release/lustre/ptlrpc/../../lustre/ldlm/ldlm_lockd.c:2593:ldlm_cancel_handler()) ldlm_cancel from 0@lo arrived at 1717559362 with bad export cookie 2307922713184600694 [ 2770.262079] LustreError: 166-1: MGC192.168.201.148@tcp: Connection to MGS (at 0@lo) was lost; in progress operations using this service will fail [ 2838.345984] Lustre: server umount lustre-MDT0001 complete [ 2906.452320] Lustre: server umount lustre-OST0000 complete [ 2908.782241] device-mapper: core: cleaned up [ 2911.982637] Lustre: server umount lustre-OST0001 complete [ 2912.744172] Key type lgssc unregistered [ 2912.833830] Lustre: DEBUG MARKER: oleg148-server.virtnet: executing unload_modules_local