Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Kernel upgrade + High disk I/O
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Daivil
n00b
n00b


Joined: 10 Oct 2004
Posts: 48

PostPosted: Wed Feb 20, 2013 10:32 pm    Post subject: Kernel upgrade + High disk I/O Reply with quote

Hello everyone,

I'm encountering a weird issue with one of my MySQL/NFS server within a web infrastructure.
I've upgraded the kernel of this server from 2.6.34 to 3.6.11 (yes, I know, long version gap...).

Anyway, this upgrade has caused a major Disk I/O behaviour as you can see on this graph :

http://94.125.167.135/diskstats_utilization-week.png

Here is the difference between my 2 kernel config files :

Quote:
2,4c2,3
< # Automatically generated make config: don't edit
< # Linux kernel version: 2.6.34-gentoo-r6
< # Fri Nov 26 10:21:14 2010
---
> # Automatically generated file; DO NOT EDIT.
> # Linux/x86_64 3.6.11-gentoo Kernel Configuration
9a9
> CONFIG_INSTRUCTION_DECODER=y
12,16d11
< CONFIG_GENERIC_TIME=y
< CONFIG_GENERIC_CMOS_UPDATE=y
< CONFIG_CLOCKSOURCE_WATCHDOG=y
< CONFIG_GENERIC_CLOCKEVENTS=y
< CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
21d15
< CONFIG_ZONE_DMA=y
22a17
> CONFIG_NEED_SG_DMA_LENGTH=y
24d18
< CONFIG_GENERIC_IOMAP=y
31d24
< CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
33d25
< CONFIG_GENERIC_TIME_VSYSCALL=y
36a29
> CONFIG_ARCH_HAS_CPU_AUTOPROBE=y
40d32
< CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y
44d35
< CONFIG_ARCH_POPULATES_NODE_MAP=y
48,54d38
< CONFIG_HAVE_EARLY_RES=y
< CONFIG_HAVE_INTEL_TXT=y
< CONFIG_GENERIC_HARDIRQS=y
< CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
< CONFIG_GENERIC_IRQ_PROBE=y
< CONFIG_GENERIC_PENDING_IRQ=y
< CONFIG_USE_GENERIC_SMP_HELPERS=y
57,58c41,43
< CONFIG_X86_TRAMPOLINE=y
---
> CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11"
> CONFIG_ARCH_CPU_PROBE_RELEASE=y
> CONFIG_ARCH_SUPPORTS_UPROBES=y
60c45,47
< CONFIG_CONSTRUCTORS=y
---
> CONFIG_HAVE_IRQ_WORK=y
> CONFIG_IRQ_WORK=y
> CONFIG_BUILDTIME_EXTABLE_SORT=y
66d52
< CONFIG_LOCK_KERNEL=y
67a54
> CONFIG_CROSS_COMPILE=""
72a60
> CONFIG_HAVE_KERNEL_XZ=y
76a65
77a67
> CONFIG_DEFAULT_HOSTNAME="(none)"
84a75
90a82
> CONFIG_AUDIT_WATCH=y
91a84,112
> CONFIG_HAVE_GENERIC_HARDIRQS=y
>
> #
> # IRQ subsystem
> #
> CONFIG_GENERIC_HARDIRQS=y
> CONFIG_GENERIC_IRQ_PROBE=y
> CONFIG_GENERIC_IRQ_SHOW=y
> CONFIG_GENERIC_PENDING_IRQ=y
> CONFIG_IRQ_DOMAIN=y
> CONFIG_IRQ_FORCED_THREADING=y
> CONFIG_SPARSE_IRQ=y
> CONFIG_CLOCKSOURCE_WATCHDOG=y
> CONFIG_ARCH_CLOCKSOURCE_DATA=y
> CONFIG_GENERIC_TIME_VSYSCALL=y
> CONFIG_GENERIC_CLOCKEVENTS=y
> CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
> CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
> CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
> CONFIG_GENERIC_CMOS_UPDATE=y
>
> #
> # Timers subsystem
> #
> CONFIG_TICK_ONESHOT=y
> CONFIG_NO_HZ=y
> CONFIG_HIGH_RES_TIMERS=y
97,99c118
---
100a120
> CONFIG_RCU_FANOUT_LEAF=16
109d128
< CONFIG_CGROUP_NS=y
116c135,137
---
118a140
120,121c142,143
< CONFIG_RELAY=y
---
125d146
< CONFIG_USER_NS=y
127a149,151
> CONFIG_RELAY=y
132a157
> CONFIG_RD_XZ=y
137c162
---
139c164
< CONFIG_SYSCTL_SYSCALL=y
---
142d166
< CONFIG_KALLSYMS_EXTRA_PASS=y
147a172
> CONFIG_HAVE_PCSPKR_PLATFORM=y
155a181
162d187
< CONFIG_PERF_COUNTERS=y
170d194
175,176c199,200
< CONFIG_KPROBES=y
< CONFIG_OPTPROBES=y
---
> CONFIG_OPROFILE_NMI_TIMER=y
178d201
< CONFIG_KRETPROBES=y
184a208,209
> CONFIG_USE_GENERIC_SMP_HELPERS=y
> CONFIG_GENERIC_SMP_IDLE_THREAD=y
187a213
> CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
188a215,224
> CONFIG_HAVE_PERF_EVENTS_NMI=y
> CONFIG_HAVE_ARCH_JUMP_LABEL=y
> CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
> CONFIG_HAVE_ALIGNED_STRUCT_PAGE=y
> CONFIG_HAVE_CMPXCHG_LOCAL=y
> CONFIG_HAVE_CMPXCHG_DOUBLE=y
> CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y
> CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y
> CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
> CONFIG_SECCOMP_FILTER=y
194d229
199,204c234
< CONFIG_MODULES=y
< CONFIG_MODULE_UNLOAD=y
< CONFIG_MODULE_FORCE_UNLOAD=y
---
207a238
208a240,261
>
> #
> # Partition Types
> #
> CONFIG_PARTITION_ADVANCED=y
> CONFIG_OSF_PARTITION=y
> CONFIG_AMIGA_PARTITION=y
> CONFIG_MAC_PARTITION=y
> CONFIG_MSDOS_PARTITION=y
> CONFIG_BSD_DISKLABEL=y
> CONFIG_MINIX_SUBPARTITION=y
> CONFIG_SOLARIS_X86_PARTITION=y
> CONFIG_UNIXWARE_DISKLABEL=y
> CONFIG_SGI_PARTITION=y
> CONFIG_SUN_PARTITION=y
> CONFIG_KARMA_PARTITION=y
> CONFIG_EFI_PARTITION=y
217d269
228d279
< CONFIG_INLINE_SPIN_UNLOCK=y
256,259c307
< CONFIG_TICK_ONESHOT=y
< CONFIG_NO_HZ=y
< CONFIG_HIGH_RES_TIMERS=y
< CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
---
> CONFIG_ZONE_DMA=y
261,262d308
< CONFIG_SPARSE_IRQ=y
< CONFIG_NUMA_IRQ_DESC=y
271,282d316
284,292d317
297,298c322
< CONFIG_X86_CPU=y
< CONFIG_X86_INTERNODE_CACHE_SHIFT=7
---
> CONFIG_X86_INTERNODE_CACHE_SHIFT=6
314d337
321,322d343
< CONFIG_AMD_IOMMU=y
< CONFIG_AMD_IOMMU_STATS=y
325d345
< CONFIG_IOMMU_API=y
329a350
349a371
> CONFIG_ARCH_DMA_ADDR_T_64BIT=y
352c374
< CONFIG_K8_NUMA=y
---
> CONFIG_AMD_NUMA=y
357,358d378
< CONFIG_ARCH_PROC_KCORE_TEXT=y
< CONFIG_ARCH_SPARSEMEM_DEFAULT=y
359a380
> CONFIG_ARCH_SPARSEMEM_DEFAULT=y
360a382
> CONFIG_ARCH_PROC_KCORE_TEXT=y
363,364d384
372a393,395
> CONFIG_HAVE_MEMBLOCK=y
> CONFIG_HAVE_MEMBLOCK_NODE_MAP=y
> CONFIG_ARCH_DISCARD_MEMBLOCK=y
375a399
384a409,412
> CONFIG_CROSS_MEMORY_ATTACH=y
387c415
< CONFIG_X86_RESERVE_LOW_64K=y
---
> CONFIG_X86_RESERVE_LOW=64
391a420
> CONFIG_ARCH_RANDOM=y
392a422
411c441
< CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
---
> CONFIG_USE_PERCPU_NUMA_NODE_ID=y
417,425d446
< CONFIG_PM=y
< CONFIG_PM_DEBUG=y
< CONFIG_CAN_PM_TRACE=y
< CONFIG_PM_TRACE=y
< CONFIG_PM_TRACE_RTC=y
< CONFIG_PM_SLEEP_SMP=y
< CONFIG_PM_SLEEP=y
427d447
429c449
< CONFIG_HIBERNATION_NVS=y
---
> CONFIG_HIBERNATE_CALLBACKS=y
431a452,455
> CONFIG_PM_SLEEP=y
> CONFIG_PM_SLEEP_SMP=y
433c457,463
< CONFIG_PM_OPS=y
---
> CONFIG_PM=y
> CONFIG_PM_DEBUG=y
> CONFIG_PM_SLEEP_DEBUG=y
> CONFIG_PM_TRACE=y
> CONFIG_PM_TRACE_RTC=y
438,439c468
< CONFIG_ACPI_SYSFS_POWER=y
---
447a477
458a489,492
466d499
< CONFIG_CPU_FREQ_DEBUG=y
469d501
480c512
< # CPUFreq processor drivers
---
> # x86 CPU frequency scaling drivers
494a527,528
508,511c542
< CONFIG_DMAR=y
< CONFIG_DMAR_FLOPPY_WA=y
---
517c548,552
---
> CONFIG_PCIEASPM=y
> CONFIG_PCIEASPM_DEFAULT=y
520a556
523c559,562
---
> CONFIG_PCI_ATS=y
> CONFIG_PCI_IOV=y
> CONFIG_PCI_PRI=y
> CONFIG_PCI_PASID=y
524a564
> CONFIG_PCI_LABEL=y
526c566
< CONFIG_K8_NB=y
---
> CONFIG_AMD_NB=y
548a589
554a596
> CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y
559a602
562a606,608
> CONFIG_KEYS_COMPAT=y
> CONFIG_HAVE_TEXT_POKE_SMP=y
> CONFIG_X86_DEV_DMA_OPS=y
569a616,617
574d621
< CONFIG_IP_FIB_HASH=y
577c624
---
597c644,729
---
> CONFIG_NETFILTER=y
> CONFIG_NETFILTER_ADVANCED=y
>
> #
> # Core Netfilter Configuration
> #
> CONFIG_NETFILTER_XTABLES=y
>
> #
> # Xtables combined modules
> #
> CONFIG_NETFILTER_XT_MARK=y
>
> #
> # Xtables targets
> #
> CONFIG_NETFILTER_XT_TARGET_RATEEST=y
>
> #
> # Xtables matches
> #
> CONFIG_NETFILTER_XT_MATCH_COMMENT=y
> CONFIG_NETFILTER_XT_MATCH_IPRANGE=y
> CONFIG_NETFILTER_XT_MATCH_LENGTH=y
> CONFIG_NETFILTER_XT_MATCH_LIMIT=y
> CONFIG_NETFILTER_XT_MATCH_MARK=y
> CONFIG_NETFILTER_XT_MATCH_MULTIPORT=y
> CONFIG_NETFILTER_XT_MATCH_RATEEST=y
> CONFIG_NETFILTER_XT_MATCH_RECENT=y
> CONFIG_NETFILTER_XT_MATCH_STATISTIC=y
> CONFIG_NETFILTER_XT_MATCH_STRING=y
> CONFIG_NETFILTER_XT_MATCH_TCPMSS=y
> CONFIG_NETFILTER_XT_MATCH_TIME=y
>
> #
> # IP: Netfilter Configuration
> #
> CONFIG_IP_NF_IPTABLES=y
> CONFIG_IP_NF_FILTER=y
> CONFIG_IP_NF_TARGET_REJECT=y
602a735
612d744
626a759
633a767,771
634a773
659a799
663a804
665a807,814
> CONFIG_DNS_RESOLVER=y
> CONFIG_RPS=y
> CONFIG_RFS_ACCEL=y
> CONFIG_XPS=y
> CONFIG_BQL=y
671d819
678,688c826
< CONFIG_WIRELESS=y
<
< #
< # CFG80211 needs to be enabled for MAC80211
< #
<
< #
< # Some wireless drivers require a rate control algorithm
< #
---
691a830,833
> CONFIG_HAVE_BPF_JIT=y
701c843,844
---
> CONFIG_DEVTMPFS=y
> CONFIG_DEVTMPFS_MOUNT=y
709a853,854
> CONFIG_DMA_SHARED_BUFFER=y
722a868
728a875
> CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
731a879
741c889,936
---
>
> #
> # Misc devices
> #
>
> #
> # EEPROM support
> #
>
> #
> # Texas Instruments shared transport line discipline
> #
>
> #
> # Altera FPGA firmware download module
> #
810c1005
---
> CONFIG_RAID_ATTRS=y
831d1025
< CONFIG_SCSI_WAIT_SCAN=m
843a1038,1040
844a1042
856a1055
860,863c1059,1067
---
> CONFIG_MEGARAID_NEWGEN=y
> CONFIG_MEGARAID_MM=y
> CONFIG_MEGARAID_MAILBOX=y
> CONFIG_MEGARAID_LEGACY=y
> CONFIG_MEGARAID_SAS=y
> CONFIG_SCSI_MPT2SAS=y
> CONFIG_SCSI_MPT2SAS_MAX_SGE=128
> CONFIG_SCSI_MPT2SAS_LOGGING=y
874a1079
899a1105,1108
>
> #
> # Controllers with non-SFF native interface
> #
900a1110,1112
903c1115,1126
---
>
> #
> # SFF controllers with custom DMA interface
> #
> CONFIG_ATA_BMDMA=y
>
> #
> # SATA SFF controllers with BMDMA
> #
907,908d1129
910d1130
912a1133
916,917c1137,1140
---
>
> #
> # PATA SFF controllers with BMDMA
> #
919a1143
921d1144
923c1146
---
926a1150
929d1152
934d1156
935a1158
937,938d1159
940,941d1160
944d1162
946c1164
---
948d1165
953d1169
954a1171
> CONFIG_PATA_SCH=y
958a1176
961c1179,1195
< CONFIG_PATA_SCH=y
---
>
> #
> # PIO-only SFF controllers
> #
>
> #
> # Generic fallback / legacy drivers
> #
972a1207
978c1213
---
> CONFIG_FUSION_CTL=y
984,991d1218
<
< #
< # You can enable one or both FireWire driver stacks.
< #
<
< #
< # The newer stack is recommended.
< #
993c1220
---
997,998c1224
---
> CONFIG_NET_CORE=y
1000c1226
---
1001a1228,1236
> CONFIG_NETCONSOLE=y
> CONFIG_NETPOLL=y
> CONFIG_NET_POLL_CONTROLLER=y
1004d1238
1005a1240,1324
>
> #
> # CAIF transport drivers
> #
> CONFIG_ETHERNET=y
> CONFIG_NET_VENDOR_ADAPTEC=y
> CONFIG_NET_VENDOR_BROADCOM=y
> CONFIG_BNX2=y
> CONFIG_TIGON3=y
> CONFIG_NET_VENDOR_INTEL=y
> CONFIG_E1000=y
> CONFIG_E1000E=y
> CONFIG_IGB=y
> CONFIG_IGB_PTP=y
> CONFIG_NET_VENDOR_I825XX=y
> CONFIG_NET_VENDOR_MARVELL=y
> CONFIG_NET_VENDOR_NATSEMI=y
> CONFIG_NET_VENDOR_8390=y
> CONFIG_NET_PACKET_ENGINE=y
> CONFIG_NET_VENDOR_REALTEK=y
> CONFIG_NET_VENDOR_WIZNET=y
1010a1330
1018a1339
1027,1058c1348,1349
< CONFIG_NETDEV_1000=y
< CONFIG_E1000E=y
< CONFIG_TIGON3=y
< CONFIG_BNX2=y
<
< #
< # Enable WiMAX (Networking options) to see the WiMAX drivers
< #
---
1069c1360,1364
---
>
> #
> # Enable WiMAX (Networking options) to see the WiMAX drivers
> #
1071,1080d1365
< CONFIG_NETCONSOLE=y
< CONFIG_NETPOLL=y
< CONFIG_NET_POLL_CONTROLLER=y
1083d1367
1091a1376
1108a1394
1110c1396,1397
---
1111a1399,1400
1112a1402
1113a1404,1405
1117a1410
1135a1429
1143a1438
> CONFIG_VT_CONSOLE_SLEEP=y
1146c1441,1443
< CONFIG_DEVKMEM=y
---
> CONFIG_UNIX98_PTYS=y
1148d1444
1151d1446
1154d1448
1157a1452,1453
1159,1160c1455,1462
---
>
> #
> # KCopy
> #
> CONFIG_KCOPY=y
> CONFIG_DEVKMEM=y
1162d1463
1183a1485
1188,1191c1490,1500
< CONFIG_UNIX98_PTYS=y
---
> CONFIG_IPMI_HANDLER=y
> CONFIG_IPMI_PANIC_EVENT=y
> CONFIG_IPMI_PANIC_STRING=y
> CONFIG_IPMI_DEVICE_INTERFACE=y
> CONFIG_IPMI_SI=y
> CONFIG_IPMI_WATCHDOG=y
> CONFIG_IPMI_POWEROFF=y
1209d1517
1220a1529
1253a1563,1565
1254a1567,1568
1260a1575
1268,1269d1582
1273a1587
1278c1592,1613
---
> CONFIG_PPS=y
>
> #
> # PPS clients support
> #
>
> #
> # PPS generators support
> #
>
> #
> # PTP clock support
> #
> CONFIG_PTP_1588_CLOCK=y
>
> #
> # Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks.
> #
1285c1620,1622
---
1286a1624
1288a1627,1631
1312a1656
1314a1659
1323a1669
1324a1671,1672
1325a1674,1675
1337a1688
1339a1691
1340a1693,1694
1341a1696,1698
1342a1700,1701
1345a1705,1706
1346a1708
1347a1710,1712
1350a1716,1719
1352a1722
1353a1724
1363a1735
1368,1369d1739
1374a1745
1376d1746
1378c1748
---
> CONFIG_THERMAL_HWMON=y
1379a1750
1389a1761,1762
1396a1770
1402a1777
1407a1783
1431a1808,1813
> CONFIG_BCMA_POSSIBLE=y
>
> #
> # Broadcom specific AMBA
> #
1437a1820,1821
1439a1824,1827
1440a1829,1831
1442a1834
1443a1836,1837
1444a1839,1842
1446c1844
---
1450c1848,1850
---
1451a1852,1859
1467a1876
1470a1880,1886
>
> #
> # I2C encoder or helper chips
> #
1472d1887
1478a1894,1900
1493a1916
1517a1941
1537a1962,1963
1541a1968,1969
1547c1975
---
1549,1553c1977,1979
<
< #
< # Display device support
< #
---
1563c1989
---
> CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
1573,1575d1998
< CONFIG_HID_SUPPORT=y
< CONFIG_HID=y
1578c2001
< # USB Input Devices
---
> # HID support
1580,1582c2003,2007
< CONFIG_USB_HID=y
---
> CONFIG_HID=y
> CONFIG_HID_GENERIC=y
1587d2011
1588a2013
1589a2015
1595a2022
1596a2024,2025
1597a2027,2028
1600a2032,2033
1601a2035
> CONFIG_HID_LOGITECH_DJ=y
1604a2039
1606d2040
1607a2042
1613c2048,2051
---
1616c2054
---
1621a2060
1627,1628c2066,2073
< CONFIG_USB_SUPPORT=y
< CONFIG_USB_ARCH_HAS_HCD=y
---
>
> #
> # USB HID support
> #
> CONFIG_USB_HID=y
1630a2076,2079
> CONFIG_USB_ARCH_HAS_XHCI=y
> CONFIG_USB_SUPPORT=y
> CONFIG_USB_COMMON=y
> CONFIG_USB_ARCH_HAS_HCD=y
1638,1639d2086
< CONFIG_USB_DEVICEFS=y
1642d2088
1657a2104,2105
1664,1665c2112
---
1683a2131
1694a2143
1729a2179,2184
>
> #
> # USB Physical Layer drivers
> #
1745c2200
---
1747a2203,2204
1749a2207
1751a2210,2213
1752a2215,2218
>
> #
> # LED Triggers
> #
1759a2226
> CONFIG_EDAC_LEGACY_SYSFS=y
1761a2229
1782a2251
1785a2255
1794a2265,2266
1825a2298
1826a2300,2301
1828a2304
1831c2307
< # TI VLYNQ
---
> # Virtio drivers
1832a2309,2316
>
> #
> # Microsoft Hyper-V guest support
> #
1835c2319
---
1838a2323,2324
1840a2327
1844d2330
1846d2331
1848a2334,2368
>
> #
> # Hardware Spinlock drivers
> #
> CONFIG_CLKEVT_I8253=y
> CONFIG_I8253_LOCK=y
> CONFIG_CLKBLD_I8253=y
> CONFIG_IOMMU_API=y
> CONFIG_IOMMU_SUPPORT=y
> CONFIG_AMD_IOMMU=y
> CONFIG_AMD_IOMMU_STATS=y
>
> #
> # Remoteproc drivers (EXPERIMENTAL)
> #
>
> #
> # Rpmsg drivers (EXPERIMENTAL)
> #
1858a2379
1859a2381
1863a2386
> CONFIG_DCACHE_WORD_ACCESS=y
1874c2397,2401
---
> CONFIG_EXT4_FS=y
> CONFIG_EXT4_FS_XATTR=y
> CONFIG_EXT4_FS_POSIX_ACL=y
> CONFIG_EXT4_FS_SECURITY=y
1876a2404,2405
> CONFIG_JBD2=y
1878c2407,2412
---
> CONFIG_REISERFS_FS=y
> CONFIG_REISERFS_PROC_INFO=y
> CONFIG_REISERFS_FS_XATTR=y
> CONFIG_REISERFS_FS_POSIX_ACL=y
> CONFIG_REISERFS_FS_SECURITY=y
1880d2413
< CONFIG_FS_POSIX_ACL=y
1887d2419
1889a2422,2423
> CONFIG_FS_POSIX_ACL=y
> CONFIG_EXPORTFS=y
1893d2426
< CONFIG_INOTIFY=y
1894a2428
1904d2437
1912c2445,2452
---
> CONFIG_FSCACHE=y
> CONFIG_FSCACHE_STATS=y
> CONFIG_FSCACHE_HISTOGRAM=y
> CONFIG_CACHEFILES=y
> CONFIG_CACHEFILES_HISTOGRAM=y
1942a2483
> CONFIG_TMPFS_XATTR=y
1962a2504
1963a2506
1967a2511
> CONFIG_NFS_V2=y
1970a2515
1971a2517,2519
> CONFIG_NFS_USE_KERNEL_DNS=y
1979d2526
< CONFIG_EXPORTFS=y
1984,1986c2531
< CONFIG_RPCSEC_GSS_KRB5=y
---
1992,2013d2536
<
< #
< # Partition Types
< #
< CONFIG_PARTITION_ADVANCED=y
< CONFIG_OSF_PARTITION=y
< CONFIG_AMIGA_PARTITION=y
< CONFIG_MAC_PARTITION=y
< CONFIG_MSDOS_PARTITION=y
< CONFIG_BSD_DISKLABEL=y
< CONFIG_MINIX_SUBPARTITION=y
< CONFIG_SOLARIS_X86_PARTITION=y
< CONFIG_UNIXWARE_DISKLABEL=y
< CONFIG_SGI_PARTITION=y
< CONFIG_SUN_PARTITION=y
< CONFIG_KARMA_PARTITION=y
< CONFIG_EFI_PARTITION=y
2052a2576,2586
2054d2587
2060a2594
> CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4
2065a2600
2068a2604
2071c2607,2610
---
> CONFIG_PANIC_ON_OOPS_VALUE=0
2085a2625
2087c2627
---
2089a2630
> CONFIG_DEBUG_STACK_USAGE=y
2097a2639
2105,2106c2647,2649
---
> CONFIG_RCU_CPU_STALL_TIMEOUT=60
2109a2653
2110a2655
2113d2657
< CONFIG_SYSCTL_SYSCALL_CHECK=y
2123a2668
> CONFIG_HAVE_C_RECORDMCOUNT=y
2125a2671
> CONFIG_EVENT_POWER_TRACING_DEPRECATED=y
2133d2678
2136d2680
2140d2683
2142,2143d2684
2145c2686,2687
< CONFIG_KPROBE_EVENT=y
---
2151a2694
2155a2699
2161,2162d2704
< CONFIG_DEBUG_STACK_USAGE=y
2166c2708
< CONFIG_DEBUG_NX_TEST=m
---
2170d2711
2183a2725
2188a2731
2189a2733
2194d2737
2205a2749,2750
2206a2752
2208,2209d2753
2226c2770
< CONFIG_CRYPTO_PCOMP=y
---
> CONFIG_CRYPTO_PCOMP2=y
2228a2773,2774
> CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
2235d2780
2275a2821
2290a2837
2291a2839
2300a2849,2850
2303a2854,2855
2315a2868,2869
2318d2871
2326a2880,2881
> CONFIG_GENERIC_STRNCPY_FROM_USER=y
> CONFIG_GENERIC_STRNLEN_USER=y
2328,2329c2883,2885
< CONFIG_GENERIC_FIND_NEXT_BIT=y
< CONFIG_GENERIC_FIND_LAST_BIT=y
---
> CONFIG_GENERIC_PCI_IOMAP=y
> CONFIG_GENERIC_IOMAP=y
> CONFIG_GENERIC_IO=y
2331c2887
---
> CONFIG_CRC16=y
2334a2891,2895
> CONFIG_CRC32_SLICEBY8=y
2336a2898
2337a2900
> CONFIG_LZO_COMPRESS=y
2338a2902,2910
> CONFIG_XZ_DEC=y
> CONFIG_XZ_DEC_X86=y
> CONFIG_XZ_DEC_POWERPC=y
> CONFIG_XZ_DEC_IA64=y
> CONFIG_XZ_DEC_ARM=y
> CONFIG_XZ_DEC_ARMTHUMB=y
> CONFIG_XZ_DEC_SPARC=y
> CONFIG_XZ_DEC_BCJ=y
2341a2914
> CONFIG_DECOMPRESS_XZ=y
2342a2916,2919
> CONFIG_TEXTSEARCH=y
> CONFIG_TEXTSEARCH_KMP=y
> CONFIG_TEXTSEARCH_BM=y
> CONFIG_TEXTSEARCH_FSM=y
2345a2923,2925
> CONFIG_CHECK_SIGNATURE=y
> CONFIG_CPU_RMAP=y
> CONFIG_DQL=y
2346a2927,2930
> CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y


(I've exluded (is not set lines from output).

What could have caused such issue? Any idea anyone?

Thanks,
Back to top
View user's profile Send private message
Daivil
n00b
n00b


Joined: 10 Oct 2004
Posts: 48

PostPosted: Wed Feb 20, 2013 10:39 pm    Post subject: Reply with quote

Clue : iotop -o seems to report a high I/O usage from kjournald. This is ext3.

Is there a kernel option (or feature) that could explain such difference between 2.6.34 and 3.6.11 regarding ext3 performance/journal ?
Back to top
View user's profile Send private message
KaZeR
Apprentice
Apprentice


Joined: 04 Feb 2004
Posts: 270
Location: Au fond, à droite.

PostPosted: Wed Feb 27, 2013 9:32 am    Post subject: Reply with quote

Hi,

I've seen similar issues in the past which where related to the chosen IO scheduler.
Which scheduler are you using?
_________________
Foo.
Back to top
View user's profile Send private message
aCOSwt
Moderator
Moderator


Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space

PostPosted: Wed Feb 27, 2013 10:46 am    Post subject: Reply with quote

which options do you mount your fs with ? (data= ? atime ?...)
Did you change anything about this ?

I can't be absolutely sure about this but I think I remember that sometimes since 2.6.32... possibly 2.6.34 some mount option was dropped from the default set of options.

EDIT : Yess ! it was journal-checksum
_________________
Back to top
View user's profile Send private message
Daivil
n00b
n00b


Joined: 10 Oct 2004
Posts: 48

PostPosted: Thu Feb 28, 2013 7:58 am    Post subject: Reply with quote

Hi,

Thanks for your answers.

Here are my mount options :

Code:
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,noatime,errors=continue,barrier=1,data=writeback)
devtmpfs on /dev type devtmpfs (rw,relatime,size=6146948k,nr_inodes=1536737,mode=755)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
cgroup_root on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
openrc on /sys/fs/cgroup/openrc type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib64/rc/sh/cgroup-release-agent.sh,name=openrc)
cpuset on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cpu on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
cpuacct on /sys/fs/cgroup/cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)
freezer on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
/dev/sda4 on /var type ext3 (rw,noatime)
nfsd on /proc/fs/nfsd type nfsd (rw,noexec,nosuid,nodev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
/dev/sda1 on /boot type ext2 (rw,noatime)


The scheduler options i'm using is :

Code:
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set
CONFIG_INLINE_READ_UNLOCK=y
# CONFIG_INLINE_READ_UNLOCK_BH is not set
CONFIG_INLINE_READ_UNLOCK_IRQ=y
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_WRITE_TRYLOCK is not set
# CONFIG_INLINE_WRITE_LOCK is not set
# CONFIG_INLINE_WRITE_LOCK_BH is not set
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set
# CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set
CONFIG_INLINE_WRITE_UNLOCK=y
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_FREEZER=y
Back to top
View user's profile Send private message
aCOSwt
Moderator
Moderator


Joined: 19 Oct 2007
Posts: 2537
Location: Hilbert space

PostPosted: Thu Feb 28, 2013 8:25 am    Post subject: Reply with quote

Daivil wrote:

Code:
/dev/root on / type ext3 (rw,noatime,errors=continue,barrier=1,data=writeback)
/dev/sda4 on /var type ext3 (rw,noatime)
/dev/sda1 on /boot type ext2 (rw,noatime)


Because the graphics you posted in the OP concerns /dev/sda, can you tell which fs (root or var) is the most concerned ?

BTW you are aware of the impacts of setting barrier=1.
Did you pass from the default nobarrier to barrier =1 coincidentally with your kernel upgrade ?
_________________
Back to top
View user's profile Send private message
smlbstcbr
n00b
n00b


Joined: 08 Apr 2006
Posts: 34

PostPosted: Thu Feb 28, 2013 3:17 pm    Post subject: Reply with quote

I think you've finally found yourself with this:

http://forums.gentoo.org/viewtopic-t-482731-postdays-0-postorder-asc-start-0.html
http://forums.gentoo.org/viewtopic-t-793263-postdays-0-postorder-asc-start-0.html

As an advice, I've been using the Deadline scheduler and seems to be a decent solution to the unresponsiveness of the system during disk access.
Back to top
View user's profile Send private message
Daivil
n00b
n00b


Joined: 10 Oct 2004
Posts: 48

PostPosted: Fri Mar 01, 2013 6:49 am    Post subject: Reply with quote

aCOSwt wrote:
Daivil wrote:

Code:
/dev/root on / type ext3 (rw,noatime,errors=continue,barrier=1,data=writeback)
/dev/sda4 on /var type ext3 (rw,noatime)
/dev/sda1 on /boot type ext2 (rw,noatime)


Because the graphics you posted in the OP concerns /dev/sda, can you tell which fs (root or var) is the most concerned ?

BTW you are aware of the impacts of setting barrier=1.
Did you pass from the default nobarrier to barrier =1 coincidentally with your kernel upgrade ?


It concerns /var/.

I'm not aware of the impact of barrier=1. What's the impact?
Back to top
View user's profile Send private message
_______0
Guru
Guru


Joined: 15 Oct 2012
Posts: 521

PostPosted: Fri Mar 01, 2013 12:08 pm    Post subject: Reply with quote

which program keeps the statistics and makes that graph?
Back to top
View user's profile Send private message
Chiitoo
l33t
l33t


Joined: 28 Feb 2010
Posts: 833
Location: Here and Away Again

PostPosted: Fri Mar 01, 2013 1:05 pm    Post subject: ><)))°€ Reply with quote

_______0 wrote:
which program keeps the statistics and makes that graph?

I was interested of that as well, and right now, am emerging something with the faint 'Munin 2.0.8' around the bottom-centre of the image working as a clue. ^^
_________________
Kind Regards,
~ The Noob Unlimited ~

Sore wa sore, kore wa kore.
Back to top
View user's profile Send private message
KaZeR
Apprentice
Apprentice


Joined: 04 Feb 2004
Posts: 270
Location: Au fond, à droite.

PostPosted: Fri Mar 01, 2013 2:52 pm    Post subject: Reply with quote

Daivil wrote:

I'm not aware of the impact of barrier=1. What's the impact?


Barriers are known to have a nasty impact on performances : http://lwn.net/Articles/283164/
_________________
Foo.
Back to top
View user's profile Send private message
Daivil
n00b
n00b


Joined: 10 Oct 2004
Posts: 48

PostPosted: Sat Mar 02, 2013 9:40 am    Post subject: Re: ><)))°€ Reply with quote

Chiitoo wrote:
_______0 wrote:
which program keeps the statistics and makes that graph?

I was interested of that as well, and right now, am emerging something with the faint 'Munin 2.0.8' around the bottom-centre of the image working as a clue. ^^


Yes, it's munin !
Back to top
View user's profile Send private message
Daivil
n00b
n00b


Joined: 10 Oct 2004
Posts: 48

PostPosted: Sat Mar 02, 2013 9:45 am    Post subject: Reply with quote

smlbstcbr wrote:
I think you've finally found yourself with this:

http://forums.gentoo.org/viewtopic-t-482731-postdays-0-postorder-asc-start-0.html
http://forums.gentoo.org/viewtopic-t-793263-postdays-0-postorder-asc-start-0.html

As an advice, I've been using the Deadline scheduler and seems to be a decent solution to the unresponsiveness of the system during disk access.

Changing to Deadline scheduler hasn't changed anything (at all).
Back to top
View user's profile Send private message
Daivil
n00b
n00b


Joined: 10 Oct 2004
Posts: 48

PostPosted: Thu Mar 07, 2013 11:35 pm    Post subject: Reply with quote

I've changed /var/ to ext2 instead of ext3 in my fstab and rebooted my server. Disk IO/Load has fallen to 30/40% instead of 90/100%.

No I need to understand why my 3.6.11 kernel is consuming so much IO/ressources for kJournald with ext3.

Anyone ?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum