2015-04-29, 23:55
Thank you, looks interesting!
user.mergerfs.srcmounts: /mnt/disk1:/mnt/disk2:/mnt/disk3:/mnt/disk4
user.mergerfs.category.action: all
user.mergerfs.category.create: epmfs
user.mergerfs.category.search: newest
user.mergerfs.func.access: newest
user.mergerfs.func.chmod: all
user.mergerfs.func.chown: all
user.mergerfs.func.create: epmfs
user.mergerfs.func.getattr: newest
user.mergerfs.func.getxattr: newest
user.mergerfs.func.link: all
user.mergerfs.func.listxattr: newest
user.mergerfs.func.mkdir: epmfs
user.mergerfs.func.mknod: epmfs
user.mergerfs.func.open: newest
user.mergerfs.func.readlink: newest
user.mergerfs.func.removexattr: all
user.mergerfs.func.rename: all
user.mergerfs.func.rmdir: all
user.mergerfs.func.setxattr: all
user.mergerfs.func.symlink: epmfs
user.mergerfs.func.truncate: all
user.mergerfs.func.unlink: all
user.mergerfs.func.utimens: all
(2015-05-20, 14:39)eskay993 Wrote: Thanks for the mergerfs tip! Been testing it and worked great with latest Helix.
However, I'm having trouble with Isengard Beta 1, and latest nightly as of today. New episodes are not being picked up.
Fasthash advancedsetting doesnt work eitehr. Used to work in Helix, but also doesn't in Isengard. Have tried mhddfs and mergerfs. Not touched aufs in a while since I was having some issues with it.
Reason for using Isengard is to use my fav skin so keen to get it to work. Anyone else having this issue in Isengard?
Edit:
This is the output of "xattr -l .mergerfs". I set category.search=newest in fastab, but noticed func.getattr=newest is also set. Woudl these two conflict with each other?
Code:user.mergerfs.srcmounts: /mnt/disk1:/mnt/disk2:/mnt/disk3:/mnt/disk4
user.mergerfs.category.action: all
user.mergerfs.category.create: epmfs
user.mergerfs.category.search: newest
user.mergerfs.func.access: newest
user.mergerfs.func.chmod: all
user.mergerfs.func.chown: all
user.mergerfs.func.create: epmfs
user.mergerfs.func.getattr: newest
user.mergerfs.func.getxattr: newest
user.mergerfs.func.link: all
user.mergerfs.func.listxattr: newest
user.mergerfs.func.mkdir: epmfs
user.mergerfs.func.mknod: epmfs
user.mergerfs.func.open: newest
user.mergerfs.func.readlink: newest
user.mergerfs.func.removexattr: all
user.mergerfs.func.rename: all
user.mergerfs.func.rmdir: all
user.mergerfs.func.setxattr: all
user.mergerfs.func.symlink: epmfs
user.mergerfs.func.truncate: all
user.mergerfs.func.unlink: all
user.mergerfs.func.utimens: all
user.mergerfs.srcmounts: /media/btrfs1:/media/btrfs2:/media/btrfs4:/media/btrfs5 :/media/btrfs6
user.mergerfs.category.action: all
user.mergerfs.category.create: mfs
user.mergerfs.category.search: newest
user.mergerfs.func.access: newest
user.mergerfs.func.chmod: all
user.mergerfs.func.chown: all
user.mergerfs.func.create: mfs
user.mergerfs.func.getattr: newest
user.mergerfs.func.getxattr: newest
user.mergerfs.func.link: all
user.mergerfs.func.listxattr: newest
user.mergerfs.func.mkdir: mfs
user.mergerfs.func.mknod: mfs
user.mergerfs.func.open: newest
user.mergerfs.func.readlink: newest
user.mergerfs.func.removexattr: all
user.mergerfs.func.rename: all
user.mergerfs.func.rmdir: all
user.mergerfs.func.setxattr: all
user.mergerfs.func.symlink: mfs
user.mergerfs.func.truncate: all
user.mergerfs.func.unlink: all
user.mergerfs.func.utimens: all
Quote:I also set category.create to "mfs", since I was running into an issue where mergerfs was thinking I was out of disk space when I really wasn't.
(2015-06-03, 22:48)trapexit Wrote:Quote:I also set category.create to "mfs", since I was running into an issue where mergerfs was thinking I was out of disk space when I really wasn't.
Hi. trapexit here. Author of mergerfs. Can you provide more information about this statement? epmfs only considers drives with the path available. mfs considers all drives and will clone the path appropriately.
Quote:But what if you try to add new files somewhere inside that /mnt/virtual? Well, that is quite tricky issue, and I must say the author of mhddfs solved it very well. When you create a new file in the virtual filesystem, mhddfs will look at the free space, which remains on each of the drives. If the first drive has enough free space, the file will be created on that first drive. Otherwise, if that drive is low on space (has less than specified by “mlimit” option of mhddfs, which defaults to 4 GB), the second drive will be used instead. If that drive is low on space too, the third drive will be used. If each drive individually has less than mlimit free space, the drive with the most free space will be chosen for new files.
(2016-03-03, 05:43)yuuzhan Wrote: @Wintersdark, do you mind sharing your fstab entry?
@trapexit (or anyone who knows) is there a policy for Actions (specifically mv / rename) that chooses "Same Drive if enough space, falls back to [SOMETHING ELSE]". Or is that such a basic function that I am missing that it would be anything else
Thanks!
server@server:~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# / was on /dev/sdb1 during installation
###########################################################################################Drive 3tb.wd.nas.2
# <file system> <mount point> <type> <options> <dump> <pass>
# /dev/sdc1 - Root partition
UUID=cb60f539-3611-4a2f-ae87-5d76160298c8 / ext4 errors=remount-ro 0 1
#
# /dev/sdc3 - 3TB WD Red NAS #2
UUID=84d1bfd0-f926-4d10-b6a6-ccda6e34680b /mnt/disk1 ext4 defaults 0 2
#
# /dev/sdc2 - swap partition
UUID=3584caa1-9cbd-4774-a983-c7721bc527ae none swap sw 0 0
##########################################################################################Drive 3tb.seagate.1
# <file system> <mount point> <type> <options> <dump> <pass>
# /dev/sda1 - parity partition
UUID=a809414f-89f0-4804-a9bc-e4b2ffda6e87 /mnt/parity ext4 defaults 0 0
###########################################################################################Drive 3tb.wd.nas.1
# <file system> <mount point> <type> <options> <dump> <pass>
# /dev/sdb2 - 3 TB WD Red NAS #1
UUID=3a315131-a7ec-4cfe-ae97-080fc4919b89 /mnt/disk2 ext4 defaults 0 0
##########################################################################################Drive 2tb.wd.blue.1
# <file system> <mount point> <type> <options> <dump> <pass>
# /dev/sdd1 - 2TB WD Blue
UUID=3dc60174-ae35-449d-ad7a-f5b9d177270f /mnt/disk3 ext4 defaults 0 0
#######################################################################################Drive 1.5tb.wd.green.1
# <file system> <mount point> <type> <options> <dump> <pass>
# /dev/sde1 - 1.5TB WD Green
UUID=875f2541-5fb4-41cb-a0fb-f30be34b58e7 /mnt/disk4 ext4 defaults 0 0
#MergerFS pool mount
/mnt/disk* /mnt/pool fuse.mergerfs defaults,allow_other,func.getattr=newest 0 0