similar to: Ext3 works on Debian PPC

I've attached the .gz'ed log of another EXT3 crash on my PPC box. This time it was on IDE and I was doing a tab completion as it died. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/

Hi, I'm using ext3 filesystems in embedded devices (storage is on 512Mb or 1Gb CF cards). A typical development cycle would see the filesystem created on the desktop PC running linux 2.4 (eg. RedHat 9). The CF card would be installed in the hardware and linux 2.4 (eg. Montavista Pro 3.1, on PPC) would boot from the CF. Recently I tried a linux 2.6 desktop (CentOS) for the same task and

Okay, after playing around a bit more, I'm getting two oopes in a row when running dbench 16 or dbench 32. Decoded, here they are: Assertion failure in unmap_underlying_metadata() at buffer.c:1530: "!buffer_jlist_eq(old_bh, 3)" kernel BUG at buffer.c:1530! Oops: Exception in kernel mode, sig: 4 NIP: C003BB34 XER: 00000000 LR: C003BB34 SP: CF881E00 REGS: cf881d50 TRAP: 0700 Using

(It was suggested I send a copy of this to ext3-users, so here it is - note that I need this RAID going so I've rebuilt with reiser, but would still appreciate suggestions; the message was original sent to the lkml) Hi, I've just built an 800GB RAID5 array and built an ext3 file system on it; on trying to copy data off the 200GB RAID it is replacing I'm starting to see errors of the

Hello everyone, I'm new to the list and I hope I'm not repeating something that was already asked for. I had been using the stock kernel that came with Mandrake 8.1 which is kernel 2.4.8-26mdk (not sure what things are applied to a stock 2.4.8) I have my root partition /dev/hda1 on ext3 Mandrake took care of all this, by putting the ext3 module in initrd. I just dl'ed 2.4.13

Hi list! Sometimes I need to make boot floppies for an i386 based Linux router. Just for interest, I tried to use syslinux together with my iMac G4 (PPC) with Yellow Dog Linux to create the floppy. I know that this is generally difficult because it requires cross- compiler and cross-assembler. Nevertheless, I tried it because I only needed the disk installer, the loader binaries for i386

Kernel 2.4.8 on an Athlon 500. e2fsprogs-1.23 ext3 compiled as a module. I used "tune2fs" to make /boot and /home into ext3, and remounted them OK. (I am so amazed to see the system come right back without an lengthy fsck on these two file systems after a power off! Well done!) I also used "tune2fs -j" on /, it created a /.journal file. The debugfs features command shows

Patch against linux-2.4.8 is at http://www.uow.edu.au/~andrewm/linux/ext3/ The only changes here are merging up to 2.4.8 and the bigendian fix. linux-2.4.8-ac1 currently has ext3-0.9.3 which has no known crash-worthy bugs, but is old. I'm about to send Alan a diff which takes -ac up to 0.9.6. The changes between 0.9.3 and 0.9.6 may be summarised as: - Simplify the handling of

Hi all, My system is : kernel 2.4.8 with ext3-0.9.6 patch e2fsprogs-1.22-2, mount-2.11g, util-linux-2.11f And ext3 filesystem works fine, but when a vfat partition is mounted: [fargo] [~] # mount /dev/hdd1 /mnt/tmp [fargo] [~] # mount /dev/hda1 on / type ext2 (rw) none on /proc type proc (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) /dev/hdd1 on /mnt/tmp type vfat (rw) everything looks

Hi, I just tested ext2 and ext3(2.4-0.9.6) with 2.4.8-ac8, using bonnie++-1.01. The hardware is an old Pentium 100 box with 48M RAM and a 16.6MB/s EIDE harddrive. The test results(see attachment) show ext3 is a lot slower than ext2 in most aspects. Does anybody get better results? Wenzhuo

I am running debian unstable. I applied the ext3 patch to the 2.4.9 kernel source, and got ext3 working fine. However, when I shut my system down (shutdown -h now or shutdown from kdm), it does not turn the power off. The whole shutdown sequence runs, and finally displays the message "Power Down", but nothing else happens. At this point, the power switch does not turn off the

I've compiled your patch on a PowerPC with a kernel 2.4.8. All works fine! good Work! NathanK

hi, i have a laptop: asus l5800gm, with a dual boot system: windows xp and linux (debian sarge with kernel 2.4.25) These are the errors when I perform fsck.ext3 -y /dev/hdc1. >pass 1: checking inodes, blocks and sizes >error reading block 1090648 (attempt to read block from filesystem resulted >in short read) while reading indirect blocks of inode 360671. Ignore error? >yes >Force

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

Is there a reason why an ext3 root partition cannot be copied to an alternate partition using the "dd" command? The dd is copying the mounted root partition into an alternate partition that is not mounted. The dd returns success, but the fsck on that partition fails with errors as follows: ----------------- fsck 1.37 (21-Mar-2005) /dev/Active_Update/root2: recovering journal

I'm running Linux travis 2.6.15-1-686 #2 Mon Mar 6 15:27:08 UTC 2006 i686 GNU/Linux on a laptop with ext3 on / Some time ago things started getting weird in the following way: I do a fairly normal hack, ^Z, make, test loop when developing and it seems that vim is calling fsync or sync and that is then flushing everything to disk. My tests create maybe 10 dozen files in ~30MB and for some

Hello ext3-users, I tested ext3 on a Linux for S/390 with several stress and benchmark test tests and faced a kernel bug message. The console showed the following output: Message from syslogd@boeaet34 at Fri Aug 3 11:34:16 2001 ... boeaet34 kernel: Assertion failure in journal_forget() at transaction.c:1184: "! jh->b_committed_data" I tried the Patch from

I've read through the archives and it looks like people are using ext3 with software RAID with at least some success. I just want to confirm that it works properly. If I convert my md RAID 0 to ext3, should I expect A) A fast journalled filesystem, or B) Wailing and gnashing of teeth My RAID currently does not use persistant superblocks, because I created it many moons ago under the old

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 ext3-developers, Just to summarize, I reported a kernel bug message with ext3 on S/390 in transaction.c. I was able to reproduce it with a ext3 on LVM and on MD. Tom Rini reported a similar problem on PPC. (both big endian). I have sent a backtrace and with jbd-debug set to 5 I was not able to reproduce the problem until now. On S/390 there are some more debug possibilities. I would