Ext2 driver causing mount to fail in linux with Ext4 formatted drive

[shaka]

I formatted a known working thumbdrive to ext4 in linux, copied some files and folders to the drive then unmounted. Mounted read/write in Haiku x64 hrev57394 and did various file operations- copied, deleted executed files etc.. Then unmounted drive.

When putting drive back in linux box it was unable to mount with a message about possible file corruption.

I have attached linux syslog output and a picture of error message

[waddlesplash]

[    0.000000] JBD2: journal checksum error
[    0.000000] EXT4-fs (sdc1): error loading journal

Well, that's not too helpful, but I guess these errors are supposed to be pretty rare.

[korli]

what does e2fsck say when checking the drive?

[shaka]

sudo e2fsck -v /dev/sdc1

e2fsck 1.47.0 (5-Feb-2023)

Journal superblock is corrupt. Fix<y>? yes

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Unattached inode 36

Connect to /lost+found<y>? yes

Inode 36 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 42

Connect to /lost+found<y>? yes

Inode 42 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 45 Connect to /lost+found<y>? yes

Inode 45 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 46 Connect to /lost+found<y>? yes

Inode 46 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 60 Connect to /lost+found ('a' enables 'yes' to all) <y>? yes

Inode 60 ref count is 2, should be 1. Fix ('a' enables 'yes' to all) <y>? yes

Unattached inode 65 Connect to /lost+found ('a' enables 'yes' to all) <y>? yes

Inode 65 ref count is 2, should be 1. Fix ('a' enables 'yes' to all) <y>? yes

Unattached inode 73 Connect to /lost+found<y>? yes

Inode 73 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 80 Connect to /lost+found<y>? yes

Inode 80 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 93 Connect to /lost+found<y>? yes

Inode 93 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 96 Connect to /lost+found<y>? yes

Inode 96 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 102 Connect to /lost+found<y>? yes

Inode 102 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 103 Connect to /lost+found<y>? yes

Inode 103 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 128 Connect to /lost+found<y>? yes

Inode 128 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 132 Connect to /lost+found<y>? yes

Inode 132 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 170 Connect to /lost+found<y>? yes

Inode 170 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 182 Connect to /lost+found<y>? yes

Inode 182 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 183 Connect to /lost+found<y>? yes

Inode 183 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 186 Connect to /lost+found<y>? yes

Inode 186 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 193 Connect to /lost+found<y>? yes

Inode 193 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 199 Connect to /lost+found<y>? yes

Inode 199 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 211 Connect to /lost+found<y>? yes

Inode 211 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 213 Connect to /lost+found<y>? yes

Inode 213 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 231 Connect to /lost+found<y>? yes

Inode 231 ref count is 2, should be 1. Fix<y>? yes

Unattached inode 254 Connect to /lost+found<y>? yes

Inode 254 ref count is 2, should be 1. Fix<y>? yes

Pass 5: Checking group summary information

1gExt4Drv: * FILE SYSTEM WAS MODIFIED *

52 inodes used (0.08%, out of 61440)

1 non-contiguous file (1.9%) 0 non-contiguous directories (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 44

10933 blocks used (4.45%, out of 245504)

0 bad blocks 1 large file

40 regular files

3 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets

19 files

*NOTE After running e2fsck drive worked fine in linux again, but same problems after using in Haiku again.

[shaka]

Also, is it correct that 'root' retains ownership of files/folders copied from Haiku drive to ext4 drive? If I copy the same file/folder via ftp from Haiku to Linux, the current user has ownership on the target side.

[korli]

Please provide a syslog.