-
tytso pushed 3 commit(s) to refs/heads/maint in the e2fsprogs Git repository of the Ext2 Filesystems Utilities project.
2009-11-17 02:59:52 UTC in Ext2 Filesystems Utilities
-
tytso pushed 16 commit(s) to refs/heads/master in the e2fsprogs Git repository of the Ext2 Filesystems Utilities project.
2009-11-17 02:59:52 UTC in Ext2 Filesystems Utilities
-
tytso pushed 9 commit(s) to refs/heads/next in the e2fsprogs Git repository of the Ext2 Filesystems Utilities project.
2009-11-17 02:59:52 UTC in Ext2 Filesystems Utilities
-
Fixed in commit b71e0183 on the e2fsprogs maint branch.
2009-11-17 02:58:39 UTC in Ext2 Filesystems Utilities
-
tytso committed revision 30 to the Ext2 Filesystems Utilities SVN repository, changing 1 files.
2009-11-16 03:13:06 UTC in Ext2 Filesystems Utilities
-
tytso pushed 4 commit(s) to refs/heads/maint in the e2fsprogs Git repository of the Ext2 Filesystems Utilities project.
2009-11-13 04:10:50 UTC in Ext2 Filesystems Utilities
-
Well, blocks are clearly getting written to the wrong location on disk, so that tends to indicate either some kind of hardware problem (or more likely in your case) some kind of kernel bug that is causing blocks to be written to the wrong location. It's certainly not normal and I haven't seen anyone else reporting problems like this with ext2/ext3.
2009-10-06 14:35:20 UTC in Ext2 Filesystems Utilities
-
Well, if you look at those numbers, and convert them into ASCII you get: " LOAD_DAT_ERV_ERROR: %s". So it's ascii text which is getting written into an indirect block, first of inode #2042 and then of inode #1002. do you have multiple partitions on that device (and if so, have you checked to make sure the partition table isn't corrupt), or some other OS that might be wrtiting...
2009-10-05 14:19:06 UTC in Ext2 Filesystems Utilities
-
This is normal but since you probably won't be the first person to be confused by this, here's an attached patch which clarifies the message to something like this:
Illegal indirect block (2324697516) in inode 176. CLEARED.
2009-10-04 22:13:19 UTC in Ext2 Filesystems Utilities
-
Well, your filesystem is corrupted, but it's not a really horrible thing. It's likely that the problem was merely caused by a corrupted double indirect block. Block #-1 simply means a corrupted indirect block.
2009-10-03 16:33:08 UTC in Ext2 Filesystems Utilities
