Seg fault error when adding plots

[RobbieL811]

What's up bud? Thanks for your work first of all. I'm using PlotFS to try to create a filesystem of all of the left over space on the drives that I already have plotted. I used dd to create an empty file that fills the leftover space on each of the drives, then I add that file as a device to my PlotFS filesystem. Once all drives are added, I run "sudo plotfs --add_plot $PLOT" and it will run successfully until around about 50 or 60% then stop abruptly with no debug message except for "segmentation fault". Any ideas what I might be able to do to find out what's going on?

[RobbieL811]

So, did some testing today. New Ubuntu 22 VM and new Debian VM. Seems that PlotFS is working just fine on the new Ubuntu VM. Brand new Debian VM is failing adding plots @ 63%, I'm pretty sure that's when PlotFS switches over to the new drive for the rest of the plot. Maybe something isn't getting installed or is missing in Debian???

[fisherwei]

Segmentation fault too.

writing recovery point header
0% writing up to 1073741824 bytes from offset 0 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
1% writing up to 1073741824 bytes from offset 1073741824 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
2% writing up to 1073741824 bytes from offset 2147483648 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
3% writing up to 1073741824 bytes from offset 3221225472 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
5% writing up to 1073741824 bytes from offset 4294967296 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
6% writing up to 1073741824 bytes from offset 5368709120 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
7% writing up to 1073741824 bytes from offset 6442450944 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
8% writing up to 1073741824 bytes from offset 7516192768 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
10% writing up to 1073741824 bytes from offset 8589934592 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
11% writing up to 1073741824 bytes from offset 9663676416 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
12% writing up to 1073741824 bytes from offset 10737418240 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
13% writing up to 1073741824 bytes from offset 11811160064 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
15% writing up to 924842944 bytes from offset 12884901888 to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
16% finished writing to device 300751622238b71a7781bf6efefb6dd7345188e32693e6207204cdb71e44e0a6
Segmentation fault

debian 12 bare metal