similar to: EXT3-fs error: ext3_readdir: bad entry in directory

Hi. I was using ext3 0.0.1 without any problems in the last 33 days (same boot). / was still ext2, but I changed /etc/fstab to ext3. /home/ftp/pub/ is ext3. I mounted /home/ftp/pub/slakware/bare.i with loopback in /mnt/floppy/. After some time: ==> /var/log/syslog <== Jul 4 09:40:51 pervalidus kernel: Assertion failure in ext3_prepare_write() at inode.c:934: "handle != 0" Jul 4

Hi. I was using 2.4.10 with ext3 0.9.10 and thought it was time to use -ac for the first time because 2.4.12-ac3 includes 0.9.12. I don't know what I did to get the following messages, but in my last boot I removed /etc/mtab (at runtime) and made it a symlink to /proc/mounts. Not sure if a bad idea, but the only problem until I rebooted was the need of losetup -d. When I rebooted, all

Hi, I have read this thread and want to say that I have expirienced the same problem. Once, when I was loged in, one of my filesystems ( root filesystem :( ) became read-only with the same symptoms. But results was more tragic. Almost in each directory avg. 10% of files had incorrect attributes, owner, links, etc. But filenames was correct. So, I was obliged to re-create root filesystem :(

I have many errors of this type in my logs: 2 * postfix/pipe[21511]: BC8DD3356A: to=<*****@******>, relay=dovecot, delay=1001, status=bounced (Command time limit exceeded: "/usr/local/dovecot-1.0-rc2/libexec/dovecot/deliver") My command time limit is 1000s in postfix (more than 15 minutes) After many check, I found that a lots of this error is not really an error. The mail is

Is there an updated version of the fileutils df that will show mounted ext3 partitions? I'm using fileutils-4.1. -- Curtis Hogg [buckminst@inconnu.isu.edu] ---------------------------------------------- T-shirt Of The Day: I'm the person your mother warned you about. ---------------------------------------------- Email 1 - buckminst@inconnu.isu.edu Email 2 - buckminst@hotmail.com WWW -

Does the ext3 patch applies on top of the newly released 2.4.6 kernel (and/or the 2.4.6-ac1 variant) ? I want to upgrade to the new kernel and wanted to know before I run into problems if there are any known problems and if it's better to wait for an 'official' release. Thanks. Stelian. -- Stelian Pop <stelian.pop@fr.alcove.com> |---------------- Free Software Engineer

Hi, I am trying to boot from an external USB hard drive (partition 1: Windows, partition 2: primary/bootable ext3). I took the kernel-image-2.6.8-1-368.deb and created a new initrd with all modules, root=/dev/sda2 and Busybox (mkinitrd failed with my own kernel ;-) isolinux.cfg contains: PROMPT 1 DEFAULT sda2 LABEL sda1 KERNEL vmlinuz APPEND initrd=initrd ramdisk=16432k root=/dev/sda1

Hi, I have a severe filesystem crash on a machine with a single ext3 filesystem. It is the second time that this happens to me (on two different machines that are identical in hardware setup and mostly in software - I cloned them when I started to work). It looks like the journal (or something else, i am not an expert here) has gone wild and overwritten loads of inodes. I have a single filesys

Hi, yesterday I upgraded my kernel to 2.4.15-pre6 (after months of using only ac-kernels) and had my first ext3-error since 0.0.3 . syslog tells me : Nov 20 18:16:31 enterprise kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #47390: inode out of bounds - offset=0, inode=404363549, rec_len=4096, name_len=23 and the system remounted /usr to ro. I don't have

Hi. What are the right steps to convert a file system from ext3 back to ext2 ? I need to use GNU Parted to resize my root file system and Andrew Clausen said I have to convert it to ext2, resize, and then convert back to ext3. My journal is visible. My initrd.img (from which I plan to use Parted) contains both ext2 and ext3. I compile ext2 as a module in my other boot images. --

Stelian Pop wrote: > I found out that a new version of ext3-2.4 was available from > the previous messages on this list, despite the fact that > no 'official' announce was given... I thought that the message, https://listman.redhat.com/pipermail/ext3-users/2001-July/000804.html , was the official announcement. BTW, no problems here with 0.9.0. 1 week and some hours of

Hi. While reading Documentation/filesystems/ext2.txt I noticed that the information about ext3 is outdated: The ext3 code is currently (Apr 2001) available for 2.2 kernels only, and not yet available for 2.4 kernels. Journaling (ext3) ftp://ftp.uk.linux.org/pub/linux/sct/fs/jfs/ The file was touched when I applied the 2.4.7 patch from Linus, so I suspect it's maintained. --

Hi. I just installed ext3 for 2.4.5 from http://www.uow.edu.au/~andrewm/linux/ext3/ but couldn't find anything about converting my root partition to ext3. 2 partitions are now ext3 after I umount and tune2fs, but what should I do with / ? I tried init 1 and umount, but tune2fs would fail because it was on read-only fs. Another question is if I can now build ext2 as a module, and if it's

hi all, sorry when i am off topic, but: i am trieing to compile the new e2fsprogs like the ext3-manual recommend. but it don't want to work, and it's look like i need a programm which is named "makeinfo". does anybody had the same problems, or know where i can find it? thanks for all.. i added my error-log Andreas log: make[1]: Wechsel in das Verzeichnis Verzeichnis

Hi, I am getting the following errors on /boot partition on a production server running 2.4.18 kernel. ------------- Aug 10 00:19:37 kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 ------------- /boot is not readable at all and attempt to do an ls will return the same error.

Hi all, OK, here is ext3-0.0.5e. Changes since 5d are summarised below. The major changes are the barrier support: this infrastructure should be sufficient to allow the snapshotting interface which LVM is wanting for ext3. The journal initialisation fix will also help people adding ext3 to an existing filesystem. Look for ext3-0.0.5e.tar.gz on:

Dear Ted, I upgraded e2fsprogs and util-linux to the latest versions, as per the instructions on the "ext3 for 2.4" page, to make the switching between ext2-only and ext3-enabled kernels seamless. Now that if the filesystems have not been unmounted cleanly, due to a power failure for example, "fsck -A -a" cannot continue after checking the root filesystem on reboot, issuing

Hi, I'm encountering a strange situation. I'm writing to an ext3 filesystem mounted like this: /dev/scsi/host2/bus0/target0/lun0/part3 on /tmp/volumes/md0 type ext3 (rw,noatime,data=ordered) with the physical device being a FC-connected RAID (IBM DF4000) no software raid personality is used I'm using 2.4.18-19.7 My test program writes files in a loop, with the essential system

Dear Sir or Ma'am: I am interested to think about implementing EXT3 onto my servers here. However, I have some concerns and am hoping someone can address them. 1) If I install ext3 what is the likelihood that the extent of damage caused by its bugs will be limited to just the fact that the journals may not work properly? Alternatively, do I risk real damage to files and the filesystem at

Hei, 839ca903f12e (drm/nouveau/kms/nv50: transition to atomic interfaces internally, 2016-11-04) seems to introduce a regression on my machine. Attached dmesg output. Has anyone else seen this on a MacBookPro? Thanks. -- Mit freundlichen Grüßen Alexander Alemayhu -------------- next part -------------- [ 0.000000] microcode: microcode updated early to revision 0x16, date = 2016-04-01 [