search for: xfslogd

...> .... >>>> So far I do not have a reproducible test case, >>> >>> Ok. What sort of load is being placed on the machine? >> Hello, generally the load is low, it mainly serves out some samba shares. >> >>> >>> It appears that both the xfslogd and the xfsdatad on CPU 0 are in >>> the running state but don't appear to be consuming any significant >>> CPU time. If they remain like this then I think that means they are >>> stuck waiting on the run queue. Do these XFS threads always appear >>> like th...

...2194 0.0 0.0 0 0 ? S 01:38 0:00 \_ [nfsd] root 2491 0.0 0.0 0 0 ? S 01:38 0:00 \_ [kauditd] root 5430 0.0 0.0 0 0 ? S 01:56 0:00 \_ [xfs_mru_cache] root 5431 0.0 0.0 0 0 ? S 01:56 0:00 \_ [xfslogd/0] root 5432 0.0 0.0 0 0 ? S 01:56 0:00 \_ [xfslogd/1] root 5433 0.0 0.0 0 0 ? S 01:56 0:00 \_ [xfslogd/2] root 5434 0.0 0.0 0 0 ? S 01:56 0:00 \_ [xfslogd/3] root 5435 0.0 0.0 0 0 ? S 0...

I''m tracking performance on the machine I installed yesterday. mutt running on one Xen instance, accessing via imap to another instance, accessing via nfs the maildir in another instances, seems little laggy when moving up and down the message index list. Network latency seems low < 30ms on average. So I was tracking vmstat. On the mutt instances is seems reasonable: [nic@shell:~]

....349765] XFS (sda1): Internal error xfs_sb_read_verify at line 730 of file fs/xfs/xfs_mount.c. Caller 0xffffffffa01faf35 [ 2.349765] [ 2.351733] CPU: 0 PID: 5 Comm: kworker/0:0H Not tainted 3.10.101 #1 [ 2.352728] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 [ 2.353651] Workqueue: xfslogd xfs_buf_iodone_work [xfs] [ 2.354521] 0000000000000001 ffff88001d9dbd68 ffffffff81597c51 ffff88001d9dbd80 [ 2.355762] ffffffffa01fd96b ffffffffa01faf35 ffff88001d9dbdb8 ffffffffa01fd9c5 [ 2.356992] 000002da00002d4e ffff88001c29a180 0000000000000016 ffff88001ba27000 [ 2.358243] Call T...