summary refs log tree commit diff
path: root/gnu/build
diff options
context:
space:
mode:
authorTobias Geerinckx-Rice <me@tobias.gr>2021-06-12 21:36:08 +0200
committerTobias Geerinckx-Rice <me@tobias.gr>2021-09-23 18:17:16 +0200
commit68b219b9f482f09e7c55aaee4b64222d8c86172a (patch)
treeac557b08cd1ab581cf501627f5d55f7d7bb888cc /gnu/build
parenta75a3d71329d3ca07a2ef18b81fc7b463f703ed7 (diff)
downloadguix-68b219b9f482f09e7c55aaee4b64222d8c86172a.tar.gz
gnu: Don't abuse check-btrfs-file-system to scan.
It was never guaranteed to be run for non-root file systems.  It was for
root file systems only due to a bug now fixed.

* gnu/build/file-systems.scm (check-btrfs-file-system): Don't invoke
‘btrfs device scan’ here.
* gnu/system/linux-initrd.scm (raw-initrd): Do so here if any btrfs file
systems are present.
Diffstat (limited to 'gnu/build')
-rw-r--r--gnu/build/file-systems.scm2
1 files changed, 0 insertions, 2 deletions
diff --git a/gnu/build/file-systems.scm b/gnu/build/file-systems.scm
index a54127e888..251ca51fc4 100644
--- a/gnu/build/file-systems.scm
+++ b/gnu/build/file-systems.scm
@@ -328,8 +328,6 @@ When FORCE? is true, do perform a real check.  This is not recommended!  See
 @uref{https://bugzilla.redhat.com/show_bug.cgi?id=625967#c8}.  If REPAIR is
 false, do not write to DEVICE.  If it's #t, fix any errors found.  Otherwise,
 fix only those considered safe to repair automatically."
-  ;; XXX Why make this conditional on (check? #t) at all?
-  (system* "btrfs" "device" "scan")     ; ignore errors
   (if force?
       (match (status:exit-val
               (apply system* `("btrfs" "check" "--progress"