issues with fpart and CUR_FP_FLE

[fusionmc-evilscoop]

Getting this error -

WARN: fpart has finished and the calculated chunk file [/root/.pfp2/fpcache/f.4]
  doesn't exist.  At this point, the number of chunk files
  (NBR_FP_FLES) = [4]. Unless there's valid reason to continue, you should
  consider killing this run and filing a bug.
1758 : chunk file overrun. CUR_FP_FLE = [/root/.pfp2/fpcache/f.4],  NBR_FP_FLES=[4]
ls: cannot access '/root/.pfp2/fpcache/f.4': No such file or directory
1760 : status of [/root/.pfp2/fpcache/f.4] : []

fpart v1.2.0 parsyncfp2 version 2.59 (Smooth Close) Ubuntu 20.04.5 LTS

The fpart is the older version that runs from 0 so file count is 4 CUR_FP_FLE 4th file is f.3 which is why I believe this is giving an error....

Ive tried to fix myself, but my coding skills are not that great and its beyond a quick fix

I did also try setting $FPSTART = 0 ; but this didnt help

[fusionmc-evilscoop]

found if I add the f.4 file then remove it the error goes away

touch f.4 sleep 5 rm -f f.4

[hjmangalam]

Hi, sorry for the delay in answering. You've identified the problem - you need to upgrade fpart to a version > 1.4 I think. At least this one: https://github.com/martymac/fpart/releases/tag/fpart-1.5.0 if not the latest. Harry

On Wed, Jun 5, 2024 at 4:44 AM fusionmc-evilscoop @.***> wrote:

Getting this error -

WARN: fpart has finished and the calculated chunk file [/root/.pfp2/fpcache/f.4] doesn't exist. At this point, the number of chunk files (NBR_FP_FLES) = [4]. Unless there's valid reason to continue, you should consider killing this run and filing a bug. 1758 : chunk file overrun. CUR_FP_FLE = [/root/.pfp2/fpcache/f.4], NBR_FP_FLES=[4] ls: cannot access '/root/.pfp2/fpcache/f.4': No such file or directory 1760 : status of [/root/.pfp2/fpcache/f.4] : []

fpart v1.2.0 parsyncfp2 version 2.59 (Smooth Close) Ubuntu 20.04.5 LTS

The fpart is the older version that runs from 0 so file count is 4 CUR_FP_FLE 4th file is f.3 which is why I believe this is giving an error....

Ive tried to fix myself, but my coding skills are not that great and its beyond a quick fix

I did also try setting $FPSTART = 0 ; but this didnt help

— Reply to this email directly, view it on GitHub https://github.com/hjmangalam/parsyncfp2/issues/20, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASF3Y5GIL42KALOSZGDB7DZF32YVAVCNFSM6AAAAABI2RD3CCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZTKNRXHEZTGOI . You are receiving this because you are subscribed to this thread.Message ID: @.***>

--

Harry Mangalam

[fusionmc-evilscoop]

have to source install the fpart then... 1.2 is the latest in 20.04 which is an LTS and so still in use https://packages.ubuntu.com/search?keywords=fpart

These are work machines and not meant to have source installs on them, policy is repo only, certainly cant release upgrade them

[hjmangalam]

I'm afraid that's a problem I can't address currently. That would seem to counter using parsyncfp itself then..? Harry

On Fri, Jun 14, 2024, 10:06 AM fusionmc-evilscoop @.***> wrote:

have to source install the fpart then... 1.2 is the current one in ubuntu repos....

These are work machines and not meant to have source installs on them, policy is repo only

— Reply to this email directly, view it on GitHub https://github.com/hjmangalam/parsyncfp2/issues/20#issuecomment-2168004372, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASF3Y7SBCYOL4APNJ4UNBTZHLTEJAVCNFSM6AAAAABI2RD3CCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRYGAYDIMZXGI . You are receiving this because you commented.Message ID: @.***>

[fusionmc-evilscoop]

:( on a cronscript yes, its going to cause an issue... manually, the workaround works...just not pretty lol

shame there isnt a way to detect fpart version and adjust accordingly.... failing that, ill have to wait for end of support in 2025 :(