similar to: ext3/kjournald overhead

Hello, I have a client with a windows utility that relies on "touch"ing (changing the mod time) on zero-length files in a folder for the purpose of judging when that folder was last accessed. This works fine for him on mapped windows servers, and from the local disk, but from a Samba (v3.0.22) volume, the mod time doesn't change unless there was an actual data change within the

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

I thought I understood things, but I guess not. I recently configured a new system for a colleague as follows: 1. Redhat 7.1 install Dell Inspiron 8100 - three partitions on 30G - /, /boot, swap 2. Boot up 3. configure, make, make install of linux-2.4.12-ac3 (with approriate lilo changes) lilo (but no reboot until 8) 4. rpm -U mount-2.11g-5.i386.rpm (from rawhide)

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

(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

kernel version 2.6.10-1.771_FC2smp We have had quite a few instances of kjournald pegging cpu and thereby effectively knocking out the system's i/o. What can we do to provide more information so that the cause can be identified and fixed? Thanks Christopher

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

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

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

Hi, I'm having trouble migrating from Samba2 to Samba3. I'm trying to make a share that allows some users read-only access, and others read-write. In version 2.2 this worked, but not in version 3. I'm pretty sure it's my configuration, but I ran into this link on the samba bugzilla site, and now I don't know. https://bugzilla.samba.org/show_bug.cgi?id=1844 Can

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

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

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

hi, - big and ugly mail. If you don't like them, delete it now :-) - I have collected and classified some information of: http://home.earthlink.net/~rwhron/kernel/bigbox.html And I observed that ext3 performance is worse than previous kernels(2.4.19...). -ac and -aa are here only as reference. Complete information is in the upper URL. dbench: Performance is worse. dbench (Numbers are in

Hi List - I have a friend that runs a Windows domain with Active Directory and is setting up some new laptops with Redhat. He wants to automate installs, etc. on these laptops as he would on a Windows machine. Just wondering if anyone has any experience with this - and also if anyone knows of a good tutorial for joining a Linux machine to a Windows domain. I've heard that it is possible.

I had the following spat out by syslog on my (2.4.18-pre7-ac3) mailer / web server: Assertion failure in do_get_write_access() at transaction.c:611: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)" One of its partitions froze hard--I've rebooted it, and I have an oops which the BUG() triggered which won't decode at the moment, but I'll sort that one out

I am using a Redhat 7.1 system with the Kernel 2.4.10. I have the two partitions on the system: /dev/hda1 = / /dev/hb5 = /extra I was able to create the journal for both filesystems using the tune2fs -j command. I have also updated my "fstab" file to reflect "ext3" When I try to reboot the machine without unmounting the filesystems. It still shows that I have not cleanly

I have a NFS server with stock 2.4.20 patched with the 5 data=journal patches, plus the 2.4 LSM and NSA's selinux. The partition is mounted with the options: rw,noatime,nosuid,nodev,data=journal,errors=remount-ro The oops seems to happen when the fs is under load. I don't think I encountered this behavior with a non LSM/selinux kernel, so it may have something to do with those, but I

I'm getting oops whenever I pull a big file off of an ext3 filesystem on my large LV. The kernel this comes from happens to have lvm 1.0.2 and posix ACL for ext2/3 patched in, but I get the crash even on vanilla 2.4.17. kymoops 2.4.3 on i686 2.4.17-acl-lvm. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.17-acl-lvm/

I've tried to find my answer to this question but I have not (yet). Any assistance or expert knowledge is greatly appreciated! PROBLEM: mounting an ext3 volume 'read only' results in a different md5sum hash value for the volume than when the same volume is *not* mounted SCENARIO: - when I hash unmounted /dev/hda5 using 'md5sum /dev/hda5' I get value XXX. - when I hash