We have moved to a new Sailfish OS Forum. Please start new discussions there.
3

[solved] ext4 file system compatibility [not relevant]

asked 2019-12-17 22:18:13 +0300

Leon gravatar image

updated 2019-12-19 03:21:12 +0300

Hi, I have formatted (ext4) an USB memory stick on my workstation (CentOS8, mke2fs 1.44.3).

When attaching this device via an USB OTG adapter to a XA2 phone (SFOS 3.2.0.12). I can mounting the encrypted partition via system preferences. But it seems that the UI has glitches, timeouts, responsiveness, file manager not usable etc. At this point there appears also a warning text while at the terminal I see the mounted filesystem (df -h) and copied manually (cp) some files onto it.

Comparing two device, each one formatted on the phone and workstation respectively, I see these main differences (tune2fs -l):

  • SFOS: Filesystem features: ...... 64bit ....
  • SFOS: Filesystem flags: unsigned_directory_hash
  • SFOS: Default mount options: user_xattr acl
  • CENTOS8: Filesystem flags: signed_directory_hash

I added the user_xattr,acl options to the device of the workstation but the file manager on SFOS is still not usable. Also, after using the device at the phone, when plugged to the workstation back, following appears in the logs:

  kernel: EXT4-fs (dm-4): recovery complete

SFOS has mke2fs 1.45.0 and should be backward compatible. It feels still sluggished. Does this experiences have to do with the above Filesystem flags: signed_directory_hash? Any hints?

edit retag flag offensive reopen delete

The question has been closed for the following reason "question is not relevant or outdated" by olf
close date 2019-12-19 17:38:48.651385

Comments

1

Based on the evidence of my own answer I did some tests and EVERYTHING works as expected now! Summarized: Created a encrypted usb device on the workstation (CentOS8) based on LUKS/EXT4 and used it for data transfers between SFOS and vice versa.

Leon ( 2019-12-19 03:17:00 +0300 )edit

2 Answers

Sort by » oldest newest most voted
7

answered 2019-12-18 04:38:53 +0300

Leon gravatar image

I found the culprit now - its the underlying encryption layer. LUKS (at least not on this platform [SFOS 3.2.0]) does not support or handle keysizes of 512 bits. Some tests with 256 bit encryption seems to work so far. Its also the default used by SFOS. Albeit /proc/crypto seems to state something different.

edit flag offensive delete publish link more

Comments

@Leon, you wrote in your OP,

Hi, I have formatted (ext4) an USB memory stick on my workstation (CentOS8, mke2fs 1.44.3).

As you created no "underlying encryption" this way, so where does that "encryption layer" on your USB-stick suddenly come from?

Anyway, this underlines my answer even more:
Always format, partition and encrypt USB-attached storage and SD-cards with SailfishOS!

olf ( 2019-12-18 20:34:56 +0300 )edit

If readed carefully the encryption layer is mentioned but not very explicitly.

Leon ( 2019-12-19 03:15:57 +0300 )edit
0

answered 2019-12-18 02:50:05 +0300

olf gravatar image

Create filesystems on USB-attached storage and SD-cards with SailfishOS.

edit flag offensive delete publish link more

Question tools

Follow
2 followers

Stats

Asked: 2019-12-17 22:18:13 +0300

Seen: 537 times

Last updated: Dec 19 '19