Displaying 20 results from an estimated 5000 matches similar to: "kjournald pegging cpu"
2007 Jun 16
1
kjournald hang on ext3 to ext3 copy
All,
I am running into a situation in which one of my ext3 filesystems is
getting hung during normal usage. There are three ext3 filesystems on a
CompactFLASH. One is mounted as / and one as /tmp. In my test, I am
copying a 100 MB file from /root to /tmp repeatedly. While doing this
test, I eventually see the copying stop, and any attempts to access /tmp
fail - if I even do ls /tmp the
2002 Dec 07
6
kjournald using up majority cpu%.
We run several RH7.2/7.3 servers & recently 2 of them, although still
working fine, have started to show kjournald as generally using over 50%
cpu% on 'top' - virtually continuously. Free cpu% generally less than 25%
now!
Both machines are also using software RAID5 EIDE ....... otherwise are
standard server installs.
Any info on what kjournald is & why it should have recently
2001 Aug 29
1
kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?)
(Sent to linux-raid, linux-kernel and ext3-users since I'm not sure what type of issue
this is)
I've got a test system here running Redhat 7.1 + stock 2.4.9 with these
patches:
http://www.fys.uio.no/~trondmy/src/2.4.9/linux-2.4.9-NFS_ALL.dif
http://www.zip.com.au/~akpm/ext3-2.4-0.9.6-249.gz
http://domsch.com/linux/aacraid/linux-2.4.9-aacraid-20010816.patch
All three patches applied
2015 Apr 16
2
Samba process pegging CPU
On Thu, Apr 16, 2015 at 02:33:20PM +0000, Donaldson Jeff wrote:
> My apologies, went to paste and accidentally sent the message...see below for rest of detail.
>
>
> Greetings,
>
>
> I'm currently experiencing an issue with two of my three Samba servers where one Samba process is pegging the CPU usage and eating up a lot of virtual and resident memory. While this is
2015 Apr 16
3
Samba process pegging CPU
Greetings,
I'm currently experiencing an issue with two of my three Samba servers where one Samba process is pegging the CPU usage and eating up a lot of virtual and resident memory. While this is happening I get a "ERROR(runtime): DsReplicaGetInfo of type 0 failed - (-1073610723, 'NT_STATUS_RPC_PROTOCOL_ERROR')" error when I try to run the samba-tool drs showrepl command.
2002 Oct 03
1
kjournald tuning
While investigating erratic performance on one our our servers,
I'm getting some very odd performance stats coming from vmstat.
What initially appeared to be happening is the machine goes into a hard loop
in some mod_perl webserver code.
Now there still may be an issue with the code, but my code examinations show
no possible way this could be happening, but what I'm writing to you
2015 Apr 17
0
Samba process pegging CPU
I did, but I don't know how to decypher it. Here's a 1.5 second snippet of the the strace -p PID command.
Jeff Donaldson
Technology Director
Newark Charter School
jeff.donaldson at ncs.k12.de.us
(302) 369-2001 ext: 425
________________________________________
From: Jeremy Allison <jra at samba.org>
Sent: Thursday, April 16, 2015 6:49 PM
To: Donaldson Jeff
Cc: samba at
2002 Sep 06
1
kjournald & jbd
Hello everybody,
Could someone please explain to me what is the difference between
kjournald and jbd (precisely, what does each of them do?)
Thank you,
Alina
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
2001 Nov 06
1
ext3/kjournald overhead
Hi,
I've recently installed ext3 on an 800MB RAID5
(software) array. I am running RedHat Linux 7.1 with
the Linux kernel 2.4.12-ac3 on a 1GHz Pentium system
with 128MB RAM. I am seeing a significant amount of
write operation slowdown when running ext3 (and
kjournald), as opposed to my old ext2. The problem
seems to be associated with the times that kjournald
is accessing the disk. At
2015 Apr 16
0
Samba process pegging CPU
My apologies, went to paste and accidentally sent the message...see below for rest of detail.
Greetings,
I'm currently experiencing an issue with two of my three Samba servers where one Samba process is pegging the CPU usage and eating up a lot of virtual and resident memory. While this is happening I get a "ERROR(runtime): DsReplicaGetInfo of type 0 failed - (-1073610723,
2006 Jul 28
1
nautilus pegging the cpu
I have a user that is running centos on
many machines. At each machine, the users is logged
into a common account that is located elsewhere on the network.
Meaning that everyone is logged on as user_x and accessing
the home directory via NFS.
All users are running gnome. On some of the machines, the nautilus
process is pegging the cpu. At this time, I have no strace or other
info to
2005 Feb 04
1
A smbd process pegging CPU at near 100% with v3.0.10-1FC2 RPM
Maybe it's stuck in a library call loop. Try ltrace -p 2170 -f -o
smbd.2170.ltrace.out
-Marc
> -----Original Message-----
> From: Kel Way [mailto:kpwspam-samba@yahoo.com]
> Sent: Friday, February 04, 2005 9:06 AM
> To: Denis Vlasenko; samba@lists.samba.org
> Subject: Re: [Samba] A smbd process pegging CPU at near 100% with
v3.0.10-
> 1FC2 RPM
>
> > strace -p
2006 Dec 22
2
Sangoma Wanpipe 2.3.4-3 compilation fails under FC2 with Zaptel 1.0.9.2
LD [M] /root/wanpipe/patches/kdrivers/wanec/wanec.o
Building modules, stage 2.
MODPOST
*** Warning: "register_wanec_iface"
[/root/wanpipe/patches/kdrivers/wanec/wanec.ko] undefined!
*** Warning: "unregister_wanec_iface"
[/root/wanpipe/patches/kdrivers/wanec/wanec.ko] undefined!
CC /root/wanpipe/patches/kdrivers/wanec/wanec.mod.o
LD [M]
2010 Jun 17
1
kjournald blocked in D state
I have a system on which kjournald becomes blocked in D state quite often.
Looking at a core file we have 5 mounted ext3 filesystems:
crash> mount
VFSMOUNT SUPERBLK TYPE DEVNAME DIRNAME
10037e07b00 10037e4ec00 rootfs rootfs /
10037e07ec0 10037e4e400 proc /proc /proc
10037e07d40 102188abc00 tmpfs
2003 Jun 26
2
ext3 with quota under heavy load.
Hello list,
I have a problem with an NFS server for my network. It has ran kernels
2.4.18-ac4 - 2.4.21-ac1, all with problems. The -ac patches are used
to provide the new style quota support. The system seems to have
gotten even less stable with the new kernel versions.
This morning around 5 am, I got a page the system was unresponding to
NFS requests. I ssh'd in, and found the loadavg
2001 Dec 30
1
Ext3fs performance/kjournald deadlock issue
Hi,
I've got a Redhat 7.2 system:
Celeron 400
512MB RAM
18GB SCSI HD (/boot (ext2fs), / (ext3fs))
40GB IDE HD (/ (ext3fs))
I run a bunch of services on the box (apache + mod_perl, MYSQL, Samba,
etc) but the system is not under heavy load.
This system has performance issues reading/writing to the ext3fs
filesystems. The performance issues cropped up when I installed Redhat
7.2. Previously
2003 Jan 17
1
Write to ext3 fs -> kjournald goes bananas
Hello,
we have just observed a rather annoying behavior one of our servers.
Specifically, when writing data to a file on an ext3fs filesystem at
around 1.5 MB/sec, network connectivity suddently started to show
signs of lag.
The ping would spike up to ~1 second every 5 seconds or so. This affects
the server in question and all hosts routing traffic through it (i.e.,
it's not a userland-only
2005 Feb 15
0
Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
Today our mailserver froze after just one day of uptime. I was able to
capture the Oops on the screen using my digital camera:
http://www.stahl.bau.tu-bs.de/~hildeb/bugreport/
Keywords: EIP is at journal_commit_transaction, process kjournald
# mount
/dev/cciss/c0d0p6 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts
2003 Apr 18
2
kjournald panic in 2.4.20 RedHat 7.2
Hi, If this is a redundant post I apologize. I am running 2.4.20 on what has been
a very stable Athlon machine for months, tried to move a 2 GB file from an ext2
partition to an ext3 and kjournald crashed. Here are the last reminants of my
shell scrollback:
[*ROOT* mofo /mnt/sda1/mysql/fd 641 ] ll oldmail/
total 2363288
-rw-rw---- 1 mysql mysql 2147483647 Jan 23 18:04 maillog.MYD
2005 Jun 14
2
[2.6 patch] fs/jbd/: possible cleanups
This patch contains the following possible cleanups:
- make needlessly global functions static
- journal.c: remove the unused global function __journal_internal_check
and move the check to journal_init
- remove the following write-only global variable:
- journal.c: current_journal
- remove the following unneeded EXPORT_SYMBOL's:
- journal.c: journal_check_used_features
-