Replies: 2 comments
-
Hi My bad in the manual you say 128M and not 128K. Sorry about that. |
Beta Was this translation helpful? Give feedback.
0 replies
-
the --buffer option IS what changes the -m option for the mbuffer command. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi
I am testing zfs-autobackup and i was playing with mbuffer. When i run the following command following the instructions from the manual
zfs-autobackup -v --clear-mountpoint --ssh-target debian11_test offsite1 storage --no-holds --strip-path=1 --keep-source=30s3m --keep-target=30s3min --min-change=0 --snapshot-format={}-%Y-%m-%d_%H:%M:%S --buffer 128k
I am getting that the following error
! [Source] STDERR > mbuffer: fatal: Number of blocks must be at least 5. ! [Target] STDERR > mbuffer: fatal: Number of blocks must be at least 5. ! [Target] STDERR > cannot receive: failed to read from stream ! [Source] Command "zfs send -L -e -v -P -p -i @offsite1-2024-01-14_11:48:03 storage@offsite1-2024-01-14_11:55:44 | mbuffer -q -s128k -m128k" returned exit code 1 (valid codes: [0]) ! [Target] Command "ssh debian11_test 'mbuffer -q -s128k -m128k | zfs recv -u -o canmount=noauto -v -s storage'" returned exit code 1 (valid codes: [0]) ! [Source] storage: FAILED: Last command returned error
Some more questions, is there a way to change mbuffer -m option?
I have red that in this option i could put 1G and i will see better transfers. Is this true?
What it is your opinion about mbuffer values?
Thanks in advanced and sorry if my english are bad
Beta Was this translation helpful? Give feedback.
All reactions