Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Sanoid/Syncoid (ZFS snapshots and replication)

Featured Replies

anyone can help here ?

 

image.thumb.png.ed607143588bf075d55b8ed205012446.png

  • Replies 77
  • Views 52.1k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • The problem is that the version of mbuffer installed by the plugin is not compatible with the new OS version (7.x). This becomes even worse because the OS provides its own mbuffer package, which will

  • foo_fighter
    foo_fighter

    @steini84: Looks like mbuffer needs to be updated for UnRaid V7:   root@NAS:/boot/config/plugins# find . -name '*mbuffer*' ./unRAID6-Sanoid/packages/mbuffer-20240107-x86_64-1_SBo.tgz

  • Hey.   I have created a pull request that does not install mbuffer and perl 5.34 (perl 5.38.2 is preinstalled on unraid 7) with the sanoid plugin on unraid 7. I don't have unraid 7 available

Posted Images

I can not help but i get exactly the same error when trying to install it from Apps.

Same here seem the issue is in the plugin config if referencing a file that doesn't exist. I opened a ticket in Github.

 

 

  • Author

Forgot to update the reference to the new mbuffer package so the install failed on new installs (updates were fine). Fixed now


Sent from my iPhone using Tapatalk

im not sure it releated here ,but im using @SpaceInvaderOne user script for ZFS snapshots and all worked fine but today have Warning when

 

Create the snapshots on the source directory [system_cache_ssd/appdata] using Sanoid ,and sanoid + syncoid take 15min instead of 3 min .

 

image.thumb.png.b8b79fe3cc79aab972f8b3cc5f305547.png

5 hours ago, steini84 said:

Forgot to update the reference to the new mbuffer package so the install failed on new installs (updates were fine). Fixed now

 

Should we need to wait for plugin Update or just to download *.plg file and replace the old one ?

On 7/25/2023 at 8:24 PM, Masterwishx said:

im not sure it releated here ,but im using @SpaceInvaderOne user script for ZFS snapshots and all worked fine but today have Warning when

 

Create the snapshots on the source directory [system_cache_ssd/appdata] using Sanoid ,and sanoid + syncoid take 15min instead of 3 min .

 

image.thumb.png.b8b79fe3cc79aab972f8b3cc5f305547.png

 

@steini84 i posted to UNASSIGNED DEVICES topic  ,and author said :

 

 

The reason this showed up is that you had a PC with the UD GUI open and apparently your server was working very hard.  The command that timed out is UD trying to read the mounts file to determine mounted status of the UD devices.  Reading that file should not take longer than 1 second.  I will increase the time out a bit to try to keep this from happening, but it is harmless other than to show UD could potentially be hanging.  UD will catch up on the mounted status at the next background scan.

 

Maybe ask the plugin author if they can adjust the priority.

  • 3 weeks later...

Since about August 6 I'm getting warnings about mbuffer not found in my daily replication logs:

 

WARN: mbuffer not available on source ssh:-S /tmp/syncoid-nas-backup-nas-backup@nas-1692147601 nas-backup@nas - sync will continue without source buffering.

 

I do regular updates of Unraid incl. all apps. My current version of sanoid is 2.2.0a.

Edited by Gorf

  • 2 weeks later...

also have this issue 

 

image.thumb.png.b0b3813f1ee02570ae0dabe35306b6ba.png

  • 1 month later...

Does this plugin work on 6.12.4 with ZFS pools created via the Unraid method rather than the old ZFS plugin? Looking for an elegant solution for snapshots on default Unraid ZFS.

  • 2 weeks later...
On 8/26/2023 at 1:29 PM, Masterwishx said:

also have this issue 

 

image.thumb.png.b0b3813f1ee02570ae0dabe35306b6ba.png

I'm also getting this warning, does anyone have a workaround? I tried installing mbuffer from source that this plugin downloads to the root of Unraid, however with no gcc I can't compile.

 

@steini84 Do you have a solution?

  • Author
I'm also getting this warning, does anyone have a workaround? I tried installing mbuffer from source that this plugin downloads to the root of Unraid, however with no gcc I can't compile.
 
@steini84 Do you have a solution?

There seems to be a problem with the mbuffer package. You can install the older version, but all the Slackware packages i found for the latest version are the same.

To install the older package you can use

wget https://github.com/Steini1984/unRAID6-Sainoid/raw/167f5ad3dc1941ef7670efcd21fbb4e6e6ad8587/packages/mbuffer.20200505.x86_64.tgz

installpkg mbuffer.20200505.x86_64.tgz


Sent from my iPhone using Tapatalk
  • 2 months later...

@steini84How do you find syncoid / sanoid for removing older snapshots that are over the allowance?  I.e. If we did hourly for a week, then daily for a month, then monthly for a year, we should expect only 4 weeks of daily backups right?  This is something that I never got working in znapzend.  It seemed to just keep everything indefinitely.  BTW I never did get znapzend working after the ZFS went built in, it only works for a few hours or days then stops.  So as per your suggestion, I am looking at Syncoid / Sanoid.  (Still figuring out that difference).

  • Author
13 hours ago, Marshalleq said:

@steini84How do you find syncoid / sanoid for removing older snapshots that are over the allowance?  I.e. If we did hourly for a week, then daily for a month, then monthly for a year, we should expect only 4 weeks of daily backups right?  This is something that I never got working in znapzend.  It seemed to just keep everything indefinitely.  BTW I never did get znapzend working after the ZFS went built in, it only works for a few hours or days then stops.  So as per your suggestion, I am looking at Syncoid / Sanoid.  (Still figuring out that difference).

It works perfectly for me in Sanoid/syncoid and I might need to depricate the Znapzend plugin since I have not used it at all since my migration. This works exactly as you described and here you can see an example of my production profile:

[template_production]
        frequently = 4
        hourly = 24
        daily = 30
        monthly = 0
        yearly = 0
        autosnap = yes
        autoprune = yes

and here you can see how the snapshots are currently 

root@Unraid:~# zfs list -t snapshot ssd/Docker/Freshrss
NAME                                                          USED  AVAIL     REFER  MOUNTPOINT
ssd/Docker/Freshrss@autosnap_2023-12-16_23:59:15_daily       1.41M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-17_23:59:03_daily       1.16M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-18_23:59:05_daily       1.12M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-19_23:59:18_daily       1.16M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-20_23:59:11_daily       1.19M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-21_23:59:17_daily       1.19M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-22_23:59:09_daily       1.13M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-23_23:59:03_daily       1.13M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-24_23:59:16_daily        864K      -     17.1M  -
ssd/Docker/Freshrss@autosnap_2023-12-25_23:59:08_daily       1.05M      -     18.3M  -
ssd/Docker/Freshrss@autosnap_2023-12-26_23:59:12_daily       1.07M      -     18.3M  -
ssd/Docker/Freshrss@autosnap_2023-12-27_23:59:13_daily       1.15M      -     18.4M  -
ssd/Docker/Freshrss@autosnap_2023-12-28_23:59:06_daily       1.18M      -     18.4M  -
ssd/Docker/Freshrss@autosnap_2023-12-29_23:59:20_daily       1.09M      -     18.4M  -
ssd/Docker/Freshrss@autosnap_2023-12-30_23:59:18_daily        904K      -     18.4M  -
ssd/Docker/Freshrss@autosnap_2023-12-31_23:59:03_daily       1.06M      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-01_23:59:03_daily       1.08M      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-02_23:59:07_daily       1.17M      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-03_23:59:10_daily       1.15M      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-04_23:59:09_daily       1.15M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-05_23:59:06_daily       1.33M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-06_23:59:23_daily       1.20M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-07_23:59:20_daily       1.14M      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-08_23:59:15_daily       1.09M      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-09_23:59:12_daily       1.09M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-10_23:59:21_daily       1.10M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-11_23:59:21_daily       1.26M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-12_23:59:02_daily       1.14M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-13_23:59:25_daily       1.04M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_13:00:09_hourly       944K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_14:00:17_hourly       824K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_15:00:11_hourly       840K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_16:00:23_hourly       856K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_17:00:32_hourly       856K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_18:00:04_hourly       752K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_19:00:16_hourly       768K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_20:00:10_hourly       792K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_21:00:36_hourly       800K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_22:00:08_hourly       760K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_23:00:45_hourly       648K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_23:59:21_daily        144K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_00:00:11_hourly       144K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_01:00:31_hourly       640K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_02:00:28_hourly       624K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_03:00:01_hourly       616K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_04:00:33_hourly       616K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_05:00:10_hourly       568K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_06:00:28_hourly       680K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_07:00:39_hourly       768K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_08:00:25_hourly       744K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_09:00:32_hourly       736K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_10:00:08_hourly       888K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_11:00:36_hourly       880K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_12:00:19_hourly         0B      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_12:00:19_frequently     0B      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_12:15:17_frequently   184K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_12:30:21_frequently   200K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_12:45:16_frequently     0B      -     19.6M  -

 

The system is really configurable and the documentation is really good: https://github.com/jimsalterjrs/sanoid

  • 4 weeks later...
On 1/16/2024 at 2:20 AM, steini84 said:

It works perfectly for me in Sanoid/syncoid and I might need to depricate the Znapzend plugin since I have not used it at all since my migration. This works exactly as you described and here you can see an example of my production profile:

[template_production]
        frequently = 4
        hourly = 24
        daily = 30
        monthly = 0
        yearly = 0
        autosnap = yes
        autoprune = yes

and here you can see how the snapshots are currently 

root@Unraid:~# zfs list -t snapshot ssd/Docker/Freshrss
NAME                                                          USED  AVAIL     REFER  MOUNTPOINT
ssd/Docker/Freshrss@autosnap_2023-12-16_23:59:15_daily       1.41M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-17_23:59:03_daily       1.16M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-18_23:59:05_daily       1.12M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-19_23:59:18_daily       1.16M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-20_23:59:11_daily       1.19M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-21_23:59:17_daily       1.19M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-22_23:59:09_daily       1.13M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-23_23:59:03_daily       1.13M      -     17.2M  -
ssd/Docker/Freshrss@autosnap_2023-12-24_23:59:16_daily        864K      -     17.1M  -
ssd/Docker/Freshrss@autosnap_2023-12-25_23:59:08_daily       1.05M      -     18.3M  -
ssd/Docker/Freshrss@autosnap_2023-12-26_23:59:12_daily       1.07M      -     18.3M  -
ssd/Docker/Freshrss@autosnap_2023-12-27_23:59:13_daily       1.15M      -     18.4M  -
ssd/Docker/Freshrss@autosnap_2023-12-28_23:59:06_daily       1.18M      -     18.4M  -
ssd/Docker/Freshrss@autosnap_2023-12-29_23:59:20_daily       1.09M      -     18.4M  -
ssd/Docker/Freshrss@autosnap_2023-12-30_23:59:18_daily        904K      -     18.4M  -
ssd/Docker/Freshrss@autosnap_2023-12-31_23:59:03_daily       1.06M      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-01_23:59:03_daily       1.08M      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-02_23:59:07_daily       1.17M      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-03_23:59:10_daily       1.15M      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-04_23:59:09_daily       1.15M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-05_23:59:06_daily       1.33M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-06_23:59:23_daily       1.20M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-07_23:59:20_daily       1.14M      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-08_23:59:15_daily       1.09M      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-09_23:59:12_daily       1.09M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-10_23:59:21_daily       1.10M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-11_23:59:21_daily       1.26M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-12_23:59:02_daily       1.14M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-13_23:59:25_daily       1.04M      -     19.7M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_13:00:09_hourly       944K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_14:00:17_hourly       824K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_15:00:11_hourly       840K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_16:00:23_hourly       856K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_17:00:32_hourly       856K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_18:00:04_hourly       752K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_19:00:16_hourly       768K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_20:00:10_hourly       792K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_21:00:36_hourly       800K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_22:00:08_hourly       760K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_23:00:45_hourly       648K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-14_23:59:21_daily        144K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_00:00:11_hourly       144K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_01:00:31_hourly       640K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_02:00:28_hourly       624K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_03:00:01_hourly       616K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_04:00:33_hourly       616K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_05:00:10_hourly       568K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_06:00:28_hourly       680K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_07:00:39_hourly       768K      -     19.5M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_08:00:25_hourly       744K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_09:00:32_hourly       736K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_10:00:08_hourly       888K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_11:00:36_hourly       880K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_12:00:19_hourly         0B      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_12:00:19_frequently     0B      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_12:15:17_frequently   184K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_12:30:21_frequently   200K      -     19.6M  -
ssd/Docker/Freshrss@autosnap_2024-01-15_12:45:16_frequently     0B      -     19.6M  -

 

The system is really configurable and the documentation is really good: https://github.com/jimsalterjrs/sanoid

Nice, I've got this started now using space invaders script, but it's a bit weird and limiting so will convert to the method you're using.  Am hoping I can do a replication different to the snaps like znapzend did.  

  • 2 weeks later...
  • Author

No sanoid does a lot and you only need to write the config file


Sent from my iPhone using Tapatalk

  • 3 weeks later...

I've having issues running replication, get this error which results in everything failing during initial replication:

INFO: Sending oldest full snapshot data/appdata@2024-01-03-171850 (~ 88 KB) to new target filesystem:
cannot receive new filesystem stream: pool must be upgraded to receive this stream.
warning: cannot send 'data/appdata@2024-01-03-171850': signal received
CRITICAL ERROR: zfs send 'data/appdata'@'2024-01-03-171850' | pv -p -t -e -r -b -s 90224 | zfs receive -F 'nvr/zfs_backups/data_appdata' failed: 256 at /usr/local/sbin/syncoid line 549.
INFO: Sending oldest full snapshot data/appdata/MKVToolNix@2024-01-03-171850 (~ 1.6 MB) to new target filesystem:
cannot open 'nvr/zfs_backups/data_appdata': dataset does not exist

 

This is the command being used:

/usr/local/sbin/syncoid -r --force-delete --delete-target-snapshots $source_path $destination_path

 

$source_path is data/appdata, where "data" is the zfs pool and "appdata" is a dataset (with child datasets for each docker)

$destination_path is nvr/zfs_backups/data_appdata, where "nvr" is the zfs pool and "zfs_backups" is the dataset. zfs_backups is empty since this is first time replication.

 

The full script I'm using is here, it's a greatly simplified/cleaned up version of Space Invader's script:

https://github.com/freeskier93/unraid-zfs-snapshot-replication/blob/main/zfs_snapshot_replication.sh

Edited by dcooper

  • 3 weeks later...
On 3/9/2024 at 11:50 AM, dcooper said:

I've having issues running replication, get this error which results in everything failing during initial replication:

INFO: Sending oldest full snapshot data/appdata@2024-01-03-171850 (~ 88 KB) to new target filesystem:
cannot receive new filesystem stream: pool must be upgraded to receive this stream.
warning: cannot send 'data/appdata@2024-01-03-171850': signal received
CRITICAL ERROR: zfs send 'data/appdata'@'2024-01-03-171850' | pv -p -t -e -r -b -s 90224 | zfs receive -F 'nvr/zfs_backups/data_appdata' failed: 256 at /usr/local/sbin/syncoid line 549.
INFO: Sending oldest full snapshot data/appdata/MKVToolNix@2024-01-03-171850 (~ 1.6 MB) to new target filesystem:
cannot open 'nvr/zfs_backups/data_appdata': dataset does not exist

 

This is the command being used:

/usr/local/sbin/syncoid -r --force-delete --delete-target-snapshots $source_path $destination_path

 

$source_path is data/appdata, where "data" is the zfs pool and "appdata" is a dataset (with child datasets for each docker)

$destination_path is nvr/zfs_backups/data_appdata, where "nvr" is the zfs pool and "zfs_backups" is the dataset. zfs_backups is empty since this is first time replication.

 

The full script I'm using is here, it's a greatly simplified/cleaned up version of Space Invader's script:

https://github.com/freeskier93/unraid-zfs-snapshot-replication/blob/main/zfs_snapshot_replication.sh

 

Had some time to look into this and the fix was easy. For whatever reason not all the zfs features were enabled for the destination pool. The command "zpool upgrade" showed what features weren't enabled, then the command "zpool upgrade -a" to upgrade all the pools. After running that no issues with replication.

 

https://openzfs.github.io/openzfs-docs/man/master/8/zpool-upgrade.8.html

 

 

 

  • 3 weeks later...
On 10/23/2023 at 3:25 PM, steini84 said:


There seems to be a problem with the mbuffer package. You can install the older version, but all the Slackware packages i found for the latest version are the same.

To install the older package you can use

wget https://github.com/Steini1984/unRAID6-Sainoid/raw/167f5ad3dc1941ef7670efcd21fbb4e6e6ad8587/packages/mbuffer.20200505.x86_64.tgz

installpkg mbuffer.20200505.x86_64.tgz


Sent from my iPhone using Tapatalk

 

I stumbled over the problem with the broken mbuffer package. The package fetched by the plugin cointains only the sources of mbuffer and I was not able to find a current version packaged for Slackware. But there is a build script available: https://slackbuilds.org/repository/15.0/system/mbuffer/

 

I built the latest version of mbuffer (20240107) and packaged it with the linked SlackBuild for Slackware. I think it would be great, if mbuffer package in the plugin would be updated to have a working version available out of the box.

 

The packaged version of mbuffer is in the attachment. But if you like, I can also create a pull request on GitHub with the updates for the plugin. 

mbuffer-20240107-x86_64-1_SBo.tgz

Edited by SoerenS
typos

On 10/23/2023 at 6:25 AM, steini84 said:


There seems to be a problem with the mbuffer package. You can install the older version, but all the Slackware packages i found for the latest version are the same.

To install the older package you can use

wget https://github.com/Steini1984/unRAID6-Sainoid/raw/167f5ad3dc1941ef7670efcd21fbb4e6e6ad8587/packages/mbuffer.20200505.x86_64.tgz

installpkg mbuffer.20200505.x86_64.tgz


Sent from my iPhone using Tapatalk

Thanks for this, worked fine on my main system and backup to remove the mbuffer error.

  • 2 weeks later...
On 4/15/2024 at 5:40 PM, SoerenS said:

But if you like, I can also create a pull request on GitHub with the updates for the plugin.

 

Please if you can

@steini84 can be this version (updated) used in plugin ?  

 

Edited by Masterwishx

On 4/15/2024 at 5:40 PM, SoerenS said:

I built the latest version of mbuffer (20240107) and packaged it with the linked SlackBuild for Slackware. I think it would be great, if mbuffer package in the plugin would be updated to have a working version available out of the box.

 

I made the pr with your file, just not shure if needs to be recompiled for usr/local instead of /usr, waiting for @steini84 responds

  • Author
51 minutes ago, Masterwishx said:

 

I made the pr with your file, just not shure if needs to be recompiled for usr/local instead of /usr, waiting for @steini84 responds

Perfect thanks, this has been merged :)

My plugin gets stuck on updating and never seems to finish. Attached is what I see in the console
 

sanoid_log.txt

Edited by maydaytek

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.