System does not recognize partitions formatted with mkfs.ext4 command.

[khallebal]

It's easy to verify, create a partition and format it using the mkfs.ext4 command, the partition is then unmountable and DriveSetup reports it just as "native linux", now format it with the mkfs -t ext4 again and it works as expected.

[waddlesplash]

Please retest after hrev53401.

[khallebal]

Now it shows up as an ext2 parttion in DriveSetup but can't be mounted, i get a "Bad data" error msg either from terminal or tracker, no other messages.

[waddlesplash]

Please post the syslog after getting said error message.

[waddlesplash]

ext2:[0m Inode::UpdateNodeFromDisk(1060): verification failed
ext2:[0m get_vnode: InitCheck() failed. Error: Bad data
ext2:[0m could not create root node: get_vnode() failed!
ext2:[0m Failed mounting the volume. Error: Bad data

[khallebal]

Sorry for the late response,i don't have much time for haiku these last few months

[korli]

Proposed change: ​https://review.haiku-os.org/c/haiku/+/4118

[waddlesplash]

Please retest on a recent nightly.

[khallebal]

As of hrev55621 it does mount now, thanks for the fix guys, although unlike the ext3 partitions i have this one has no read/write support, it mounts in read-only mode even if you choose read/write and it shows up as an ext2 filesystem in DriveSetup.

[khallebal]

Oh well, now it mounts in read/write again after cleaning some of the cache in /config/cache dir and removing the RosterSettings file in /config/settings/system/registrar, so i guess this ticket can be closed now.

[waddlesplash]

It probably auto-mounts read-only because that is what you previously selected, as with any drive. Unmounting and then re-mounting read/write is the more better solution, instead of deleting configuration files.

[khallebal]

It probably auto-mounts read-only because that is what you previously selected,

I'm not sure what you mean by "auto-mounts", it never "auto-mounted", i mounted it manually every time choosing read/write mode, anyways, this has nothing to do with the ext4 fs though, i've seen this behavior with other apps/operations where new settings do not take effect until i remove one or both of those mentioned above, i'm not sure how file a ticket about this issue.

[diver]

Replying to khallebal:

Oh well, now it mounts in read/write again after cleaning some of the cache in /config/cache dir and removing the RosterSettings file in /config/settings/system/registrar, so i guess this ticket can be closed now.

For the record: the only built-in applications that use cache dir are HaikuDepot, Mail, Package Kit, Repositories and notification_server. Cleaning that dir is very unlikely can cause anything related to mounting. RosterSettings in ~/config/settings/system/registrar also can't be related to that.

Mount settings are stored in ~/config/settings/mount_server and can be read with message command.