similar to: Re: re problems with ext3 well if think it is

Simon May <simon@imsl.es> wrote: > We use kernel 2.4.18 with a slackware linux dist. > e2fsprogs version 1.29 > > you will see that sendmail was the application that lead to the error > at the time the machine was doing a weekly new letter to clients > which puts it under abit of load but not a lot really > the machine has a 1 Gb processor and 768 Mb RAM so is

While ripping one of my cds on my laptop this happened: Message from syslogd@theirongiant at Thu Jul 5 09:52:16 2001 ... theirongiant kernel: Assertion failure in do_get_write_access() at transaction.c line 551: "handle->h_buffer_credits > 0" from the kern.log: Assertion failure in do_get_write_access() at transaction.c line 551: "handle->h_buffer_credits > 0"

Hi, Gettings lots of nasty ext3 errors, as follows: attempt to access beyond end of device 03:06: rw=0, want=1989391900, limit=55167178 EXT3-fs error (device ide0(3,6)): ext3_free_branches: Read failure, inode=10092558, block=-1113264762 - several thousand of these in the course of a few seconds And lots of these: EXT3-fs error (device ide0(3,6)): ext3_free_blocks: Freeing blocks not in

I guess this could be filed under the 'shot myself in the foot' section, but I figured I'd report it anyways.. Kernel 2.5.50-bk6, x86, preempt, PIIX IDE, ext3 fs. I dd'ed the first part of a ext3 partition to tmp, then mounted it via loopback. (the image passed a fsck, except for warning about corrupt part. table or superblock) I tried to 'cd' into a directory within

Hi I've got serious troubles - I posted a while back about experiencing ext3 errors using 2.4.18, at the time I put the problems down to harddisk failure, but these problems are occurring more and more - not all of our systems are having this problem but 3 systems have now shown this problem. The hardware is essentially the same, the only difference is disk manufacturers but we've now

Hello, Over the last month or so, I've noticed the following error showing up repeatedly in my system logs under kernel 2.4.18-ac3 and more recently under 2.4.19-rc1: EXT3-fs error (device ide0(3,3)) in ext3_new_inode: error 28 I've now been able to capture the following Oops before the system went down entirely: Assertion failure in do_get_write_access() at transaction.c:611:

All, I know that there is no official port to Kernel 2.4.4, thus I may not get any help, however I am hoping someone could point me in the right direction for my problem. I am currently forced to use kernel 2.4.4 for reasons out of my control (embedded board). Here are the exact versions of everything I'm running: ExT3 Version: ext3-2.4-0.9.6-248 Util Version: util-linux-2.11f.tar.bz2 e2fs

hello! i'm using redhat 7.2 with ext3 as my primary fs on kernel 2.4.17 + grsecurity + acl after 2-3 days of uptime i'm expiriencing problems... i attached below excert from my system logs. machine stops responing for a few seconds and after then it looks, like it's in normal operation again. the only problem is load, which is incrementing constantly, but cpu is 99% idle... after

Dual Opteron system running ext3 atop drbd (network RAID) devices, which, in turn, are atop LVM logical volumes. The underlying device is hardware SCSI RAID via a LSILogic HBA. The kernel is vanilla 2.6.13 on a Gentoo-based system. A panic occurred, which contains references to ext3 code. I'm not sure how others manage to get these typed out, but I'm manually typing it from

Hi, I'm running stock kernel 2.4.18, and was downloading some things when I filled up one of my partitions. This was sent to all attached terminals: Assertion failure in do_get_write_access() at transaction.c:708: "handle->h_buffer_credits > 0" I think: invalid operand: 0000 may have followed. Anyway, it also gave a stack trace and register dump (to syslog), which I've

Hi list, I was looking for a kernel option to mount the root fs (/) as ext2 with an ext3 enabled kernel. I searched the list archive and I'm not sure whether rootflags=noload is the right option... Can someone give me a hint? I'm using 2.4.6-pre5 with ext3-0.0.8. TIA Juri -- Juri Haberland <juri@koschikode.com>

Hello. On a server running 2.4.25, I have the two following errors in the kernel logfile: Unexpected dirty buffer encountered at do_get_write_access:618 (08:11 blocknr 920707) Unexpected dirty buffer encountered at do_get_write_access:618 (08:11 blocknr 920707) Should I worry about them (disk failure, filesystem damage) ? Thanks. As an addition what does the pair '08:11' means ? Is

Hi folks, I'm using rh72 kernel-2.4.7-10smp. I have a webmail application (sqwebmail + qmail) running together but .. I've got my server crashed since it geting thousands of messages ... the part of error message is: ---xxx-- Assertion Failure in do_get_write_access() at transaction.c:606 .... ....etc ..etc ... --xxx-- how can I fix that ? thx in advance .. Sergio Pereira

Greetings. Total newbie with Ext3. I selected when I upgraded my system to RH7.2. I upgraded my system again to RH8.0. Here is some info: [root@world root]# cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext3 rw 0 0 /proc /proc proc rw 0 0 usbdevfs /proc/bus/usb usbdevfs rw 0 0 none /dev/shm tmpfs rw 0 0 none /dev/pts devpts rw 0 0 /dev/hdd1 /mnt/genericdata1 ext2 rw 0 0 Ok, so

Hi, By running some scripts on our target system for a while, I lost all means of access to the system. It seems that the kernel is crashed with the following error message: Assertion failure in do_get_write_access() at transaction.c:731: "(((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0)" Oops: Exception in kernel mode, sig: 4 We are currently running Linux version

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

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 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 Stephen, I posted a similar report on linux-kernel a month ago, but didn't hear anything new from you. So I try it again in this list, this time with some additional info: Using a stock 2.2.17 kernel with NFS-patches and ext-0.0.3b I can reliably lockup the kjournald when extracting two or three tar.gz files (e.g. kernel tar-balls) onto a ext3 filesystem with activated quotas. This

So there is no way to skip Postfix for incoming messages and go directly to LMTP/LDA but I need two instances of Postfix in that case? Regarding your second question - it is required to be complaint with Direct Trust. Thanks, Adam ?On 4/2/20, 3:07 PM, "dovecot on behalf of Juri Haberland" <dovecot-bounces at dovecot.org on behalf of juri at koschikode.com> wrote: On