cannot mount ext3 file system

[Adek336]

On on a SATA drive, fourth logical partition. The file /MyPartitionName, when stat-ed, is shown as a "weird file". hrev27358. Don't know what should I check for.

[Adek336]

Well, it doesn't happen anymore for a 2-3 weeks now.

[Adek336]

I mean, it doesn't happen in revisions which are more recent than 2-3 weeks old.

[Adek336]

I think it works for even more, say like 4-5 weeks (not 2-3). Anyway I have an old hrev27770 real hardware install with this problem.

[Adek336]

The previous comments are partially wrong. On my laptop, I still can't mount partitions even on hrev28242, /mypartition is "weird file".

On my desktop computer I can mount partitions for about 4-5 weeks now, however some older revisions also had problems - like in hrev27000 (however here it says /mypartition is "directory" not "weird file", but still doesn't work

/mypartition>ls
ls: cannot open directory .: Is a directory
}}})

[Adek336]

I have a computer with two ext3 partitions that mount in Haiku and one that doesn't. All three mount in linux. The two mountable partitions have st_mode == 0x41ed, and the value is read from the disk. The other partition, Haiku reads, I think, the wrong block and interprets "0" as it's st_mode, so it is later recognized as a weird file.

Using DiskProbe I found that the good partitions have hexadecimal "ed 41" in block 0x2018, one partition in offset 0x80, the other partition in offset 0x100 into the block. The wrong partition has hexadecimal "ed 41" in block 0x1678, offset 0x80.

For all 3 partitions, in the ext2 module, in Volume::Mount(), deeper in Inode::Inode(), deeper in ext2_get_vnode(), block_cache_get() is called with block == 0x403 I think.

[Adek336]

dumpe2fs /dev/hda9 : partition not mountable

[Adek336]

dumpe2fs /dev/sda6: mountable

[Adek336]

dumpe2fs /dev/sda1: mountable

[Adek336]

lenovo laptop: dumpe2fs /dev/sda10 : unmountable

[Adek336]

lenovo laptop: dumpe2fs /dev/sda8 : unmountable

[Adek336]

Among the unmountable, both small (~1Gb) and large (~100Gb) partitions appear.

All unmountable partitions have ext_attr feature, no mountable partition has.

All the unmountable partitions have been created recently with gparted under a recent Debian Linux. All the mountable partitions are older and have been created with various tools under Debian.

I think this may be reproducible with a partition made under a recent Debian and gparted.

[Adek336]

fixed it. My partitions had an inode size of 0x100 instead of the more common 0x80. Now I can mount the partition and see the names of the files. Unfortunately, the sizes and contents of the files are not read correctly - probably the same problem as below but in another place in the code.

Inodes.cpp:

-     fNode = inodes + volume->InodeBlockIndex(id);
+     fNode = (struct ext2_inode*)   (   ((char*)inodes)  +   volume->InodeBlockIndex(id)  *  volume->SuperBlock().inode_size   );

[Adek336]

Now that it mounts and file names can be read, filesizes not, it is easy to get a page fault in kernel space so pointer arithmetic needs more checking.

[Adek336]

Volume.cpp

300   -     fInodesPerBlock = fBlockSize / sizeof(ext2_inode); 
300   +     fInodesPerBlock = fBlockSize / SuperBlock().inode_size; 

this seems to fix a bit, but when reading some files I get trash.

[axeld]

Thanks for looking into this! I've applied similar changes in hrev28536 (your version was not endian-safe, BTW).

Let's keep this ticket open until reading files is working as well.

[Adek336]

I though reading didn't work when MediaPlayer couldn't play movies but I've checked that after all reading works always well.