[SOLVED] 4.18.0-1-ARCH aarch64 - no btrfs ?

This forum is for topics dealing with problems with software specifically in the AArch64 repo.

[SOLVED] 4.18.0-1-ARCH aarch64 - no btrfs ?

Postby ufo6000 » Sat Sep 01, 2018 6:03 pm

At first, a big thanks for providing the aarch64 kernel for the rp3+

Did I see right, the kernel does not support btrfs ?
$this->bbcode_second_pass_code('', '
[root@alarm ~]# egrep -i "btrfs|ext" /proc/filesystems
ext3
ext2
ext4
')
So I can't put the root filesystem on a BTRFS partition ? Or is there a workaround ?

On an armv7l there is btrfs included.

Thanks very much!
Last edited by ufo6000 on Sun Sep 02, 2018 10:09 am, edited 1 time in total.
ufo6000
 
Posts: 117
Joined: Fri Jan 22, 2016 7:54 pm

Re: 4.18.0-1-ARCH aarch64 - no btrfs ?

Postby TheSaint » Sun Sep 02, 2018 4:43 am

Haven't you consider to make your own kernel ?
The wiki might guide you to make one ;)
TheSaint
 
Posts: 346
Joined: Mon Jul 23, 2018 7:57 am

Re: 4.18.0-1-ARCH aarch64 - no btrfs ?

Postby ufo6000 » Sun Sep 02, 2018 10:08 am

ah - no need anymore:
$this->bbcode_second_pass_code('', '
[root@p6 ~]# uname -a
Linux p6 4.18.5-1-ARCH #1 SMP Fri Aug 24 18:33:45 MDT 2018 aarch64 GNU/Linux
[root@p6 ~]# egrep -i "btrfs|ext" /proc/filesystems
ext3
ext2
ext4
btrfs
')
Updating the boot.txt with rootfstype=btrfs rootflags=subvol=@ work fine. The root filesystem is now BTRFS :-)
ufo6000
 
Posts: 117
Joined: Fri Jan 22, 2016 7:54 pm

Re: [SOLVED] 4.18.0-1-ARCH aarch64 - no btrfs ?

Postby summers » Sun Sep 02, 2018 12:56 pm

btrfs is usually loaded as a module, so it only shows up as a filesystem when the module is loaded.

So it should work as long as you make your your initrd includes btrfs.

Me I've always had root as ext4 and only /home as btrfs ...
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm

Re: [SOLVED] 4.18.0-1-ARCH aarch64 - no btrfs ?

Postby ufo6000 » Mon Sep 03, 2018 2:37 pm

In my 2nd try I added

$this->bbcode_second_pass_code('', '
# /etc/mkinitcpio.conf
MODULES=(btrfs)
')
to be sure, also I updated the kernel. So I blamed only the kernel update to be resposible :D

Thanks for the explanation!
ufo6000
 
Posts: 117
Joined: Fri Jan 22, 2016 7:54 pm


Return to ARMv8

Who is online

Users browsing this forum: No registered users and 5 guests