tillkrueger

well damnit, looks like I'm stuck until I can clear the docker.img and/or increase its size...by a *lot*, then, since I filled up the docker.img within only hours and have so many terabytes worth of data ahead of me that it will take days/weeks. guess I'm in the same shoes as you, syrys, of needing a solution to not ballooning the docker.img in the first place...maybe slightly simpler than your issue, as I *only* run the Krusader docker.

thanks, syrys! did you end up increasing the size of your docker.img successfully? I don't seem to be able to find the info on that and my img is now at 90%...I stopped all dockers and am ready to make the change, but can't locate the instructions pertaining to this.

emptying the Trash in Krusader did not solve me docker.img ballooning issue (now at 86%, growing by about 1% every hour or so). I also found that Krusader did *not* continue the file moving operations after I shout down the computer from which I initiated the file management operations...I built a queue with 2 items in addition to the first item, which was at 98% completed), and found everything this morning exactly where it was last night...the queue was still intact, but had paused, in essence, last night when I shut down my control computer. Krusader also seems to use total file-size when estimating completion...the last 2% (even though calculated at 30mins) are taking many hours, bc they consist mostly of small JPG images from various timelapses I shot. Krusader is amazing, but lots of room for improvement, still. if a moderator wants to move this into a new thread, I think that would be best...otherwise please excuse my deviation from the OP's main-topic!

my thought exactly, Squid...since I have no other way of knowing what Krusader is doing...it's a really cool file manager, I must say! if the UI could be configured to always show the Queue at the bottom and the file manager at the top, that would make it an over the top solution for my file management duties on the server...if I were better at using rsync in Terminal, maybe I'd feel different about that, but for a GUI guy like me, Krusader is pretty great...sure beats Dolphin, in my mind. if ever you do find a way to get that big Queue display back, do let us know, Squid! (and I'll do the same)

the big horizontal Queue window is covering up the Docker menus right now, so I can't operate it until the current move operation is in progress, but will look for "Empty Trash" as soon as it finishes this move (in about 2hrs)...if that solves it, that would be nice; thanks Squid! do you know how I can get that big horizontal Queue window back after I close it? not the little floating one but the big horizontal one that actually shows you the progress and what file(s) it is doing. copy/move operations are not persistent in Krusader, or are they? if I close the browser tab/window that Krusader is running in, it stops the files operation(s), or does it not?

sollte ich eine neue Diskussion anfangen, da diese hier schon etwas älter ist?

I, too, just got a few warnings that my docker.img went from just under 70% to over 75%. In my case it appears pretty obvious that my Krusader app is doing this, as this is the only Docker I've used in a long time and have started to use it to migrate data from smaller/older drives in the array to new/bigger drives...since I'll be doing a *lot* of this in the coming days/weeks (paring down a 15 drive unRAID system to an 8 drive system) I see the pressing need to keep the docker.img from reaching 100%. Could it be that Krusader does excessive logging, and if so, where/how can this be controlled? After the current move operation finishes (in about 5hrs), I can pause and deal with figuring out how to increase the docker.img size before continuing this lengthy process of migrating/combining data to bigger drives.

brilliant! thanks, dmacias, for the tip, and trurl, for the link! the new drive I was shipped (marked as "refurbished" at a substantial discount), already failed and was kicked out of the array...ARRRRGH!!!

ummm, ok, I should have added "screen" before the "-a", of course...I just did that and while it doesn't look like any other old telnet session now, I assume it is now behaving differently? I invoked "rsync -avPX /mnt/disk12/ /mnt/disk11/", so will this be enough to make this session persistent in the background, until it is finished, even if I close this telnet session?

does the server need to be restarted after installing these? I am trying to figure out how to invoke a telnet session that allows me to do copy/move operations in the background, persistently, even if I shut down the machine that invoked it, and was told that that is what "screen" can do...but after installing these tools and telnet'ing into my unRAID server, then using the -a command to try to invoke screen as per the instructions here, i get a "-a: command not found" error...or do I need to cd into a subdirectory first, before invoking screen? I'm a nerd but not a terminal jockey, to say the least, as you can probably see.

that looks excellent...can't wait!

when i try installing, i get this...what could be going wrong? plugin: installing: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community plugin: downloading https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community plugin: downloading: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community ... failed (Invalid URL / Server error response) plugin: wget: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community download failure (Invalid URL / Server error response) UPDATE: never mind...in that original post the URL was not displayed in its entirety in my browser, and hence couldn't find the actual plg file...the correct one is: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg and allowed me to get it installed now. my bad!