search for: 8d16

Displaying 6 results from an estimated 6 matches for "8d16".

Did you mean: 816
2014 Jul 10
0
PJSIP Transfer not working
...cline v: SIP/2.0/UDP 1.1.1.1:49260;rport;received=1.1.1.1;branch=z9hG4bK-d8754z-22994e127365d474-1---d8754z- i: MmFjNDM4NDc2NmFhZWNiYTU2MDQ1YmNjNGVmYmMyOTY f: "9544447408" <sip:9544447408 at 8.26.191.189>;tag=82c82c1d t: <sip:17274428141 at 8.26.191.189>;tag=09f3a67a-f457-46d1-8d16-243478ac3859 CSeq: 1 INVITE Reason: Q.850;cause=0 l: 0
2017 Oct 30
3
[locking/paravirt] static_key_disable_cpuslocked(): static key 'virt_spin_lock_key+0x0/0x20' used before call to jump_label_init()
...ci 0000:00:16.1: PME# supported from D0 D3hot D3cold [ 7.298241] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320 [ 7.305034] pci 0000:00:1a.0: reg 0x10: [mem 0x91d02000-0x91d023ff] [ 7.312118] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold [ 7.319218] pci 0000:00:1c.0: [8086:8d16] type 01 class 0x060400 [ 7.326107] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 7.333239] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320 [ 7.340002] pci 0000:00:1d.0: reg 0x10: [mem 0x91d01000-0x91d013ff] [ 7.347119] pci 0000:00:1d.0: PME# supported from D0 D3hot D3col...
2017 Oct 30
3
[locking/paravirt] static_key_disable_cpuslocked(): static key 'virt_spin_lock_key+0x0/0x20' used before call to jump_label_init()
...ci 0000:00:16.1: PME# supported from D0 D3hot D3cold [ 7.298241] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320 [ 7.305034] pci 0000:00:1a.0: reg 0x10: [mem 0x91d02000-0x91d023ff] [ 7.312118] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold [ 7.319218] pci 0000:00:1c.0: [8086:8d16] type 01 class 0x060400 [ 7.326107] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 7.333239] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320 [ 7.340002] pci 0000:00:1d.0: reg 0x10: [mem 0x91d01000-0x91d013ff] [ 7.347119] pci 0000:00:1d.0: PME# supported from D0 D3hot D3col...
2017 Oct 26
0
not healing one file
Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health
2017 Oct 26
3
not healing one file
On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next
2017 Oct 26
2
not healing one file
...76DB8DD7AB (53454058-7740-41e7-aeac-a40eb8b74cc5) on home-client-2 [2017-10-25 10:13:58.860152] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/CBEB61E03D48E58FECB97A80E2AB57D5A3121873 (40ddedce-721f-4b76-8d16-336ec2b305df) on home-client-2 [2017-10-25 10:13:58.871382] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/722CABC5F88A1D87E3326F38B07B0F41FE90C49F (5d9f7619-03fe-47f4-8cdb-b0d400db7ce6) on home-client-2...