similar to: Assertion failure in ext3_get_block() at inode.c:853: "handle != 0"

Below is a kernel dump that I just got. This is a fresh new install of centos 5.1 on NVIDIA gigabyte MB-GA-M61P-S3. nothing extra has been added. I have not tried the irqpoll but I am surprised to get this. Also the machine keeps running just hod this show on the console... Any ideas??? Jerry Jan 8 05:20:00 localhost kernel: irq 169: nobody cared (try booting with the "irqpoll"

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

Hello Andrew, I patched 2.4.20 with your patch found out on http://lwn.net/Articles/17447/ and I have a big problem with: once server is booted on 2.4.20 with your patch, when I want to reboot with /sbin/reboot, server makes a Segmentation fault and it crashs. I tested it on 50-60 servers and it is the same problem. I tested kernel 2.4.20 without your patch: no problem. # uname -a Linux XXXXXX

http://www.sample.banga.lt/crash.gif System - fully (except kernel) updated RedHat 7.3. Filesystems - ext3 in default ordered mode. What could be the cause of the crash? Kernel update will solve the problem? Thanks, Mindaugas

Hi, I'm running redhat 9 (kernel 2.4.20-8) as a heavy file server using ext3 file system. The server hang once a week and I found the following my log in /var/log/messages It looks like some ext3 quota problem. Anyone has similar experience ? Any suggestion ? Unable to handle kernel paging request at virtual address ffffffff printing eip: ffffffff *pde = 00001067 *pte = 00000000

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

Dear Sirs and Madams, I run a small visual effects production company, Hammerhead Productions. We'd like to have an easily extensible inexpensive relatively high-performance storage network using open-source components. I was hoping that OCFS2 would be that system. I have a half-dozen 2 TB fileservers I'd like the rest of the network to see as a single 12 TB disk, with the aggregate

Hi all. Every few days I am getting a message that looks like the one I have cut and pasted below. It is accompanied by a severe slowdown of the system. In fact, it's practically locked. The machine runs gnome-desktops for 40 users plus about a hundred sessions of a curses based point of sale software, plus a few other functions, so it's a busy machine. Dual Xeon 3.2GHz processors.

I am experimenting with the kernel (as some of you may know), and I have added a whole slew of traces in some relatively sensitive code in the lower levels of the page cache and i/o functions. Most of this tracing not only works but is highly revealing as to what the kernel is doing and why. However, I am now getting this odd content in the trace log (dmesg), and I cannot figure out what it is

Am using RedHat 7.3 with software raid. it was crashing from time to time so i desided to investigate. after running some stress tests on it it died with a kernel message (see below). it might not be ext3 related but since I was running redhat with ext2 for some time without problems (not on the same machine) I thought it might have somthing to do with the fs. Any ideas. I'll try converting

On Monday August 4, akpm@osdl.org wrote: > Daniel Jacobowitz <dan@debian.org> wrote: > > > > I came back this morning and found: > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted >

Asterisk - 1.8.4.1 Dahdi-linux - 2.4.1.2 Dahdi-tools - 2.4.1 Kernel: 2.6.37.6 Kernel BKL: enabled I am upgrading Asterisk on this box. It has an OpenVox A400P PCI analog card with 1 FXO and 1FXS module. This server has been running just fine for two years with Asterisk 1.6.1.0 I've just upgraded all the OS and installed Asterisk 1.8.4.1. On trying to configure the A400P I get: # modprobe

Several times recently my "mutt" email program has looped for hours at a time in the middle of a sys_ftruncate call. This happens when I use the "$" command to write changes out to my mailbox. It does eventually return from the call and everything seems to have worked ok. But in the meantime the CPU is pegged, $MAIL is locked so I can't receive new mail, and signals to

The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.

I wasn't doing anything .. really! ;-) ..but I got this Oops with process = smbd. (Using samba-3.0.28-0.fc7) Is is a samba problem? """ Mar 30 12:26:39 jgs kernel: Oops: 0000 [1] SMP Mar 30 12:26:39 jgs kernel: CPU 0 Mar 30 12:26:39 jgs kernel: Modules linked in: ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink ipt_REJECT xt_tcpudp

In August I reported a problem with the sys_ftruncate call that caused me to reboot my machine. I didn't see any responses to it then on the ext3 list, and the problem is now recurring, so I thought I'd try again. I don't think I've rebooted since the last problem. In the last few days it hasn't taken as long as 17 hours, but it has sometimes taken unusual and uncomfortable

Hi! After switching from UMS (dated 20090701+c0bf670) to KMS (as of 2010-02-01), almost any X activity causes buffer underruns on my firewire soundcard. When the X pointer changes from arrow to the vertical text selection bar, firewire streaming is interrupted. Same with scrolling in firefox or hovering over a link, thus changing the pointer to "hand". Looks like nouveau is disabling

Andi Kleen <ak at suse.de> writes: > As far as I can see there is nothing in ocfs2_ioctl that requires the BKL, > so use unlocked_ioctl Mark, can you please ack/nack this patch and ideally take it into your tree? You're the only file system maintainer who hasn't acknowledged yet. Thanks, -Andi

This patch fixes the data loss which can occur when unmounting a data=journal ext3 filesystem. The core problem is that the VFS doesn't tell the filesystem enough about what is happening. ext3 _needs_ to know the difference between regular memory-cleansing writeback and sync-for-data-integrity purposes. (These two operations are really quite distinct, and the kernel has got it wrong for

Hi, I'd like to use a flash drive as a journal device, with the purpose of keeping the main disk drive spun down as long as possible. I have a couple of questions: 1) Does the journaling code spread write accesses to the journal device evenly, as I hope, or are there blocks that are particularly "hot"? I.e., do I have to worry about the flash device dying quickly because of