similar to: kjournald blocked in D state

The latest ext3 patches against linux-2.4.7 and linux-2.4.7-ac3 are at http://www.uow.edu.au/~andrewm/linux/ext3/ Changes since 0.9.4 include: - Fixed a bug which could trip an assertion failure when using small journals under heavy load in full data journalling mode. - A patch from Ted plus the latest version of e2fsprogs plus the stomping of various ext3 bugs gives us preliminary

Hi, A system running ext3 crashed this afternoon (nothing to do with ext3, bad network driver). Is was saving a file from emacs when it happened. The file system is 0.06b and had ordered data as the mount option. Let me emphasize this was running ext3 pure, not with SnapFS or InterMezzo layered on top of it. strace reveals that Emacs does open("existing file name", O_TRUNC |

The patch below contains the following cleanups: - make some needlessly global code static - super.c: remove the unused global function ext3_panic Please comment ib whether this patch is correct or conflicts with pending changes. diffstat output: fs/ext3/balloc.c | 2 fs/ext3/dir.c | 2 fs/ext3/inode.c | 4 fs/ext3/resize.c | 4

An ext3 update for Alan's latest kernel is at http://www.uow.edu.au/~andrewm/linux/ext3/ The version of ext3 in -ac kernels currently stands at 0.9.6, so this is a fairly large diff. However most of this code has had a decent amount of external testing via the 0.9.9 patch. The changelog since 0.9.6 is below. Please test it if you can, and all being well we shall ask Alan to merge it a

I'm a newbie with a TDM11B. I've read the FAQs about linking /usr/src/linux-2.6 to /usr/src/linux-2.6.8-1.521 and /lib/linux-2.6 to /lib/linux-2.6.8-1.521 but still get a million errors and eventual abort during compile. Could someone point me in the right direction? I do a yum update every day and I'm using the CVS from 9/14/04. I'm also using an ASUS CUSL2 system board.

Hi I've just installed Tachyon: The Fringe and it plays but the max resolution that it detects is 1024x768. My monitor is 1600x900. Is there some way of helping it detect the full resolution? I've tried running with a desktop, but no joy. Wine version 1.7.46 Thanks

I''m having trouble capturing the params from a select type form. For text field like this: <%= text_field_tag :courseid %> I''m able to capture the posted value with this params[:courseid] However with a select field like this: <%= select(:course, :id, %w{value1 value2 value3} %> I''m not sure how to capture the posted value. -- Posted via

Hi,guys In my server, the process kjournald used much more cpu time. How can I let my system load down? Thanks. Forrest Wang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20070417/67bf3e94/attachment.htm>

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

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

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

Hello! While performing some zttest's for some time today, I was also keeping an eye of a top of the machine. While the zttest was running, I also had a ssh-keygen and a dd creating a 5GB file on an EXT3 partition running. I noticed that for the most part, I got a decent number of 100%'s, and a bunch of 99.6%'s or higher. However, it seems that whenever the zttest dropped

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

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

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

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'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

Hi, I am getting the following Oops on 2.6.30.1 kernel. The bad part is, it happens rarely (twice in last 1.5 months) and the system is pretty lightly loaded when this happens (no heavy file/disk io). Any insights or patches that I can try? (i searched lkml and ext3 lists but could not find any similar oops/reports). == Oops =================== BUG: unable to handle kernel NULL pointer

(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