similar to: PATCH for filesys corruption in ext3 with data=journal

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

In 2.4.20-pre5 an optimisation was made to the ext3 fsync function which can very easily cause file data corruption at unmount time. This was first reported by Nick Piggin on November 29th (one day after 2.4.20 was released, and three months after the bug was merged. Unfortunate timing) This only affects filesystems which were mounted with the `data=journal' option. Or files which are

Hi Stephen, I'm one of developers of SnapFS, which based on Ext3. I got Assertion failure from SnapFS, at ext3_new_block() in fs/ext3/balloc.c: J_ASSERT (!test_and_set_bit(BH_Alloced, &bh->b_state)) If J_ASSERT is only use as debug, why it will modify data? I found the 'BH_Alloced' flag only occures at two place: one is balloc.c as above, the other is at journal_forget() in

Hello all, I am trying to integerate 0.0.6b with our kernel RPM here and have come across an interesting conflict. I want to include the raid patch that Red Hat includes in their kernel but that patch includes the following hunk: --- linux/include/linux/fs.h.orig Tue Jan 16 13:30:09 2001 +++ linux/include/linux/fs.h Tue Jan 16 13:47:18 2001 @@ -191,6 +191,7 @@ #define BH_Req 3 /* 0 if the

Our main NFS-server, running Debian Potato, died this morning whilst under quite heavy load - due to a runaway perl-script forking of some 200 instances of "/bin/cp" (the load was ~ 50). The server is running 2.2.19pre14 with ext3-0.0.6b. The server is running kernel-nfs. Assertion failure in journal_dirty_metadata() at transaction.c line 796: "bh->b_next_transaction ==

Hi, I found the following, suspect looking, gem in ext3-2.4-0.9.1-246.gz. Is this supposed to compile or is it just a tyypo ? +enum jbd_state_bits { + BH_JWrite + = BH_PrivateStart, /* 1 if being written to log (@@@ DEBUGGING) */ + BH_Freed, /* 1 if buffer has been freed (truncated) */ Rik -- Virtual memory is like a game you can't win; However, without

Hi, I have a 32-bit installation of Arch Linux and I have developed my own little script (in perl) for downloading files over SMB/CIFS using multiple TCP connections to speed up the transfer. I have googled a lot but could not find any good download accelerator for files hosted over SMB/ CIFS. For example, the DownThemAll firefox add-on allows you to download files hosted over SMB/ CIFS, but is

I'm trying to use Filesys::SmbClient to connect to a windows share using kerberos to authenticate, however, I get a permission denied error. I've tried this on a FC5 with samba 3.0.22 and on Solaris 9 with samba 3.0.22 and 3.0.23rc2. Using kerberos with the command smbclient works however. If I specify a password, I can connect; however, I need to use kerberos. Since the smbclient

Hi, I'm missing perl-Filesys-Df ins CentOS-8, I need it because of Df.pm which is in it. Any suggestiosn? Adrian -- Adri P. van Bloois "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

I get 2 rejects applying 2.2.19-ext3 to latest errata rh 2.2.19 kernel. 1) fs/buffer.c Should I put "J_ASSERT(buf->b_count > 0);" before or after " *(int *)0 = 0;"? ===== ext3 0.0.7a patch --- 934,946 ---- if (buf->b_count) { buf->b_count--; + if (!buf->b_count && + (buf->b_jlist != BJ_None && buf->b_jlist

Hi, On Thu, Jan 24, 2002 at 04:54:34PM +0100, frode wrote: > > I got the following error while rm'ing a 700mb file from an ext3 partition: > > Assertion failure in journal_unmap_buffer() at transaction.c:1857: > "transaction == journal->j_running_transaction" Hmm --- this is not one I think I've ever seen before. > >>EIP; c015ea1a

i've built up rsync on both opensuse & osx from src. on osx, it's v2.6.3 w/ both apple's "Extended Attributes" patches: http://www.opensource.apple.com/darwinsource/10.4.8.ppc/rsync-24/patches/EA.diff http://www.opensource.apple.com/darwinsource/10.4.8.ppc/rsync-24/patches/PR-3945747-endian.diff and the 'lartmaker' fix (iteself, slightly fixed ...):

SYSTEM: rh6x based system, 2.2.19-6.2.7 rh errata kernel + 0.0.7a patch, I rebuilt rpm for i686; celeron466, 64MB, PIIX4. root fs is on software raid1 ext2, 6 additional fs's on software raid1 ext2. There's a 3rd HD, not mirrored, which is mounted ext3. EXT3-fs: mounted filesystem with ordered data mode. I enabled journal with tune2fs -j with unmounted fs. The 3 HDs are tuned with

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

We have DELL 2650 with CENTOS 3.4 installed. Today I saw following messages on /var/log/messages. Anyone know what it mean? Does it point to which disk? =================================== Jun 4 06:58:40 ORA03 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0); Jun 4 06:58:40 ORA03 kernel: Possible IO failure. Jun 4 06:58:40 ORA03 kernel:

This is a 2.2.19 machine with ext3-0.0.7a and quota support running. The symptoms are a particular NFS export hangs (for linux clients but not Solaris clients?) the local filesystem gives the following: EXT3-fs warning (device sd(8,49)): ext3_free_blocks: bit already cleared for block 2213 EXT3-fs error (device sd(8,49)): ext3_free_blocks: Freeing blocks not in datazone - block = 1563120916,

Hi all (and developers in particular) I just got bitten by this Assertion. The one that starts as in the subject, and ends with: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)" Google reminds me that it was mentioned a few times earlier this year, but I couldn't find any statement saying that it has been fixed. I got this in a 2.4.16 kernel, though the

Hi, My current code is tripping the following assertion: lib/libzpool/build-kernel/arc.c:736: arc_change_state: Assertion `new_state->size + to_delta >= new_state->lsize (0x2a60000 >= 0x2a64000)` failed. gdb info: Program terminated with signal 6, Aborted. #0 0x00002afcd767847b in raise () from /lib/libc.so.6 (gdb) bt #0 0x00002afcd767847b in raise () from /lib/libc.so.6 #1

I got this.. The system was usuable, but not very. If I tried to access the ext3 volume, it would hang. Reboot hung too, complaining about too many open files. Any ideas? I have no idea what triggered it; this is a big file/web/mail server, with all of that on the ext3 volume. And I've never run ksymoops before, but I think I did it right. - Josh Assertion failure in

I have ext3 0.0.6b + 2.2.19 and cannot get ext3 to compile as a module. If I try to modularize it, or turn in off completely, the kernel build fails. Is there an easy fix for this, or is there something that I am missing? Thanks. Peter