similar to: lilo causes a "Unexpected dirty buffer encountered at do_get_write_access:597 (03:02 blocknr 0)"

Hello, I am not subscribed to this mailing list. My apologies if non-members are not allowed to post in this forum. I have a Linux-2.4.19pre10aa4 computer and I have seen an error message "Unexpected dirty buffer encountered at do_get_write_access:598 (03:05 blocknr 0)" appears in the log. With a little bit of research I found that this message is printed from fs/jbd/journal.c,

Right now I'm building a 2.4.17 kernel on an HPPA Linux system. The kernel it ships with supports ext2 only. Has anybody tried ext3 on HPPA? -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandt@charite.de Charite Campus Virchow-Klinikum Tel. +49 (0)30-450 570-155 Referat V A - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 "A man who

We have been using ext3 for our Maildir message store for the better part of a year now. I saw Stephen mention fragmentation and wondered if we might be affected from this as well. How can I find out how fragmented our message store is? -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandt@charite.de Charite Campus Virchow-Klinikum Tel. +49 (0)30-450 570-155

How do I increase the journal size of a partition? -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandt@charite.de Charite Campus Virchow-Klinikum Tel. +49 (0)30-450 570-155 Referat V A - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 The Imperial Vendor or Contractor probably told them that droid armies don't need redundant command centers, nor

Hi! I'm investigating the maximum DB size of mySQL on ext3 with a 2.4 kernel. * mysql is supposed to support tables up to 2^63 bytes * kernel-2.4.x supports files up to a size of 16 TB But what about the filesystem? What are the limits for the local filesystem (ext2, ext3, ReiserFS and XFS) ? -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandt@charite.de Charite Campus

Please have a look at this http://www.net.oregonstate.edu/~kveton/fs/ While I'm not doubting the numbers per se, I fail to see how the lines: ext3 w/ noatime and ext3 w/ noatime,data=ordered can actually be different. According to the docs, the default mode IS data=ordered! -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandt@charite.de Charite Campus Virchow-Klinikum

The ext3-2.4-0.9.17-2418p3 patch applies with 0 fuzz against both 2.4.18 pre 4 and 2.4.18 pre3-ac2. Will it be included into 2.4.18 pre 5? -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandt@charite.de Charite Campus Virchow-Klinikum Tel. +49 (0)30-450 570-155 Referat V A - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 "Debugging is

Hi! We're using 2.4.15-pre5 on our Postfix mailserver. /etc/fstab: LABEL=/var /var auto data=journal 1 2 LABEL=/home /home auto exec,dev,nosuid,rw 1 2 Recently, we got the following entries in our /var/log/messages: Dec 1 00:42:05 postamt1 kernel: invalidate: busy buffer Dec 1 00:42:05 postamt1 last message repeated 329 times

On a 2.4.15-pre5 system with a 3ware-Escalade-68000 IDE RAID (mode 1) we had the follwing "dmesg" output today: EXT3-fs error (device sd(8,38)): ext3_free_blocks: Freeing blocks in system zones - Block = 16, count = 1 EXT3-fs error (device sd(8,38)): ext3_free_blocks: bit already cleared for block 1052672 EXT3-fs error (device sd(8,38)): ext3_free_blocks: Freeing blocks not in datazone

Hi! Today I switched over to devfs. I'm on Debian unstable, installed devfsd, installed a kernel with devfs support and "devfs mount on boot". Reboot, devfs is being used. All over a sudden, dmesg reports: Linux version 2.4.21-ac1 (root@hummus) (gcc version 3.3 (Debian)) #1 Sun Jun 15 19:06:13 CEST 2003 ... kjournald starting. Commit interval 5 seconds EXT3-fs: mounted

There's a big thread about filesystems on postfix-users@postfix.org Could you shed some light on that issue? ----- Forwarded message from Wietse Venema <wietse@porcupine.org> ----- From: wietse@porcupine.org (Wietse Venema) Date: Sun, 3 Feb 2002 07:53:26 -0500 (EST) To: Lawrence Greenfield <leg+@andrew.cmu.edu> Cc: Wietse Venema <wietse@porcupine.org>,

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

Greetings all, I have hit a kernel BUG in revoke.c in kernel 2.4.7-ac7 twice today while attempting to perform the same operation (patching stock 2.4.8 kernel src with "patch -p1 < patch-2.4.8-ac4"). Syslog entries follow. Please email me if you want/need my kernel config or any other information. Thanks, jtp

Hi, I'm running 2.4.9-ac7 with ext3 compiled in, and I ran across this problem. Now that I look back, it makes sence, but it wasn't obvious at first... I wanted to change the journal mode on my / partition, so I changed my fstab to: /dev/hda1 / ext3 defaults,errors=remount-ro,data=journal 0 1 as well as several other partitions, and rebooted. After rebooting I had a read only / that I

I'm lacking some understanding of how to tune / when to tune /proc/sys/vm/bdflush Where can I read up on this? Our current problem: Load is low, but ever so often the system decides to do some serious disk I/O which causes all processes to wait for disk I/O -- load explodes (rises linear up into the 20-30ies) just to fall linearly (spelling?) right after that. We think there might be some

On several machines with ext3 we have a periodic "unresponsiveness" problem. Take for example our mailserver: When it handles a lot of email (lots of deliveries to Maildirs), it shovels the data into the Maildirs. But every now and then (the interval being >> 5s, the commit interval) the machine becomes unresponsive, your hear a lot of disk activity, and after about 12-18s the

Hi! I keep getting errors like these: oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc (dev = 301, inode = 2469218, file_id = 7). [2003/07/31 15:43:22, 0] smbd/oplock.c:oplock_break(843) oplock_break: client failure in break - shutting down this smbd. [2003/07/31 15:47:12, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb error (Success)

Hi! I tried to add an other FiweFire Drive to my existing four devices but it turned out, that the OpenSolaris IEEE1394 support doen''t seem to be well-engineered. After not recognizing the new device and exporting and importing the existing zpool, I get this zpool status: pool: tank state: DEGRADED status: One or more devices could not be used because the label is missing or

Just out of curiosity: Is htree in 2.6.0-test11 ? -- Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-916 Referat V a - Kommunikationsnetze - AIM. ralfpostfix

Hi, I just had my server cry this out to the console: Assertion failure in do_get_write_access() at transaction.c:658: "jh->b_transaction == journal->j_committing_transaction" kernel BUG at transaction.c:658! invalid operand: 0000 CPU: 0 EIP: 0010:[<c015e1f6>] Not tainted EFLAGS: 00010286 eax: 0000007d ebx: c2ff4200 ecx: c243e000 edx: c068af00 esi: c0d6d900