search for: kupdated

What is really puzzling me is that the ataraid device (/dev/ataraid/d0p1 mounted as /bigdisk) 2x 123GB IBM Deskstar's is formated as ext2...top and ps etc... show a fight between kjournald and kupdated and all searches for kjournald or kupdated fights suggest ext3 issues... :-) It's a RedHat 7.2, 2.4.7-10 custom kernal (I added in the Promise FastTrak support and HIGH mem support to break through the c800MB barrier to use the whole 1GB RAM). Creates the array fine... I get a problem as soo...

Hi, I'm using linux 2.4.25 and I'm trying to change the wakeup interval of kupdate daemon. Is there a way to change that ? I once used 'update' tool for that. But that is not there in 2.4.25. Has it been removed ? I appreciate any help regarding this. thanks, Vijayan

...ksoftirqd_CPU0] root 4 0.0 0.0 0 0 ? SW Aug27 0:03 [kswapd] root 5 0.0 0.0 0 0 ? SW Aug27 0:00 [kreclaimd] root 6 0.0 0.0 0 0 ? DW Aug27 0:00 [bdflush] root 7 0.0 0.0 0 0 ? DW Aug27 0:00 [kupdated] root 9 0.0 0.0 0 0 ? SW< Aug27 0:00 [mdrecoveryd] root 10 0.0 0.0 0 0 ? SW< Aug27 0:00 [raid1d] root 11 0.0 0.0 0 0 ? SW Aug27 0:02 [kjournald] root 130 0.0 0.0 0 0 ? SW Aug27 0:00 [kjou...

hi. i'm using 2.2.18 with ext3-0.0.5e on a dual p3-550 with 1.5 gigs of ram. the system is redhat 6.2-based but with lots of modifications and a clean kernel build. i've been using 2.2.18 and 2.2.17 with ext3 patches on other machines with much success and no problems, up until last night, when the machine mentioned above kernel panicked on me. unfortunately i don't have much of

This patch fixes the data loss which can occur when unmounting a data=journal ext3 filesystem. The core problem is that the VFS doesn't tell the filesystem enough about what is happening. ext3 _needs_ to know the difference between regular memory-cleansing writeback and sync-for-data-integrity purposes. (These two operations are really quite distinct, and the kernel has got it wrong for

...rnel: EFLAGS: 00210286 kernel: kernel: EIP is at journal_blocks_per_page_Rab88fbd5 [jbd] 0x4 (2.4.18-3) kernel: eax: 00000000 ebx: 00000000 ecx: c77b8468 edx: c162412c kernel: esi: c162412c edi: 00000000 ebp: 00000000 esp: c7de7f10 kernel: ds: 0018 es: 0018 ss: 0018 kernel: Process kupdated (pid: 7, stackpage=c7de7000) kernel: Stack: c881f9b3 00000000 c0136eb8 009bfec8 c018c6e2 000000c8 c7de6000 c162412c kernel: c881e12a 00000000 009bfe3d c0353d44 0000000b c7dcdec0 c018ca54 c0353d44 kernel: c162412c 00000004 c1624124 c7de6000 c01275aa c162412c c1624134 c881e0c0 kernel...

My hard drive on a Dell Latitude keeps being accessed every 5 seconds for a couple tenths of a second. Is there a way yo shut this off. I suspect it might be related to journaling? Thanks in advance. -- David I. Sommers, Ph.D. Kensington, MD

...[keventd] root 3 0.0 0.0 0 0 ? SWN 2004 0:00 [ksoftirqd_CPU0] root 4 0.0 0.0 0 0 ? SW 2004 0:00 [kswapd] root 5 0.0 0.0 0 0 ? SW 2004 0:00 [bdflush] root 6 0.0 0.0 0 0 ? SW 2004 0:00 [kupdated] root 7 0.0 0.0 0 0 ? SW 2004 0:00 [kjournald] root 20 0.0 0.0 0 0 ? SW 2004 0:00 [kjournald] root 21 0.0 0.0 0 0 ? SW 2004 0:00 [kjournald] root 22 0.0 0.0 0 0 ? SW 2004 0:02 [kjournald...

...0.0 0:00 ksoftirqd_CPU0 4 root 9 0 0 0 0 SW 0.0 0.0 0:00 kswapd 5 root 9 0 0 0 0 SW 0.0 0.0 0:00 kreclaimd 6 root 9 0 0 0 0 SW 0.0 0.0 0:00 bdflush 7 root 9 0 0 0 0 SW 0.0 0.0 0:00 kupdated 8 root 9 0 0 0 0 SW 0.0 0.0 0:00 kjournald 85 root 11 0 0 0 0 SW 0.0 0.0 0:00 kjournald 155 root 9 0 628 628 524 S 0.0 0.1 0:00 syslogd 160 root 9 0 536 536 404 S 0.0 0.1 0:00 klogd 170 rpc...

Tom Syroid was kind enough to answer my first question. I had some really weird errors and he told me to uninstall the samba that I had compiled on my own and reinstall the samba.tgz that came with slackware 7.1 which is what I am running. I did so, and the weird errors no longer occur. Instead when I try: root@vader82:/# smbclient -L localhost added interface ip=192.168.0.1

...9 ? 00:00:02 ksoftirqd_CPU3 ksoftirqd SW 10 ? 01:50:36 kswapd schedule_timeout SW 11 ? 00:00:27 kreclaimd kreclaimd RW 12 ? 00:26:38 krefilld - SW 13 ? 00:00:06 bdflush bdflush SW 14 ? 00:10:26 kupdated schedule_timeout SW 15 ? 00:00:00 scsi_eh_0 down_interruptible SW 16 ? 00:00:00 scsi_eh_1 down_interruptible SW 17 ? 00:00:03 kjournald kjournald SW 134 ? 00:00:00 kjournald kjournald SW 135 ? 00:00:00 kjo...

Hello everybody! As I wrote in my mail the previous week ("BUG: 2.4.19pre1 & journal_thread & open filehandles") I followed the problem a little bit further. Here's my patch; I beg the ext3-maintainers (Stephen, Andreas, Andrew) to have a look at it and submit it to Marcelo and Linux for inclusion. (2.4 is for now for me more important than 2.5). Patch ----- On every

Hi, I have a large journal of 400MB (the max for 4k blocks), and I'd like to be able to check how much of it is being used. If it's not being used that much, I'd like to know if the writes *from* the journal to the rest of the disk could be delayed until a certain percentage of the journal has been used. It would be nice to be able to get more contiguous writes to the journal for

...5 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kscand/DMA 6 root 15 0 0 0 0 SW 0.0 0.0 3:57 0 kscand/Normal 7 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kscand/HighMem 9 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kupdated 10 root 24 0 0 0 0 SW 0.0 0.0 0:00 0 mdrecoveryd 16 root 21 0 0 0 0 SW 0.0 0.0 0:00 0 scsi_eh_0 19 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kjournald 77 root 25 0 0 0 0 SW 0.0 0.0 0:00 0 khu...

...6 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kscand/DMA 7 root 15 0 0 0 0 SW 0.0 0.0 0:02 0 kscand/Normal 8 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kscand/HighMem 10 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kupdated 11 root 23 0 0 0 0 SW 0.0 0.0 0:00 0 mdrecoveryd 15 root 15 0 0 0 0 SW 0.0 0.0 0:01 0 kjournald 617 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kjournald 942 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 eth...

...23:14 /dev/tun # tincd -n silmuvpn -d5 # ps ax PID TTY STAT TIME COMMAND 1 ? S 0:03 init [2] 2 ? SW 0:00 [keventd] 3 ? SWN 0:00 [ksoftirqd_CPU0] 4 ? SW 0:04 [kswapd] 5 ? SW 0:00 [bdflush] 6 ? SW 0:00 [kupdated] 264 ? S 0:00 /sbin/syslogd 267 ? S 0:02 /sbin/klogd 270 ? S 0:00 /usr/sbin/dhcpd3 -q br0 eth2 281 ? S 0:00 /usr/sbin/inetd 288 ? S 0:03 /usr/sbin/sshd 291 ? S 0:00 /usr/sbin/atd 294 ? S 0:00 /usr/sbin...

...[keventd] root 3 0.0 0.0 0 0 ? SWN Feb02 0:00 [ksoftirqd_CPU0] root 4 0.0 0.0 0 0 ? SW Feb02 0:14 [kswapd] root 5 0.0 0.0 0 0 ? SW Feb02 0:00 [bdflush] root 6 0.0 0.0 0 0 ? SW Feb02 0:00 [kupdated] root 85 0.0 0.0 0 0 ? DW Feb02 0:01 [kjournald] root 292 0.0 1.1 1540 164 ? S Feb02 0:00 /sbin/syslogd root 295 0.0 0.0 2156 4 ? S Feb02 0:01 /sbin/klogd root 309 0.0 0.0 1520 0 ? SW Feb02 0:00 /usr/sbi...

...0:00 ksoftirqd_CPU2 6 root 19 19 0 0 0 SWN 0.0 0.0 0:00 ksoftirqd_CPU3 7 root 9 0 0 0 0 SW 0.0 0.0 305:31 kswapd 8 root 9 0 0 0 0 SW 0.0 0.0 0:00 bdflush 9 root 9 0 0 0 0 SW 0.0 0.0 83:16 kupdated 10 root 9 0 0 0 0 SW 0.0 0.0 13:08 kjournald 122 root 9 0 0 0 0 SW 0.0 0.0 0:00 kjournald 123 root 9 0 0 0 0 SW 0.0 0.0 2:26 kreiserfsd 124 root 9 0 0 0 0 SW 0.0 0.0 1:05 kjournald 125 root...

...root 6 0.0 0.0 0 0 ? SW 00:42 0:00 [kscand/DMA] root 7 0.0 0.0 0 0 ? SW 00:42 0:20 [kscand/Normal] root 8 0.0 0.0 0 0 ? SW 00:42 0:00 [kscand/HighMem] root 10 0.0 0.0 0 0 ? SW 00:42 0:02 [kupdated] root 11 0.0 0.0 0 0 ? SW 00:43 0:00 [mdrecoveryd] root 19 0.0 0.0 0 0 ? SW 00:43 0:00 [raid1d] root 20 0.0 0.0 0 0 ? SW 00:43 0:00 [raid1d] root 21 0.0 0.0 0 0 ? SW 00:43 0:00 [raid1d] root...

...W 0 1 0.0 0.0 khubd 5 root SW 0 1 0.0 0.0 bdflush 2 root SW 0 1 0.0 0.0 keventd 160 root SW 0 1 0.0 0.0 scsi_eh_0 37 root SWN 0 1 0.0 0.0 jffs2_gcd_mtd2 6 root SW 0 1 0.0 0.0 kupdated 7 root SW 0 1 0.0 0.0 cifsoplockd 10 root SW 0 1 0.0 0.0 mtdblockd My router's logfile (<-- means message from server via channel-0): Sat Jan 1 01:00:08 CET 2000 --> client start up... Sat Jan 1 01:00:08 CET 2000 --> storing server key...