On 2024-10-07 02:35, -pj via openSUSE Users wrote:
On 10-06-2024 07:58AM, Carlos E. R. wrote:
On 2024-10-06 06:01, -pj via openSUSE Users wrote:
On 10-05-2024 09:38PM, -pj via openSUSE Users wrote:
I sometimes use a machine at another location with an older 6.8 lts series kernel installed. While reading a bit on the F2FS filesystem.
https://wiki.archlinux.org/title/F2FS
Warning: The data contained on F2FS partitions can become unusable if the kernel version on the running machine is older than the kernel version used to create the partition. For example, this limitation can manifest if the F2FS partition was created on a mainline kernel provided by linux yet the system has a need to downgrade to an older series of kernels provided by linux-lts. See FS#69363. - This situation could arise using a F2FS usb between a Tumbleweed system and the latter? - Can you give anymore insight on F2FS at all? I understand there is plenty to read on my end about it. I went through the wiki page on it.
I have created on the USB flash drive a msdos partition with gparted. Then F2FS filesystem mkfs.f2fs -l mylabel -f -i -O extra_attr,inode_checksum,sb_checksum /dev/sdb
Unable to mount in Dolphin and receiving this error message > An error occurred while accessing 'mylabel', the system responded: The requested operation has failed: Error mounting /dev/sdb at /run/media/paul/mylabel: Filesystem type f2fs not configured in kernel.
Then I have read this comment > openSUSE doesn't support F2FS, unless you recompile the kernel manually, as far as I know. You might try exFAT with your phone and openSUSE instead. From here > https://www.reddit.com/r/openSUSE/comments/enlu5b/speaking_of_lack_of_f2fs_s...
Your insight please?
Do not use f2fs in production.
I gave the information as information to have, that there is an effort on making a better filesystem for sticks, but the unfortunate truth is that we can not use it.
Use it only for experimenting.
Yes, exFAT is the best practical filesystem to use on sticks and memory cards, but being a windows filesystem it does not support all Linux filesystem features. For that, the best alternative we have is ext4 without a journal.
Carlos, I found this link > https://wiki.archlinux.org/title/Dm-crypt/Device_encryption#Cryptsetup_usage and it helped alot with luks over ext4, in section |5.3.1 Encrypt an existing unencrypted file system|.
After powercycle it appears to be working, had to chown paul:paul WORLDWIDE-EXT4 to get permissions.🙂 It takes a bit of time to initially mount (or open) in Dolphin though. Appears to be working so far.
Appears to be typo under command in link > # umount /mnt It should be # umount /mnt /sdXY ?
No, the system knows that /mnt is /dev/sdXY. cat /etc/mtab
lsblk sdb 8:16 1 3.7G 0 disk └─luks-1bcdbc03-c669-4866-a4ad-f2b7984a4e1f 254:3 0 3.7G 0 crypt
How can I see if the EXT4 filesystem on /dev/sdb in luks-1bcdbc03-c669-4866-a4ad-f2b7984a4e1f has or does not have a journal? I followed > mke2fs -t ext4 -O ^has_journal -L WORLDWIDE-EXT4 /dev/sdXY < template you suggested.
First, you can no longer look at /dev/sdb, it contains a gibberish of data, it is encrypted. You have to look at the unencrypted filesystem, which is "/dev/mapper/cr_name" after opening it with "cryptsetup luksOpen /dev/sdb cr_name". Actually above it will be (I think): /dev/mapper/luks-1bcdbc03-c669-4866-a4ad-f2b7984a4e1f -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)