similar to: Problem with ext3 filesystem

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these

Hi, I'm running kernel 2.6.8-15, lvm2 v2.01.04-5 and acl v2.2.23-1 on a Sunblade 100 (sparc). In a few months we have experienced for several times that an ext3 filesystem is remounted as read-only (this is due to the option "errors=remount-ro" in /etc/fstab). Sometimes there is no error in log files but sometimes we see: kernel: init_special_inode: bogus i_mode (3016) kernel:

Hello list I've been having the following error messages pop up in my kernel log: Apr 12 04:08:09 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: bad entry in directory #2670595: rec_len %% 4 != 0 - offset=0, inode=827218527, rec_len=20275, name_len=73 Apr 12 04:08:14 hal kernel: EXT3-fs error (device md(9,2)): ext3_readdir: bad entry in directory #2670596: rec_len %% 4 != 0 -

Hi RedHat 7.2, ext3 on /, kernel 2.4.18p1. whilst updatedb was running, i had these messages appear... Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_readdir: bad entry in directory #147553: rec_len %% 4 != 0 - offset=0, inode=1651076143, rec_len=19527, name_len=85 Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_readdir: bad entry in directory

Jul 25 01:41:21 big kernel: EXT3-fs error (device device-mapper(254,16)): ext3_readdir: bad entry in directory #248447030: rec_len %% 4 != 0 - offset=0, inode=538976266, rec_len=14637, name_len=49 Jul 25 01:42:53 big kernel: EXT3-fs error (device device-mapper(254,16)): ext3_readdir: bad entry in directory #248447030: rec_len %% 4 != 0 - offset=0, inode=538976266, rec_len=14637, name_len=49

Hi there, I'm not that new in Samba, just paused a little while ;) My actual problem is, that I try to setup a FreeBSD Samba Server who should control share access with authenticating users in a win2k ads domain. The 2K Domain is setup correctly (I think so). Now I created three test shares on the samba server after setting up smbb, nmbd and winbindd. Problem now is any time I try accessing

I have several CentOS5 hosts in a VMware ESX 3.5.0 226117 environment using iSCSI storage. Recently we've begun to experience journal aborts resulting in remounted-read-only filesystems as well as other filesystem issues - I can unmount a filesystem and force a check with "fsck -f" and occasionally find errors. I've found -

Hi, One of my shared volumes crashed the other day on a RH-7.2, 2.4.9-31 system. These are the first errors in the log: kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0 kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is

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, 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.

Hello ext3-users, We have a RH71 machine running 2.4.16 kernel with e2fsprogs 1.25. I noticed many of these errors in our logs. EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #884828: directory entry across blocks - offset=0, inode=404600689, rec_len=23080, name_len=59 EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #966714: rec_len % 4 != 0 -

Hi, I recently upgraded one of my fileservers from 2.4.16 to 2.4.18 plus the ext3-cvs.patch that Andrew Morton pointed me to for addressing and assertion failure. Since then I have been getting lots of errors like: May 21 14:07:03 glass kernel: EXT3-fs error (device md(9,0)): ext3_add_entry: bad entry in directory #2945366: rec_len %% 4 != 0 - offset=0, inode=1886221359, rec_len=24927,

Hi. IIRC, I had the same problem with 2.4.3 and ext2, I'm not sure if with the same directory entry, but at the time fsck fixed without any problems. I only know that the error again is with my Mozilla sources. The Mozilla sources are in another partition. I used lndir from my root fs to symlink everything and build it. At some point c++ segfaulted (happens a lot with my GCC 3.0), and I had

Hi Linus, Here are some 2.6.20 fixes for ocfs2. The patch by Zhen Wei isn't really a fix, but a very small amount of support for a feature which is mostly implemented in ocfs2-tools. Considering it's just a single attribute export via configfs, I'd say it's pretty safe to merge. Please pull from 'upstream-linus' branch of

ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal

Hi all, Sorry for the repost. If I should be asking somewhere else please tell me where. I woke up a few days ago to find this on one of my machines. Below is hopefully the revelent output from dmesg and /var/log/messages. I have had this b4 but this is the first time I have been able to get any useful information from it. The machine usually locks and all I see is the assertion failure on

Hi all. I have two hosts with drbd: kmod-drbd83-8.3.8-1.el5.centos drbd83-8.3.8-1.el5.centos and kernel (CentOS 5.7): 2.6.18-308.4.1.el5 After a recent upgrade of kernel I have had two sitiuations when my ext3 filesystem on /dev/drbd0 became read-only. I've checked disks with smartctl -t long, they are ok. There are no messages with disks problems in /var/log/messages | dmesg. I've made

Hello, I am doing some testing on a PXA270 based processor (on a single board computer) which makes the processor vulnerable to bit flips. One such bit flips seems to have corrupted the file system. The debug port on the board (it is a single board computer) had the following message when i think the FS corruption occured : <7>init_special_inode: bogus i_mode (33061) init_special_inode:

(sort-of xposted from linux-kernel) Hi, I am wondering how to interpret this error message, which popped up on a 2.4.26 SMP x86 box two days ago: EXT2-fs: corrupt root inode, run e2fsck init_special_inode: bogus imode (37316) EXT2-fs: corrupt root inode, run e2fsck init_special_inode: bogus imode (37316) EXT2-fs: corrupt root inode, run e2fsck The problem is, the error message doesn't

The difference between kdev_t and dev_t in 2.4 is rather theoretical, no need to clutter up the source for it. Index: src/inode.c =================================================================== --- src/inode.c (revision 969) +++ src/inode.c (working copy) @@ -1877,11 +1872,8 @@ case OCFS_ATTRIB_FIFO: case OCFS_ATTRIB_SOCKET: { -#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)