Open zunder1990 opened 1 year ago
Zorlin
commented
1 year ago Hi @zunder1990,
That's cool! I think you might be the first person to actually use this outside of me.
Currently the plugin doesn't support subfolders at all, but I will strongly consider prioritising adding support for that. It should be a relatively minor change, it just needs testing and care.
zunder1990
commented
1 year ago I will keep an eye on the git updates and test again. Right now I have 4 node proxmox cluster and I mount moosefs path using fstab. I use moosefs as the backend for my vm backups. I am using the mfsdelayedinit since on other hosts it would fail to mount on boot since it was trying to mount before network was up. Here is from fstab moosefs-leader:/vmbackups /mnt/vmbackups moosefs rw,mfsdelayedinit,mfspassword=xxxxxxxxxxxxxx 0 0 Here is the mfsexports 10.10.0.0/24 /vmbackups rw,alldirs,maproot=0,password=xxxxxxxxxxxxxx,admin,mingoal=2,maxgoal=2 I built the package on one of my proxmox nodes and had to install make and gcc I did get an error but the .deb looked to install fine.
rm -rf debian
mkdir debian
make DESTDIR=/root/pve-moosefs/debian install
make[1]: Entering directory '/root/pve-moosefs'
install -d /root/pve-moosefs/debian/usr/share/perl5/PVE/Storage/Custom
for i in MooseFSPlugin.pm; do install -D -m 0644 $i /root/pve-moosefs/debian/usr/share/perl5/PVE/Storage/Custom/$i; done
make[1]: Leaving directory '/root/pve-moosefs'
install -d -m 0755 debian/DEBIAN
sed -e s/@@VERSION@@/0.1.0/ -e s/@@PKGRELEASE@@/1/ -e s/@@ARCH@@/all/
Zorlin
commented
1 year ago Ah. The build error you're seeing is because you need Lintian to test the
built package before finalising it, which is normally covered by installing
the package build-essential.
But yes, it looks like it was built and worked just fine without it; just without actually being lint'd :)
I'll see if I can work on a patch today; apologies if I don't get to this straight away - work such as this plugin is very much a hobby for me as I only use it at home so far :)
~ B
On Sat, Jul 15, 2023 at 8:22 AM zunder1990 @.***> wrote:
I will keep an eye on the git updates and test again. Right now I have 4 node proxmox cluster and I mount moosefs path using fstab. I use moosefs as the backend for my vm backups. I am using the mfsdelayedinit since on other hosts it would fail to mount on boot since it was trying to mount before network was up. Here is from fstab moosefs-leader:/vmbackups /mnt/vmbackups moosefs rw,mfsdelayedinit,mfspassword=xxxxxxxxxxxxxx 0 0 Here is the mfsexports 10.10.0.0/24 /vmbackups rw,alldirs,maproot=0,password=xxxxxxxxxxxxxx,admin,mingoal=2,maxgoal=2 I built the package on one of my proxmox nodes and had to install make and gcc I did get an error but the .deb looked to install fine.
rm -rf debian mkdir debian make DESTDIR=/root/pve-moosefs/debian install make[1]: Entering directory '/root/pve-moosefs' install -d /root/pve-moosefs/debian/usr/share/perl5/PVE/Storage/Custom for i in MooseFSPlugin.pm; do install -D -m 0644 $i /root/pve-moosefs/debian/usr/share/perl5/PVE/Storage/Custom/$i; done make[1]: Leaving directory '/root/pve-moosefs' install -d -m 0755 debian/DEBIAN sed -e s/@@Version https://github.com/Version@@/0.1.0/ -e s/@@PKGRELEASE@@/1/ -e s/@@Arch https://github.com/Arch@@/all/ < control.in >debian/DEBIAN/control install -D -m 0644 copyright debian//usr/share/doc/libpve-storage-custom-moosefs-perl/copyright install -m 0644 changelog.Debian debian//usr/share/doc/libpve-storage-custom-moosefs-perl/ install -m 0644 triggers debian/DEBIAN gzip -9 debian//usr/share/doc/libpve-storage-custom-moosefs-perl/changelog.Debian dpkg-deb --build debian dpkg-deb: building package 'libpve-storage-custom-moosefs-perl' in 'debian.deb'. mv debian.deb libpve-storage-custom-moosefs-perl_0.1.0-1_all.deb rm -rf debian lintian libpve-storage-custom-moosefs-perl_0.1.0-1_all.deb make: lintian: No such file or directory make: *** [Makefile:44: libpve-storage-custom-moosefs-perl_0.1.0-1_all.deb] Error 127
— Reply to this email directly, view it on GitHub https://github.com/Zorlin/pve-moosefs/issues/4#issuecomment-1636580893, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKONLCHGAE2KRPTOT5NYXLXQHPEXANCNFSM6AAAAAA2KWUIYM . You are receiving this because you commented.Message ID: @.***>
I got this working mounting the root of the moosefs folder. I have a subfolder export from moosefs, how do I tell this plugin to use it.