search for: xfsaild

...as /dev/sdb (total 572GB) (RAID-5) Stock Centos 6.4 x64, everything updated. Kernel : 2.6.32-358.2.1.el6.x86_64 #1 SMP My Load always shows : top - 10:30:21 up 23:09, 1 users, load average: 0.99, 0.96, 0.79 yet there is no services what-so-ever doing anything. Using PowerTOP I can see that xfsaild is causing second most wake-ups (after kernel core : hrtimer_start (tick_sched_timer) ) < Detailed C-state information is not P-states (frequencies) 3.00 Ghz 100.0% 1500 Mhz 0.0%...

...w kernel it locks up within 1-12 hours of boot, with errors in /var/log/messages that start with things like kernel: arcmsr0: abort device command of scsi id = 0 lun = 0 (that is indeed the RAID scsi device) and within a few minutes of those also things like Oct 19 23:06:57 radon kernel: INFO: task xfsaild/dm-9:913 blocked for more than 120 seconds. Oct 19 23:06:57 radon kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 19 23:06:57 radon kernel: xfsaild/dm-9 D ffff88103eaa2000 0 913 2 0x00000080 Oct 19 23:06:57 radon kernel: ffff881033f67...

CentOS 7.4 client mounting a CentOS 7.4 server filesystem over nfs4. nfs seems to be much slower since the upgrade to 7.4, so I thought it might be nice to mount the directory as v4.0 rather than the new default of v4.1 to see if it makes a difference. The release notes state, without an example: "You can retain the original behavior by specifying 0 as the minor version" nfs(5)

...it was missed, here are the dmesg errors being thrown by gluster (as far as I can tell). They definately started after I upgraded from gluster 3.8 to 3.12: [ 6604.536156] perf: interrupt took too long (9593 > 9565), lowering kernel.perf_event_max_sample_rate to 20000 [ 8280.188734] INFO: task xfsaild/dm-10:1061 blocked for more than 120 seconds. [ 8280.188787] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 8280.188837] xfsaild/dm-10 D ffff93203a2eeeb0 0 1061 2 0x00000000 [ 8280.188843] Call Trace: [ 8280.188857] [<ffffffff960a3a2e>] ?...

...dmesg errors being thrown by gluster > (as far as I can tell). They definately started after I upgraded from > gluster 3.8 to 3.12: > > [ 6604.536156] perf: interrupt took too long (9593 > 9565), lowering > kernel.perf_event_max_sample_rate to 20000 > [ 8280.188734] INFO: task xfsaild/dm-10:1061 blocked for more than 120 > seconds. > [ 8280.188787] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" > disables this message. > [ 8280.188837] xfsaild/dm-10 D ffff93203a2eeeb0 0 1061 2 > 0x00000000 > [ 8280.188843] Call Trace: > [ 8280.18...

...in 1-12 hours of boot, with errors in > /var/log/messages that start with things like > kernel: arcmsr0: abort device command of scsi id = 0 lun = 0 > (that is indeed the RAID scsi device) and within a few minutes of those also > things like > Oct 19 23:06:57 radon kernel: INFO: task xfsaild/dm-9:913 blocked for more > than 120 seconds. You mention you have hardware problems, what are they? A write is blocked for longer than they host is willing to wait. There are a few sysctl parameters that affect this but I'd be more willing to suggest its related to your hardware problems....

...n by gluster >> (as far as I can tell). They definately started after I upgraded from >> gluster 3.8 to 3.12: >> >> [ 6604.536156] perf: interrupt took too long (9593 > 9565), lowering >> kernel.perf_event_max_sample_rate to 20000 >> [ 8280.188734] INFO: task xfsaild/dm-10:1061 blocked for more than 120 >> seconds. >> [ 8280.188787] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" >> disables this message. >> [ 8280.188837] xfsaild/dm-10 D ffff93203a2eeeb0 0 1061 2 >> 0x00000000 >> [ 8280.188843] Ca...

...b992076f>] ? system_call_after_swapgs+0xbc/ >>> 0x160 >>> [11159.499234] [<ffffffffb992082f>] system_call_fastpath+0x1c/0x21 >>> [11159.499238] [<ffffffffb992077b>] ? system_call_after_swapgs+0xc8/ >>> 0x160 >>> [11279.488720] INFO: task xfsaild/dm-10:1134 blocked for more than 120 >>> seconds. >>> [11279.490197] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" >>> disables this message. >>> [11279.491665] xfsaild/dm-10 D ffff9720a8660fd0 0 1134 2 >>> 0x00000000 >&g...

...86536k buffers > Swap: 2047992k total, 18884k used, 2029108k free, 246504k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 863 root 20 0 0 0 0 D 0.3 0.0 26:05.07 xfsaild/dm-5 1 root 20 0 21452 1032 780 S 0.0 0.1 0:01.76 init 2 root 20 0 0 0 0 S 0.0 0.0 0:00.53 kthreadd...

...write64+0x92/0xc0 > [11159.499230] [<ffffffffb992076f>] ? system_call_after_swapgs+0xbc/0x160 > [11159.499234] [<ffffffffb992082f>] system_call_fastpath+0x1c/0x21 > [11159.499238] [<ffffffffb992077b>] ? system_call_after_swapgs+0xc8/0x160 > [11279.488720] INFO: task xfsaild/dm-10:1134 blocked for more than 120 > seconds. > [11279.490197] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" > disables this message. > [11279.491665] xfsaild/dm-10 D ffff9720a8660fd0 0 1134 2 > 0x00000000 > [11279.491671] Call Trace: > [11279.49...

...+0xbc/ >>>>> 0x160 >>>>> [11159.499234] [<ffffffffb992082f>] system_call_fastpath+0x1c/0x21 >>>>> [11159.499238] [<ffffffffb992077b>] ? system_call_after_swapgs+0xc8/ >>>>> 0x160 >>>>> [11279.488720] INFO: task xfsaild/dm-10:1134 blocked for more than 120 >>>>> seconds. >>>>> [11279.490197] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" >>>>> disables this message. >>>>> [11279.491665] xfsaild/dm-10 D ffff9720a8660fd0 0 1134...