similar to: Assertion failure in __journal_drop_transaction()

Displaying 20 results from an estimated 3000 matches similar to: "Assertion failure in __journal_drop_transaction()"

2005 Nov 16
0
(large, external) data journal BUG (Assertion failure in __journal_drop_transaction() at fs/jbd/checkpoint.c:626: "transaction->t_forget == NULL")
Hi, A couple of our important servers, both running FC4 but one i386 and one x86_64, have been crashing recently. They both are running ext3 data=journal with large external journals and high commit intervals. Both machines use the gdth driver for their hardware RAID sets, if that's of any use. I think the hardware is good in both cases. I hope someone finds this data useful enough to be
2005 Feb 16
0
Oops in 2.6.8.1 at __journal_drop_transaction
Hi all, One of our mx servers started misbehaving today (postfix would timeout internally, load rising) and after I tried to reboot it, I got this: Assertion failure in __journal_drop_transaction() at fs/jbd/checkpoint.c:613: "transaction->t_forget == NULL" ------------[ cut here ]------------ kernel BUG at fs/jbd/checkpoint.c:613! invalid operand: 0000 [#1] PREEMPT SMP Modules
2005 Jun 07
0
transaction->t_forget == NULL assertion failure with data=journal
It appears that this bug in data=journal mode, https://listman.redhat.com/archives/ext3-users/2005-February/msg00045.html isn't fixed in 2.6.11.11. Andrew, I've CC'd you since you have previously looked at this specific issue. I'm seeing this problem on dual-Opteron x86-64 boxes serving NFS + Samba3 to a few dozen clients; it takes several hours at high load to reproduce. We
2005 May 03
0
several ext3 and mysql kernel crashes
Hi Ext3! I'm running about 30 dedicated MySQL machines under quite decent loads, and they are occassionally crashing. I've been logging console messages recently in an effort to find the cause, and some appear to be related to I perused your lists and found the message I'm replying to. If you don't mind, I've included messages and ksymoops from two crashes that I had
2002 May 31
2
PATCH for filesys corruption in ext3 with data=journal
Hi, as I mentioned in earlier mail to ext3-users I have been getting some corruption on an ext3 filesystem that has been serving NFS. I am now confident that I fully understand the problem and have a patch. It only affects data=journal mode and I wonder if it might also be the cause of the corruption noted by a number of people on linux-kernel. First I will explain the problem. Then display
2001 Oct 07
2
"DRQ after issuing write" error
While writing a file to an ext3 filesystem, i get some drive errors on the console. I guess is a drive/ide related problem more that a ext3 one, but anyway the debug output is here if you want to take a look. And, by the way, what means that DRQ thing?? Oct 7 20:31:36 fargo kernel: (journal.c, 218): kjournald: kjournald wakes Oct 7 20:31:36 fargo kernel: (journal.c, 202): kjournald:
2005 Sep 09
7
[PATCH 0/6] jbd cleanup
The following 6 patches cleanup the jbd code and kill about 200 lines. First of 4 patches can apply to 2.6.13-git8 and 2.6.13-mm2. The rest of them can apply to 2.6.13-mm2. fs/jbd/checkpoint.c | 179 +++++++++++-------------------------------- fs/jbd/commit.c | 101 ++++++++++-------------- fs/jbd/journal.c | 11 +- fs/jbd/revoke.c | 158
2007 May 08
1
kernel: kernel BUG at include/asm/spinlock.h:109!
Hi, We are running a server as an nfs head connect to a clariion, every couple of days we have our box fall over with the following msg in syslog. Has anyone had this happen to there boxen? rhel4 u4 May 8 12:23:52 ruchba kernel: Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:363: "drop_count != 0 || cleanup_ret != 0" May 8 12:23:52 ruchba kernel: ------------[ cut
2005 Feb 15
6
no kernel upgrade on 3.3
I have 2 servers: On both, I did yum update. One upgraded the kernel, the other didn't. Why? TIA, Dave Augustus
2003 Dec 01
0
No subject
Perhaps you can see somethign I can't - or perhaps there is a better way for me to get information for you ? Let me know if there is as this server is not live yet... All the best, Noel NB ATTACHMENTS REMOVED FOR LIST POSTING Domain/network info: Domain = UK Win2000 DC (192.168.5.4) = BRAIN Live Samba server 2.2.3a (192.168.5.5) = BELLY New Samba server 2.2.3a
2008 Mar 18
1
Problems patching fs/jbd/checkpoint.c in RHEL4 2.6.9-67.0.4 kernel
My manual patching of the rejects in checkpoint.c didn''t work out; a delete of 10,000 files caused a panic (in any ext fs, not just Lustre). In the new checkpoint.c, two routines expected by the patch no longer exist: __cleanup_transaction and __flush_buffer. I can avoid the panic if I omit (don''t try to manually patch) the following: Index: linux-2.6.9/fs/jbd/checkpoint.c
2005 Jan 04
0
[PATCH] BUG on error handlings in Ext3 under I/O failure condition
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
2005 May 19
1
ext3 journal problems
This caused a crash on a 2.6.10-1.12_FC2smp kernel May 19 09:56:35 spf1 kernel: Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:361: "drop_count != 0 || cleanup_ret != 0" May 19 09:56:35 spf1 kernel: ------------[ cut here ]------------ May 19 09:56:37 spf1 kernel: kernel BUG at fs/jbd/checkpoint.c:361! May 19 09:56:37 spf1 kernel: invalid operand: 0000 [#1] May 19
2004 Jan 26
0
Anyone run * on OS X ?
With the 1U Apple G5 server at a good reliability/storage/pricepoint level... got to thinking about compiling Asterisk on OS X.. at least for SIP phone call switching, voicemail, etc. Has anybody attempted this? Email me off list if this is too dev-heavy for the user list. Thanks, Ted W -----Original Message----- From: asterisk-users-request@lists.digium.com
2010 Feb 24
3
moving from Xen to KVM
Hello All, I have been building a new server to deploy using Xen. However, seeing that Redhat is moving towards KVM, it would seem beneficial to deply this server using KVM as well. This is a Centos 5.4 x86_64 fresh install. So here is the scoop: * running the xen kernel with 2 vms works great. I have 2 vms- a cobbler host and an ldap host. * running with non-xen kernel, I
2004 Jan 26
0
Digium FXO Card
Hi, I wish to know if GNUGk can work with * running as a gateway with the Digium FXO card. Kindly share your experiences in case there are some issues which one must know before going in for such a setup. Also, I've been reading about the DialTone detection capability by the hardware in different countries. What are the issues with it? Thanks & Regards, Deepak ----- Original Message
2001 Nov 03
1
Patch for kernel 2.4.14pre7
Hi ! Is a ext3 patch for kernel 2.4.14pre7 available ? Patching 2.4.14pre7 with latest patch ext3-2.4-0.9.14-2414p5 fails: patching file include/linux/sched.h Hunk #2 succeeded at 489 (offset 1 line). patching file include/linux/fs.h patching file include/linux/capability.h patching file fs/buffer.c patching file mm/filemap.c Hunk #1 succeeded at 209 (offset 4 lines). patching file mm/vmscan.c
2007 Jun 09
1
Redhat Cluster Manager?
I just spend a few hours working with Redhat Cluster Manager. After working through some things that deal with Centos versus the *upstream provider*, I started configuring a cluster. Even to the point of using HP ILO as the fence. Anyone using this in production? With GFS ? I have used Heartbeat V1 in the past and I am deploying a new colo so I am looking at options. Any feedback is welcome.
2001 Nov 20
1
OH DEAR! - RE: 2.2.2 runaway SMBD process
Jeremy, Bit of bad news - we had a another runaway SMBD. This time profiles were NOT involved - I was simply copying up an installation of Office2000 and then deleting it. It almost reached the end of the deletion when the processor utilisation went up to 90%. The client connection then dropped with a 'connection is no longer available' and there is now 99% processor utilisation on the
2023 May 05
1
[PATCH 2/2] ocfs2: add error handling path when jbd2 enter ABORT status
On 5/5/23 12:20 AM, Heming Zhao wrote: > On Thu, May 04, 2023 at 05:41:29PM +0800, Joseph Qi wrote: >> >> >> On 5/4/23 4:02 PM, Heming Zhao wrote: >>> On Thu, May 04, 2023 at 03:34:49PM +0800, Joseph Qi wrote: >>>> >>>> >>>> On 5/4/23 2:21 PM, Heming Zhao wrote: >>>>> On Thu, May 04, 2023 at 10:27:46AM +0800, Joseph