Package Details: linux-bcachefs-git v5.18.3.arch1.r1092118.00e321143014-1

Git Clone URL: (read-only, click to copy)
Package Base: linux-bcachefs-git
Description: The Linux kernel and modules ~ featuring Kent Overstreet's bcachefs filesystem
Upstream URL:
Licenses: GPL2
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: Chiruno
Maintainer: QuartzDragon
Last Packager: QuartzDragon
Votes: 11
Popularity: 0.000819
First Submitted: 2018-01-13 15:37 (UTC)
Last Updated: 2022-06-17 10:56 (UTC)

Pinned Comments

QuartzDragon commented on 2019-06-11 15:15 (UTC) (edited on 2019-06-11 15:17 (UTC) by QuartzDragon)

If there are bugs related to the PKGBUILD or config, report here.

Otherwise, please report here:

Latest Comments

sonicrules1234 commented on 2022-06-02 13:56 (UTC) (edited on 2022-06-02 20:03 (UTC) by sonicrules1234)

This needs to be updated to use the 5.18.x arch kernel since bcachefs master has moved to use kernel 5.18.x

columna1 commented on 2022-04-28 23:35 (UTC)

@RX14 the bcachefs github upgraded to linux 5.17, I found editing the PKGBUILD to clone linux 5.17 before cloning and merging bcachefs-linux instead of 5.16 works fine.

RX14 commented on 2022-04-25 19:00 (UTC)

Plenty of merge conflicts :(

QuartzDragon commented on 2022-03-19 05:52 (UTC)


Cheers ~ I've fixed it now. :)

Gotta remember to update the sha512sums before pushing...

benjumanji commented on 2022-03-18 17:20 (UTC)

Current package sums are broken for me. This fixed it:

diff --git a/PKGBUILD b/PKGBUILD
index 4c40381..cf1ba3c 100755
@@ -117,7 +117,7 @@ sha512sums=('SKIP'
-            '90f8c978bde10c80770431c3d8686b6f8c10e2c9645dddb9e8772312eb0cb1129bcfc6af5b86477c5616b723da25f629859092b1af178da7bd71c7b89e1de97d')
+            'd154f68d39cbe0dc25f9a721e987b7b8fbbebe5d08ed1a50c4ef64174814caf13fc8c4cc64d7d057e3d157d72ab1e88543cab397bff47bcca71bc916ec4da189')

 export KBUILD_BUILD_HOST=archlinux
 export KBUILD_BUILD_USER=$pkgbase

mentaluproar commented on 2021-08-05 05:01 (UTC)

Recent changes allow this to build on aarch64. Please update this for those of us on ARM devices. :)

QuartzDragon commented on 2021-07-25 20:17 (UTC)


Cannot reproduce.

Please report upstream.

hwaiting commented on 2021-07-25 12:43 (UTC)

I'm getting the following error when building with makepkg -sc

make[4]: *** No rule to make target 'libbpf_util.h', needed by '/home/gamer/Source/linux-bcachefs-git/src/linux-bcachefs/tools/bpf/resolve_btfids/libbpf/staticobjs/xsk.o'.  Stop.
make[3]: *** [Makefile:158: /home/gamer/Source/linux-bcachefs-git/src/linux-bcachefs/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf-in.o] Error 2
make[2]: *** [Makefile:44: /home/gamer/Source/linux-bcachefs-git/src/linux-bcachefs/tools/bpf/resolve_btfids//libbpf/libbpf.a] Error 2
make[1]: *** [Makefile:72: bpf/resolve_btfids] Error 2
make: *** [Makefile:1974: tools/bpf/resolve_btfids] Error 2

PythonNut commented on 2021-07-08 05:09 (UTC)

Looks like the latest changes have introduced a merge conflict?

clonejo commented on 2021-07-03 20:40 (UTC)

@QuartzDragon: I thought yay had pulled, but it looks like it didn't. For some reason it did not detect the package update and i just forced a rebuild. Sorry for the trouble. With a pull, and a clean rebuild, it builds fine now. Thanks for the help!

I did remove the checksum check for config though, since there was a conflict. It is part of this AUR repo, so i don't see why it needs to be checked.

QuartzDragon commented on 2021-07-03 04:37 (UTC)


Actually... maybe I didn't forget...

Did you pull the repo for the latest updates?

What are you terminal output results?

QuartzDragon commented on 2021-07-03 04:35 (UTC)


Whoops ~ I'd forgot to push the URL changes after updating them.

Please try again. :)

clonejo commented on 2021-07-02 23:06 (UTC)

Is gone? The domain does not resolve anymore.

The repo the linux package uses is on Github:

QuartzDragon commented on 2021-05-07 16:08 (UTC)


Not with this package, at least.

You'll be better off asking upstream about this.

RealGecko commented on 2021-05-07 08:41 (UTC)

Is there a way to install bcachefs as kernel module? DKMS maybe?

nicman23 commented on 2021-03-30 17:11 (UTC)

if anyone cares, i will support 5.10 lts zen at linux-bcachefs-510-zen and i ll have a kpatch script available in the next week for that.

QuartzDragon commented on 2021-03-27 05:40 (UTC)


Fixed. :)

Hamled commented on 2021-03-26 22:57 (UTC) (edited on 2021-03-26 22:57 (UTC) by Hamled)

Patch file got renamed again :P


Hamled commented on 2021-03-12 22:30 (UTC)

Looks like the Graysky GCC patch file was renamed as of this commit:

So the PKGBUILD should reference "more-uarches-for-gcc-v10-and-kernel-5.8+.patch" instead of "enable_additional_cpu_optimizations_for_gcc_v10.1+_kernel_v5.8+".

QuartzDragon commented on 2020-12-17 01:32 (UTC)


Hmmm. Thanks. Will do that.

bobpaul commented on 2020-12-17 01:17 (UTC) (edited on 2020-12-17 16:04 (UTC) by bobpaul)

~~make defconfig should create a default .config and then you can compare it with the config you want to use and it probably won't be very fun. ~~ (Edit: Actually, I don't think that's a thing. Things that aren't defined as Y, N, or M in the config are just left as "undefined". But the suggestion below is good, and it looks like linux-git and other linux packages on aur do that:)

But in this case, it looks like the config you're providing has a lot of commented lines. You could simply delete all comments and blank lines. Lines like # CONFIG_KERNEL_GZIP is not set represent a feature that's available in the code base, but not configured. Removing all empty and commented lines reduces the file to 205K. Something like grep -v '^#' big_config | grep -v '^$' > config

Also, for a single file it's somewhat preferable to avoid tar and use gzip directly to produce a config.gz, since tools like vim/emacs, zdiff, zgrep, zless, zcat, etc can directly read a gzipped text file. That's why you never see *.tar.gz archives in /var/log/

QuartzDragon commented on 2020-12-17 00:35 (UTC)


So I suppose also not ideal, but another option would be to remove some kernel config options that match the default config.

Don't have the technical knowledge on how to do that.

I'm not sure which options are default config, considering that the Arch devs have many non-default kernel options.

bobpaul commented on 2020-12-16 23:55 (UTC)

So I suppose also not ideal, but another option would be to remove some kernel config options that match the default config.

QuartzDragon commented on 2020-12-16 23:37 (UTC)

Compressed the config file, so it fits within the 250KiB blob limit... :|

QuartzDragon commented on 2020-12-16 22:51 (UTC)

Currently cannot update due to

QuartzDragon commented on 2020-03-23 00:25 (UTC)


Please report upstream ~ I'm unable to do anything about this.

bobpaul commented on 2020-03-22 23:58 (UTC)

Has anyone tried building virtualbox-host-dkms?

I get this:

==> dkms install vboxhost/6.1.4_OSE -k 5.3.18-1-bcachefs-git-196109-g3d16f5d33e21
Error! Bad return status for module build on kernel: 5.3.18-1-bcachefs-git-196109-g3d16f5d33e21 (x86_64)
Consult /var/lib/dkms/vboxhost/6.1.4_OSE/build/make.log for more information.
[bobpaul@celestra ~]$ cat /var/lib/dkms/vboxhost/6.1.4_OSE/build/make.log
DKMS make.log for vboxhost-6.1.4_OSE for kernel 5.3.18-1-bcachefs-git-196109-g3d16f5d33e21 (x86_64)
Sun 22 Mar 2020 06:51:12 PM CDT
make: Entering directory '/usr/lib/modules/5.3.18-1-bcachefs-git-196109-g3d16f5d33e21/build'
  CC [M]  /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxnetadp/VBoxNetAdp.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxnetflt/linux/VBoxNetFlt-linux.o
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./scripts/gcc-plugins/
make[2]: *** [scripts/ /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.o] Error 1
make[2]: *** Waiting for unfinished jobs....
  CC [M]  /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxdrv/linux/SUPDrv-linux.o
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./scripts/gcc-plugins/
make[2]: *** [scripts/ /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxnetadp/VBoxNetAdp.o] Error 1
make[1]: *** [scripts/ /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxnetadp] Error 2
make[1]: *** Waiting for unfinished jobs....
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./scripts/gcc-plugins/
make[2]: *** [scripts/ /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxnetflt/linux/VBoxNetFlt-linux.o] Error 1
make[1]: *** [scripts/ /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxnetflt] Error 2
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./scripts/gcc-plugins/
make[2]: *** [scripts/ /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[2]: *** Waiting for unfinished jobs....
  CC [M]  /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxdrv/SUPDrvSem.o
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./scripts/gcc-plugins/
make[2]: *** [scripts/ /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxdrv/SUPDrv.o] Error 1
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./scripts/gcc-plugins/
make[2]: *** [scripts/ /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxdrv/SUPDrvGip.o] Error 1
cc1: error: incompatible gcc/plugin versions
cc1: error: fail to initialize plugin ./scripts/gcc-plugins/
make[2]: *** [scripts/ /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxdrv/SUPDrvSem.o] Error 1
make[1]: *** [scripts/ /var/lib/dkms/vboxhost/6.1.4_OSE/build/vboxdrv] Error 2
make: *** [Makefile:1626: _module_/var/lib/dkms/vboxhost/6.1.4_OSE/build] Error 2
make: Leaving directory '/usr/lib/modules/5.3.18-1-bcachefs-git-196109-g3d16f5d33e21/build'

tscs37 commented on 2019-12-10 21:29 (UTC)

The latest kernel seems to be able to build the latest kernel, atleast in my configuration, so it seems the issue with bcachefs root has been fixed.

nicman23 commented on 2019-12-10 17:05 (UTC)

guys can someone confirm that makepkg works with bcachefs root so i can close the issue in github

QuartzDragon commented on 2019-12-07 17:22 (UTC)


I'd missed added the updated config file to my update. :/

bobpaul commented on 2019-12-07 17:07 (UTC) (edited on 2019-12-07 17:08 (UTC) by bobpaul)

I got this today:

:: Downloading the latest sources for a devel package linux-bcachefs-git...
:: error: failed to retrieve latest dev sources:
==> Making package: linux-bcachefs-git v5.3.15.arch1.r859832.ac127f6e3fa5-1 (Sat 07 Dec 2019 10:50:43 AM CST)
==> WARNING: Skipping dependency checks.
==> Retrieving sources...
  -> Cloning bcachefs git repo...
Cloning into bare repository '/home/bobpaul/.cache/pikaur/build/linux-bcachefs-git/bcachefs'...
  -> Cloning kernel_gcc_patch git repo...
Cloning into bare repository '/home/bobpaul/.cache/pikaur/build/linux-bcachefs-git/kernel_gcc_patch'...
  -> Found config
  -> Found d938db454691d69590eb081db22c507c9ebca5f8.patch
  -> Found 4932fe6b8e63b92f8252591b5381423c01bac552.patch
==> Validating source files with sha512sums...
    bcachefs ... Skipped
    kernel_gcc_patch ... Skipped
    config ... FAILED
    d938db454691d69590eb081db22c507c9ebca5f8.patch ... Passed
    4932fe6b8e63b92f8252591b5381423c01bac552.patch ... Passed
==> ERROR: One or more files did not pass the validity check!

I had to use makepkg -g to generate new hashes. It's still building.

nicman23 commented on 2019-11-23 17:01 (UTC)

@QuartzDragon updated everything to work with the new changes - just without docs

running 5.4.0-rc8-1-mainline-bcachefs-00303-ga29c11e13cf5-dirty atm, everything is as expected

QuartzDragon commented on 2019-11-21 05:17 (UTC)

Ah, no, that was an error somehow caused by my previous fixing of EXTRAVERSION. Worked for 5.2, but is broken and also obsolete for 5.3.

So, in a way, yes, fixed by upstream ages ago, probably.

bcachefs had been stuck on 5.2 for ages.

tscs37 commented on 2019-11-21 05:03 (UTC)

I've tested it a few times but my first issue continues while the second issue has gone away with the newest PKGBUILD. So I guess upstream fixed itself?

QuartzDragon commented on 2019-11-21 03:34 (UTC)


Yes, you have. :P

I maintain my package by following all of the changes at

60-linux.hook, 90-linux.hook, linux.install, linux.preset are all obsolete now, upstream. Instead, Pacman now has builtin hooks that replace all that.

I've also updated your PKGBUILD to match my own:

nicman23 commented on 2019-11-20 17:05 (UTC)

changes? what changes o.O ? i have been living under a rock in the past weeks

QuartzDragon commented on 2019-11-20 12:09 (UTC)


Can you sync your package with mine, where appropriate, to reflect the latest Arch kernel package changes? Some pretty significant ones recently that I notice you haven't seem to have been aware of.

nicman23 commented on 2019-11-20 07:21 (UTC)

hi, 2 things:

QuartzDragon commented on 2019-11-20 06:58 (UTC)

Ah, I see... my fixing of EXTRAVERSION, which was working for 5.2, isn't needed anymore.

QuartzDragon commented on 2019-11-20 06:56 (UTC)

Weird... really weird.

I could reproduce it multiple times, but after I made that comment... suddenly, I've not been able to reproduce it.

Please try building it again now.

QuartzDragon commented on 2019-11-20 06:44 (UTC)


Thanks for reporting. :)

Cannot reproduce your first issue, but can reproduce the second.

Please report a bug for bcachefs, while I figure out a stopgap fix.

tscs37 commented on 2019-11-20 06:02 (UTC) (edited on 2019-11-20 06:09 (UTC) by tscs37)

When building from a clean copy of the repo, I get an error that a fast forward could not be performed. It occurs when building on bcachefs but also on xfs/ext4 and on cleanbuilds or using a (previously failed with this error) repository. I'm using yay to run the build.

Adding the "--no-ff" Option to line 125 and 135 fixes this.

After that I get a build failure from sphinx as seen in the second snippet.

==> Starting prepare()...
  -> Setting version...
  -> Adding patches from Linux upstream kernel repository...
remote: Enumerating objects: 10276, done.
remote: Counting objects: 100% (10276/10276), done.
remote: Compressing objects: 100% (3296/3296), done.
remote: Total 10276 (delta 7095), reused 9673 (delta 6956)
Receiving objects: 100% (10276/10276), 13.17 MiB | 13.03 MiB/s, done.
Resolving deltas: 100% (7095/7095), completed with 732 local objects.
From <>
 * tag                         v5.3.11    -> FETCH_HEAD
fatal: Not possible to fast-forward, aborting.
==> ERROR: A failure occurred in prepare().
Error making: linux-bcachefs-git (linux-bcachefs-git linux-bcachefs-git-docs linux-bcachefs-git-headers)

  CC      arch/x86/events/probe.o
sphinx-build: error: argument -a: ignored explicit argument 'rch1'
  CC      arch/x86/events/amd/core.o
make[1]: *** [Documentation/Makefile:81: htmldocs] Fehler 2
make: *** [Makefile:1579: htmldocs] Error 2
make: *** Waiting for unfinished jobs....

tscs37 commented on 2019-10-08 18:24 (UTC)

@nicman23 yeah that was pretty much the issue

creating a ext4 /tmp and patching makepkg fixes the issue afaict.

nicman23 commented on 2019-10-08 12:44 (UTC) (edited on 2019-10-08 12:45 (UTC) by nicman23)


this is a known issue when packaging anything on a bcachefs root. either compile the package on some other fs (tmpfs is also a choice) or patch your makepkg like so

--- /usr/bin/makepkg    2019-03-01 03:41:56.000000000 +0200
+++ /home/nikos/.local/bin/makepkg      2019-07-21 11:47:22.353595608 +0300
@@ -1465,10 +1465,10 @@

 if [[ $BUILDDIR -ef "$startdir" ]]; then
-       pkgdirbase="$BUILDDIR/pkg"
+       pkgdirbase="/tmp/$BUILDDIR/pkg"
-       pkgdirbase="$BUILDDIR/$pkgbase/pkg"
+       pkgdirbase="/tmp/$BUILDDIR/$pkgbase/pkg"


QuartzDragon commented on 2019-10-08 08:28 (UTC)


Hmmm. Cannot reproduce, sorry. :/

How are you building this? What PKGBUILD settings are you using?

tscs37 commented on 2019-10-08 04:32 (UTC)

I'm getting a bunch of errors from mkinitcpio after installing the latest version of this kernel;

depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/btrfs.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/trusted.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/scsi_mod.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/sd_mod.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/sr_mod.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/cxgb4.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/usb-storage.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/mmc_block.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/virtio.ko.xz: Exec format error

QuartzDragon commented on 2019-10-07 20:33 (UTC)

I've changed the package version scheme to better reflect the commit of the build, so if you need to report a bug upstream, you can see what commit you're using at a glance.

QuartzDragon commented on 2019-07-24 06:22 (UTC)

I think I might cautiously wait until Kent fixes up bcachefs proper.

I guess I don't quite trust the conflict handler to do a proper fixup that won't cause issues...

nicman23 commented on 2019-07-21 08:02 (UTC) (edited on 2019-07-21 20:39 (UTC) by nicman23)

diff to the pkgbuild, it includes:

  • automatic latest x.x.y detection ie if you set _srcver_tag=5.1 then it goes to 5.1.19 + it correctly sets pkgver

  • automatic conflict handler (the below code did not work because git merge is silly with tags)

  • removal of bluetooth patch - it is included iirc E: it is

  • having the upstream git repo fetched in source=() from makepkg and added as a local filesystem remote

  • renaming prepare to actual_prepare because makepkg ordering is silly

compiling right now will update you within the hour for any possible issues but there ought to be none

E: running it since a couple of hours ago, nothing wrong to report

QuartzDragon commented on 2019-07-20 09:53 (UTC)

Implemented the first suggestion.

Second suggestion is borked:

merge: upstream_stable/v5.1.18 - not something we can merge
fatal: '--ours/--theirs' cannot be used with switching branches

nicman23 commented on 2019-07-20 08:16 (UTC) (edited on 2019-07-20 08:50 (UTC) by nicman23)

(echo "$_subarch"; yes) | make oldconfig

is better

also for simple conflicts, such as the one that is blocking 5.1.17, remove the git pull and add this

git fetch --tags upstream_stable
if ! git merge upstream_stable/v${_srcver_tag}
  then if ! git diff --name-only --diff-filter=U | xargs git checkout --theirs
    then git diff --name-only --diff-filter=U |
    while read line
    do sleep 0.1; if ! git checkout --theirs $line
      then sleep 0.1; git rm $line

QuartzDragon commented on 2019-07-04 23:27 (UTC)

Stuck at 5.1.15 for now.

5.1.16 produces an auto-merge conflict.

nicman23 commented on 2019-07-04 15:29 (UTC)

5.1 is a go it seams

QuartzDragon commented on 2019-06-13 15:35 (UTC)

Reverted back to 5.0.21 for now.

QuartzDragon commented on 2019-06-13 15:31 (UTC)

Will revert.

nicman23 commented on 2019-06-13 14:23 (UTC)

do not update, it kernel panics as per the latest issue in the project's github

QuartzDragon commented on 2019-06-11 15:15 (UTC) (edited on 2019-06-11 15:17 (UTC) by QuartzDragon)

If there are bugs related to the PKGBUILD or config, report here.

Otherwise, please report here:

QuartzDragon commented on 2019-05-13 15:28 (UTC)

Done. :)

nicman23 commented on 2019-05-13 15:03 (UTC) (edited on 2019-05-13 15:04 (UTC) by nicman23)

please add || true on line 109

and the other remote add

QuartzDragon commented on 2019-05-07 19:10 (UTC)

Should be fixed now. :)

Forgot to update it. :P

benjumanji commented on 2019-05-07 18:59 (UTC)

bad checksum on the config? Is anyone else seeing that?

QuartzDragon commented on 2019-04-07 15:46 (UTC) (edited on 2019-04-07 15:47 (UTC) by QuartzDragon)


This commit may have fixed that:

I had used backticks without realizing that Bash will execute this blindly, as a command, even when encased in normal quotes.

tscs37 commented on 2019-04-07 14:52 (UTC)

@QuartzDragon the latest commit fixed the issue and the package builds headless again.

QuartzDragon commented on 2019-04-06 10:06 (UTC)


I've implemented your patch. Thanks. :)

Can't help you with the headless build issues, sorry. :/

tscs37 commented on 2019-04-06 08:44 (UTC) (edited on 2019-04-06 08:44 (UTC) by tscs37)

The current PKGBUILD doesn't work when building headlessly, I made a small patch to prevent git revert from opening vi when running, the commit message here doesn't matter anyway

I'm however still having an issue with the build; after the message "Prepared linux-bcachefs-git version 5.0.6-arch1-1-bcachefs-git-151713-g2ee4babf9fa8-dirty", I get the error "rm: cannot remove '/logdest/logpipe.ink8OBNo': No such file or directory" I'm gonna look into that and see if I can fix that too...

diff --git a/PKGBUILD b/PKGBUILD
index [`55d15f1`]( 100755
@@ -99,7 +99,7 @@ prepare() {
     git pull arch_stable v$_srcver_arch

     msg2 "Reverting 'block: remove the unused bio_iov_iter_get_pages export' which causes `make modules` to fail"
-    git revert 0374e1132217711bc2e920cde877dd7fc3dbd2d9
+    git revert --no-edit 0374e1132217711bc2e920cde877dd7fc3dbd2d9

     # <>
     msg2 "Patching to enabled additional gcc CPU optimizatons..."

QuartzDragon commented on 2019-04-06 04:55 (UTC)

5.0.6 update at last. :)

QuartzDragon commented on 2019-04-04 09:00 (UTC) (edited on 2019-04-05 07:21 (UTC) by QuartzDragon)

May not update for the time being, as the rebase is failing to build.

Bug report here:

QuartzDragon commented on 2019-04-04 04:56 (UTC)

Thanks for the notification!

I'll do some testing to make sure it works, and then I'll push the update.

nicman23 commented on 2019-04-03 17:16 (UTC)

5.0 rebase done :D

tanscoobydoo03 commented on 2019-03-05 04:18 (UTC)

I really hope this becomes mainstream. This file system has so much potential!

QuartzDragon commented on 2019-01-21 14:07 (UTC)

Will just track master from now on.

If there are problems ~ contact Kent about it. :)

nicman23 commented on 2019-01-20 10:11 (UTC)

works with new upstream tag :)


QuartzDragon commented on 2019-01-19 18:06 (UTC)

If you're feeling so inclined, to help with debugging the OOPS, alter the PKGBUILD to remove the chosen commit to pull the latest master code.

Kent needs a kernel panic backtrace for it, but I don't understand how to get one myself. :/

QuartzDragon commented on 2019-01-14 09:43 (UTC) (edited on 2019-01-15 05:55 (UTC) by QuartzDragon)

Because I'd rather not hold this back any longer, I'm pushing it to last known working commit for bcachefs, being 303e27810eaf58a0f52518681c90422e50113d63.

Still trying to bisect why it panics beyond that.

QuartzDragon commented on 2019-01-11 18:27 (UTC)


Yeah, I know. :/

Please email Kent the results of your OOPS ~ that should help him isolate the issue. :)

nicman23 commented on 2019-01-11 14:24 (UTC)

it does compile but it oops at like 1.2 secs :/

QuartzDragon commented on 2019-01-02 07:45 (UTC)

I should have checked before... bcachefs doesn't build properly with 4.20 at the moment. :|

QuartzDragon commented on 2019-01-02 07:25 (UTC)

4.20 version is out now. :)

QuartzDragon commented on 2019-01-01 11:00 (UTC)

That's my tired mistake.

For 4.19, the Arch kernel only goes up to .12, because they've now started using 4.20.

A proper update will have to wait until Kent rebases onto 4.20, sorry.

piotr212 commented on 2019-01-01 10:43 (UTC)

I have problem with building ==> Starting prepare()... -> Adding patches from Arch Linux kernel repository... fatal: Couldn't find remote ref v4.19.13-arch1

QuartzDragon commented on 2018-12-05 12:25 (UTC)

I've added a patch from that fix the EXT4 corruption bugs caused by BLK-MQ.

Will probably be in the next stable release, but I've added it early. :)

QuartzDragon commented on 2018-11-20 21:12 (UTC)

Fixed. :)

nconfig can now be enabled by enabling a variable in the PKGBUILD. :)

QuartzDragon commented on 2018-11-20 21:08 (UTC)

I did that just in case anyone wants to modify the config before building.

I guess I should take a leaf from linux-ck's PKGBUILD... hold on.

tscs37 commented on 2018-11-20 20:34 (UTC)

Atm the compile process is interrupted by nconfig, that's probably not intentional, removing the line with "make nconfig" should do it.