Activity for Date Huang
-
Date Huang posted a comment on discussion Clonezilla live
Ideally, connection limit to 2 will be the best in theory. But it seems it not the best choice if we leave the BT swarm running on their own. I will check if we could meet the theory. Thank you for the report. I had reverted the commit. Steven will create a new release.
-
In your screenshot. ezio_ui.py stops three torrent (It shows 3 times "PauseTorrent") So you have 3 partitions, right? and only ezio_ui.py will shutdown the ezio daemon (that will show the shutdown and remove torrent warning in your screen.) So currently, I will say your restoration is corrent and proper. Because ezio_ui.py will only shutdown the ezio daemon while all torrents are finished and paused. But it's weird, it only took 2min (124s) to finish all stuffs. And all 3 torrents were paused at...
-
In your screenshot. ezio_ui.py stops three torrent (It shows 3 times "PauseTorrent") So you have 3 partitions, right? and only ezio_ui.py will shutdown the ezio daemon (that will show the shutdown and remove torrent warning in your screen.) So currently, I will say your restoration is corrent and proper. Because ezio_ui.py will only shutdown the ezio daemon while all torrents are finished and paused. But it's weird, it only took 2min (124s) to finish all stuffs. And all 3 torrents were paused at...
-
Could you help us to make sure the process is succesful or not? Do you mean "BT restore is not completed, but clients are rebooted"? Or "it's all fine, just warning message that you had some concerns but not sure about that?" By the way, in BT mode, all partitions are restored at the same time. (you could use pageup/down and arrow up/down to scroll the screen to see other partitions' progress)
-
Could you help us to make sure the process is succesful or not? Do you mean "BT restore is not completed, but clients are rebooted"? Or "it's all fine, just warning message that you had some concerns but not sure about that?"
-
By the way, @siet Could you help us to determine those question below? It will help us to figure out the problem. Did server stuck also? How many clients did stuck while cloning? How many clients in total? Always same machines stuck or random machine? Please list the hardware specs of those stuck machine When stucking, is it possible to use free -h to show the ram usage in the system (if system still has response, if not, just ignore this one) Thanks a lot
-
Hi Siet I want to check with you. Will ezio be executed or not in new version? It seems ezio will stuck in the middle of cloning. Could you provide hardware specs on those stuck machine? For now, I think there is some ram shortage on your machine because EZIO will use lots RAM. And if system is running out of ram, all operation will stuck. Let me work for this testing with Steven and give you a trial ISO to test again? Thanks a lot for your patience. I will also do some enhance to log some info to...
-
I have no idea about this Not familiar with DRBL
-
I think your Forti has more than 1 IPs. But I think you still need your network guys to help you.
-
in your desciption. I think you should setup to Forti's IP if your Forti is 10.18.50.254 you should setup to 10.18.50.254
-
Hi Oliver Bumann I saw your screenshot with following line net0: 10.18.50.13/255.255.255.0 But in iPXE website https://ipxe.org/cmd/route You should have some thing like this. net0: 10.18.50.13/255.255.255.0 gw 10.18.50.X maybe you miss the GW in your dhcp server? so client cannot access to 10.19.x.x
-
did tou use the image you created before? try to create new image from phyical disk and try afain
-
try to use latest testing version and could you describe more about your snvrionment and condition you met rks
-
if possible, plz also provide the speed of one of 32 running clients It might be some congestion, so other clients cannot send any request to Lite Server
-
Good to hear that Thanks for feedback and thanks for using Clonezilla BT
-
Thanks a lot!!
-
hmm ok try to use older version or wait for us to update we still dig info
-
maybe you can try to deploy one disk at a time not 3 disks at the same time
-
we are still digging if possible, please try 2.6.1-25 https://sourceforge.net/projects/clonezilla/files/clonezilla_live_stable/2.6.1-25/
-
we are still digging if possible, please try 2.6.1-25
-
Thanks for log we will dig for info. BTW you refresh the record about biggest size image using BT. We always test BT module with 150G image
-
did you restart the process after modifying? and we are trying to reproduce this issue in our side thanks for reporting it
-
By the way Please test this modify the config file at /etc/drbl/drbl-ocs.conf ezio_seeder_opt="-t 1 -k 60" remove -t 1
-
only torrent thanks
-
@siet Hi If possible, please provide the torrent file to us. maybe some issue in side and also provide the output of ps aux on the server side while some clients stuck Thanks
-
@siet Hi If possible, please provide the torrent file to us. maybe some issue in side Thanks
-
I'm not sure how to access remote server. maybe you can install ssh service on the server or just use the scp to send info out (I only developed the BT module) and plz provide the output of ps aux when the proccessing is stuck.(from server) (I want to make sure that other program works normally) thanks
-
remove duplicate msg
-
I'm not sure how to access remote server. (I only developed the BT module) and plz provide the output of ps aux when the proccessing is stuck.(from server) (I want to make sure that other program works normally) thanks
-
I'm not sure how to access remote server. (I only developed the BT module) and plz provide the output of ps aux when the proccessing is stuck.(from server) (I want to make sure that other program works normally) thanks
-
16g ram is enough for server try to use latest tesing version log file is in /var/log/ and if possible, pack all the file and send to us thanks
-
hi which version did you use? could you try to use testing version?
-
I'm not sure the problem is inside CloneZilla or EZIO. Both of them has lots of change after 20180812-bionic.
-
It seems it isn't the issue that EZIO doesn't detect tracker is gone. EZIO doesn't enter the Upload Mode, and it won't check tracker. I thought it is possible that progress stuck at 99.9% and it doesn't affect or damage the filesystem. Even it shows 100% progress, but it doesn't mean it's real 100%. All client stucks or just partial clients will stuck? There is some way we can try to figure out the problem. 1. Try to use CloneZilla Lite Server Bittorrent Disk-to-disk mechanism If the mechanism works...
-
There is a bug before EZIO v1.1.6 (not included) It has been fixed in latest version of CloneZilla. By the way, you can wait for 15 mins which is EZIO's timeout. If EZIO has nothing to seed for 15min, it will close itself and execute the remaining part.
-
There is some performance issue in commit ba600d9eb7 This issue was fixed until commit dffa52a4c7c I have to say version 0.3.12+gitfeb58af is still unstable. I'm not sure that commit truly works fine.
-
There is some performance issue in commit ba600d9eb7 This issue was fixed until commit dffa52a4c7c I have to say version 0.3.12+gitfeb58af is still unstable. I'm not sure that commit truly works fine.
-
ODROID XU4 is armv7 (32-bit)
-
kvm[1]: HYP mode not available That means Pi doesn't enable virtualization. That won't affect CloneZilla. I thought there is other reason to cause kernel panic. I doesn't really understand what situation do you want, so I couldn't give you advice.
-
Hi @Siet I'm Date Huang who is the author of EZIO. 1. system 1.1 ram I'm not sure what the OOM policy is. But I thought EZIO( or libtorrent-rasterbar) will overcommit memory to use. So if there are too many processes, it will kill EZIO first to free some memory. 2. Error resilience when creating torrent slices partclone will slice image to fit EZIO-compatible format, but it will slice a filesystem block into a file. It will use too many inodes to store a small file. It seems partclone doesn't combine...
-
Hi @Siet I'm Date Huang who is the author of EZIO. 1. system 1.1 ram I'm not sure what the OOM policy is. But I thought EZIO( or libtorrent-rasterbar) will overcommit memory to use. So if there are too many processes, it will kill EZIO first to free some memory. 2. Error resilience when creating torrent slices partclone will slice image to fit EZIO-compatible format, but it will slice a filesystem block into a file. It will use too many inodes to store a small file. It seems partclone doesn't combine...
-
Hi Chunk, Thanks for using CloneZilla BT. The BT module,named EZIO, is made by my friend and me. It seems EZIO stable enough to use in proction envrionment. If you have any question about BT, feel free to ask us. Thanks again
1