Messages in this thread | | | Date | Wed, 9 Dec 1998 23:30:21 +0100 (CET) | From | Junichi Saito <> | Subject | Re: EXT2-fs: unsupported inode size: 0 |
| |
On Wed, 9 Dec 1998, Rik van Riel wrote:
>On Wed, 9 Dec 1998, Junichi Saito wrote: > >> What can trigger these messages ? I have had ones so far only with this >> partition. How can I fix this ? >> >> EXT2-fs: unsupported inode size: 0 >> mount: wrong fs type, bad option, bad superblock on >> /dev/ide/hd/c0b0t0u0p7, or too many mounted file systems >> >> The kernel is 2.1.131 + 'device fs' + 'e2compr'. > ^^^^^^^ ^^^^^^^ > >I think it might be the combination of these two things >that have triggered the error. In 2.1.131 the VFS locking >scheme for some FS operations changed in a subtle way... ^^^^^^^^^^^^ So it's my fault, as e2compr patch is against 2.1.130. I will downgrade and see.
What I can't understand is why this happens only with this partition. There are four partitions. Almost all the directories on them are compressed. The only difference is that /dev/ide/hd/c0b0t0u0p7 is usually empty and that I use it only for compiling not for keeping files. I often run mke2fs on it after compiling. So running mke2fs on a partition containing compressed files may have something to do the error.
junichi
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |