Package Details: mhddfs 0.1.39-4

Git Clone URL: https://aur.archlinux.org/mhddfs.git (read-only)
Package Base: mhddfs
Description: fuse filesystem that combines several mount points into a single one.
Upstream URL: http://mhddfs.uvw.ru/
Licenses: GPL3
Submitter: None
Maintainer: n17ikh
Last Packager: n17ikh
Votes: 28
Popularity: 0.006525
First Submitted: 2009-03-17 10:40
Last Updated: 2018-06-29 22:58

Latest Comments

1 2 3 Next › Last »

n17ikh commented on 2019-01-07 08:58

matmunn14: I've tested on a few different systems and haven't seen that behavior. What are the underlying filesystems, what are the mount options you're using?

Is the mhddfs process still running or has it crashed out?

matmunn14 commented on 2019-01-07 06:52

Since upgrading to kernel 4.20 I can't seem to create any new files in the virtual directory. Every operation is just dying with "Input/output error."

I had to install fuse3 as Ownaginatious just to boot but still can't do anything in my filesystem

n17ikh commented on 2019-01-03 09:09

Ownaginatious: Initially, I couldn't reproduce your problem, because I run mhddfs manually via the command line. Mhddfs itself does not have a dependency on fuse3. However, the "mount.fuse" binary shipped in the fuse-common package seems to be broken at the moment. It links against fuse3, but the package doesn't require its installation. I'm not sure why Arch's fuse maintainer has done it like that, but it seems like a bug.

Ownaginatious commented on 2019-01-02 18:51

I started getting boot failures as of kernel linux-4.19.1.arch1-1. From journalctl, it looks like the issue was a missing library: "mount.fuse: error while loading shared libraries: libfuse3.so.3: cannot open shared object file: No such file or directory".

I was able to fix it by simply doing: "sudo pacman -S fuse3".

Not sure if this was due to the kernel update or something else; I updated a bunch of packages all at once.

Maybe the fuse dependency should be changed to fuse3?

n17ikh commented on 2018-06-29 22:59

Thanks for the heads-up, matmunn14. Should be fixed now.

matmunn14 commented on 2018-06-29 22:22

To get this to build I had to update src/tools.c and src/main.c to point to < sys/xattr.h > instead of < xattr/xattr.h >

I can supply patches if needed.

moonman commented on 2018-04-05 02:41

It seems you've delayed the problem with your workaround. I did not have any problems for 2 years and then started extracting a large archive over a network to the same directory i.e. samba was reading a writing at the same time to the same directory when mhddfs segfaulted. It seems it depends on the workload. Anyway, thanks for adding the patch!

n17ikh commented on 2018-04-04 04:36

Sure, I'll add it. I have the same problem as well - it seems to be caused by mlocate accessing my mhddfs drives while rsync is running, so I worked around it by excluding the mhddfs mount from mlocate. The patch is worth a shot though.

moonman commented on 2018-04-04 04:21

Could you add this patch: https://github.com/ram-nat/mhddfs/commit/26d0f119eaa7e3ffaaf330bf29672e13471cb091 As mentioned in this discussion here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876252

I am having exactly the same problem and the patch seems to have fixed it.

n17ikh commented on 2016-11-21 09:40

I just noticed that upstream is down. If it stays down for a while longer I'll switch the package to an alternate mirror.