01:00:25fofofofofofofofo joins
06:00:22Server0057__ quits [Client Quit]
06:02:04Miki_57 joins
06:14:19Dango360_ quits [Read error: Connection reset by peer]
07:06:41Unholy23613166180851 (Unholy2361) joins
07:49:16Exorcism (exorcism) joins
07:55:31Exorcism quits [Remote host closed the connection]
07:55:55Exorcism (exorcism) joins
08:20:38nulldata quits [Ping timeout: 252 seconds]
08:33:50nulldata (nulldata) joins
08:49:36BigBrain_ quits [Ping timeout: 245 seconds]
08:51:31BigBrain_ (bigbrain) joins
11:00:51BigBrain_ quits [Ping timeout: 245 seconds]
11:06:38BigBrain_ (bigbrain) joins
11:09:29pseudorizer quits [Ping timeout: 252 seconds]
11:12:04pseudorizer (pseudorizer) joins
13:52:33LeGoupil joins
14:19:26LeGoupil quits [Remote host closed the connection]
16:09:16Dango360 (Dango360) joins
16:21:47BearFortress_ quits [Ping timeout: 265 seconds]
16:30:19iCaotix quits [Client Quit]
16:30:27iCaotix_ joins
18:33:23qwertyasdfuiopghjkl quits [Client Quit]
18:41:39G4te_Keep3r3492 quits [Read error: Connection reset by peer]
18:42:23G4te_Keep3r3492 joins
18:42:47qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
19:27:06sec^nd quits [Ping timeout: 245 seconds]
19:29:37BearFortress joins
19:30:04that_lurker quits [Quit: Clowning around is not the same as fooling around...I am a clown, not a fool]
19:32:23sec^nd (second) joins
19:35:13that_lurker (that_lurker) joins
19:48:25Exorcism quits [Client Quit]
20:04:07tzt quits [Ping timeout: 265 seconds]
20:13:02noname quits [Remote host closed the connection]
20:13:02jonathanbuchh quits [Remote host closed the connection]
20:13:07noname joins
20:13:07jonathanbuchh joins
22:02:31tzt (tzt) joins
22:37:14<@JAA>jasons: Re #archiveteam, https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior#The_Warrior_virtual_machine_is_using_up_disk_space,_even_though_it's_not_running_a_project! still applies, even though the question mentions 'not running a project'.
22:37:48<@JAA>In short, yes, that's normal due to how virtual disks work.
22:38:37<@JAA>I suppose that answer could better explain why this happens.
22:39:42<jasons>howdy people
22:39:42<jasons>I just reimported a fresh warrior into virt box
22:39:42<jasons>have it working on youtube (as well as a couple other warriors on other projects)
22:39:42<jasons>but in the ~3.5 hours since i started the YT warrior, its disk size has grown to ~50gb
22:39:42<jasons>is that normal?!
22:41:52<@JAA>It's a bit more complicated than this in practice, but essentially, the virtual disk's size will remain at the maximum that's been used inside it since it was last cleaned with one of the methods mentioned there.
22:42:50<@JAA>When a file gets deleted inside the VM, this just sets some flags in the file system metadata to mark the relevant sectors as unused. But the virtualisation software (i.e. VirtualBox) doesn't know about this, so it can't release the storage occupied by them in the virtual disk file.
22:43:43<@JAA>Your worker probably downloaded one or multiple large videos on the YouTube project, and even though it's no longer on your worker now, the virtual disk stays inflated due to that.
22:49:09<jasons>@jaa got it TY
22:49:09<jasons>is there any way to limit the Virt disk size during import as far as you know?
22:52:54<jasons>just read the wiki nvm ^
22:52:54<jasons>thanks again JAA