similar to: Assertion failure in transaction.c

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

always use the 2.6 variants and fix up for 2.4 under the hood Index: src/journal.c =================================================================== --- src/journal.c (revision 1156) +++ src/journal.c (working copy) @@ -105,9 +105,17 @@ return status; } -#else -#define ocfs_journal_start journal_start -#define ocfs_journal_stop journal_stop + +#define journal_start(journal, nblocks) \ +

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 all, and particularly Andrew and Stephen, I recently "upgraded' one of my NFS fileservers from (patched)2.4.18 to 2.4.23-pre7 (in order to resolve a HIMEM related memory pressure problem). Unfortunately I have experienced what appears to be a deadlock. The one I will describe was experienced while running 2.4.23-pre7, though I had a very similar problem in 2.4.22 (but

Hi All. I have a server which hanged two times because we could not connect to the box, it was not responding. In /var/log/messages I saw: Apr 11 10:13:29 server kernel: INFO: task imap:5855 blocked for more than 120 seconds. Apr 11 10:13:29 server kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 11 10:13:29 server kernel: imap D

Description: Use schedule_timeout_{,un}interruptible() instead of set_current_state()/schedule_timeout() to reduce kernel size. Also use helper functions to convert between human time units and jiffies rather than constant HZ division to avoid rounding errors. Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com> --- fs/cifs/cifsfs.c | 7 ++----- fs/cifs/connect.c

This version fixes three bugs in the 2nd patch of this series that caused kernel BUG when the system was under race. We weren't accounting with t_oustanding_credits correctly, and there were race conditions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use

Hi. I have a RHEL server that has some errors in dmesg , what do they mean, how do I fix them ? mtrr: type mismatch for f9000000,800000 old: write-back new: write-combining mtrr: type mismatch for f9000000,1000000 old: write-back new: write-combining mtrr: type mismatch for f9fe0000,10000 old: write-back new: write-combining mtrr: type mismatch for f9fc0000,20000 old: write-back new:

------------[ cut here ]------------ kernel BUG at fs/ext3/fsync.c:50! invalid operand: 0000 [#1] CPU: 0 EIP: 0060:[<b0187d38>] Not tainted VLI EFLAGS: 00010296 (2.6.13.1) EIP is at ext3_sync_file+0x58/0xf0 eax: 00000068 ebx: bf4a479c ecx: b03cffac edx: b03cffac esi: b0398cfc edi: b2b8f1c8 ebp: c13bcf60 esp: c13bcf18 ds: 007b es: 007b ss: 0068 Process aptitude

I am having some trouble compiling ext3 for the 2.4.13 kernel. It appears that the journaling source file is corrupted: In file included from sysctl.c:33: /src/linux-2.4.13/include/linux/jbd.h: In function `buffer_jbd': /src/linux-2.4.13/include/linux/jbd.h:241: `BH_JBD' undeclared (first use in this function) /src/linux-2.4.13/include/linux/jbd.h:241: (Each undeclared identifier is

I have installed the xen 3.1.0 x86_64 tarball compiled for RHEL5 on a RHEL5 system. The system in question was able to boot with the xen kernel that came with RHEL5. I untarred the tarball, and did cd /boot mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen The command exited properly and made a initrd image. The machine booted with a grub.conf entry like this: title Xen 3.1.0 root

Hello. I found bugs on error handlings in the functions arround the ext3 file system, which cause inadequate completions of synchronous write I/O operations when disk I/O failures occur. Both 2.4 and 2.6 have this problem. I carried out following experiment: 1. Mount a ext3 file system on a SCSI disk with ordered mode. 2. Open a file on the file system with O_SYNC|O_RDWR|O_TRUNC|O_CREAT

Hello, I''m not sure about this, when a device is set read-only, are journal commit still allowed then, or is this the reason, why the umount hangs forever? [44825.302262] LustreError: Skipped 572 previous similar messages [44882.668079] Lustre: Failing over pfs1work-OST0026 [44882.674578] Lustre: *** setting obd pfs1work-OST0026 device ''unknown-block(9,7)'' read-only

Hello fellow listers! I've got some errors starting to crop up on one of my CentOS5 boxes. Below is a transcript: vi S 048C664F 2600 4176 2837 (NOTLB) f1c87b68 00000082 c30229e0 048c664f 00000e65 f1c87b18 00000007 f7bacaa0 f7d97aa0 048c72fc 00000e65 00000cad 00000003 f7bacbac c302a9e0 c042daae f7d20000 f1c87b70 00000286 ffffffff 00000000

Hello ext3-developers, Just to summarize, I reported a kernel bug message with ext3 on S/390 in transaction.c. I was able to reproduce it with a ext3 on LVM and on MD. Tom Rini reported a similar problem on PPC. (both big endian). I have sent a backtrace and with jbd-debug set to 5 I was not able to reproduce the problem until now. On S/390 there are some more debug possibilities. I would

Hi list, After a lot of testing + troubleshooting, I guess I'm observing what I am now calling a regression with zaptel 1.4.10 (is it?) As such I call for peer feedback, before either asking Digium install support or filing a bug. Thanks in advance! System: HP Proliant DL380 G5 with 2x PCI-X + 1x PCIe riser card OS: Centos 5 Kernel: 2.6.18-53.1.14.el5 (also tested under

Hello, Stephen, It seem that in the presence of several jornalling file systems in the kernel some mechanism is needed for proper sharing of the ->journal_info pointer in the task_struct. One journalled file system can indirectly call another during page fault in copy_from_user, quota file modification, or __alloc_pages()->balance_classzone()->shrink_cache()->vm_writeback()

Hi I am hitting this Warning reproducible, the workload is a ceph osd, kernel ist 3.1.0-rc5. Best Regards, martin [ 5472.099766] ------------[ cut here ]------------ [ 5472.099833] WARNING: at fs/btrfs/inode.c:2193 btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]() [ 5472.099838] Hardware name: MS-96B3 [ 5472.099842] Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit psmouse sp5100_tco

Hi all !!! I have got a MOSIX-Cluster and wanted to upgrade to ext3-fs, but that didn't work out. The ext3-fs patch FAILED to patch the MOSIX-kernel and if I tried to apply the ext3- patch before, the MOSIX-patch failed. Can someone help me with that ? Perhaps someone knows of a conclusion for that problem or can tell me where to get a MOSIX-patch for 2.4.15. I would be glad to hear from

Hi all, Is there a way to use the "encrypt passwords" and the "passwd chat" programs simultaneously? smb.conf(5) doesn't mention anything about them being mutually exclusive, yet when I run testparm on the smb.conf file, I get: ERROR: the 'passwd chat' script [...] expects to use the old plaintext password via the %o substitution. With encrypted passwords