Guix file-system error error with mergerfs

  • Open
  • quality assurance status badge
Details
One participant
  • Distopico
Owner
unassigned
Submitted by
Distopico
Severity
normal

Debbugs page

D
D
Distopico wrote on 5 Aug 16:22 -0700
(address . bug-guix@gnu.org)
878qjxxsjj.fsf@riseup.net
I'm trying to setup Mergerfs in Guix,

Mergefs works with normal fstab configuration like:

Toggle snippet (4 lines)
UUID=30393ca8-.......... /mnt/media1 ext4 defaults
/mnt/media1 /mnt/raid/ mergerfs defaults,cache.files=partial,dropcacheonclose=true,category.create=pfrd

But also support glob

Toggle snippet (3 lines)
/mnt/media* /mnt/raid/ mergerfs defaults,...

and Guix is adding the fstab configuration fine (after reconfigure), but
I get an error in `guix reconfigure` and is not mounting it.

Toggle snippet (4 lines)
guix system: warning: exception caught while executing 'start' on service 'file-system-/mnt/raid':
In procedure mount: mount "/mnt/media1" on "///mnt/raid": No such device

`herd status`:
Toggle snippet (4 lines)
Failed to start:
! file-system-/mnt/raid

this is my file-system configuration

Toggle snippet (9 lines)
(define margerfs-mapped-device
(list (file-system
(mount-point "/mnt/media1")
(device (uuid
"30393ca8-..." 'ext4))
(type "ext4"))))


Toggle snippet (17 lines)
(file-systems (cons*
;; more disks...
;; mergerfs
(file-system
(device "/mnt/media1")
(mount-point "/mnt/raid")
(dependencies margerfs-mapped-device)
(options "defaults,cache.files=partial,dropcacheonclose=true,category.create=pfrd")
(type "mergerfs")
;(mount-may-fail? #t)
;(create-mount-point? #t)
(check? #f))
(append
margerfs-mapped-device
%base-file-systems)))

Right now I'm just mapping one disk "/mnt/media1/", with "/mnt/media*" or
"/mnt/media1:/mnt/media2" does not work either (and I expected to not
work with that custom mergefs way), mounting manually works fine, or
after the reconfigure with `sudo mount -a`

I guess this is a perfect use case for mapping-devices but mergerfs is
not implemented for mapping in guix yet.

Why the most simple use case that should work is not working?
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 79181@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 79181
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch