[07:39] <PowerUser76> Hi all, first time asking a question in these channels for a while. I'm running Lubuntu 18.04 (the 20 series of Ubuntu I've experienced issues with WiFi and have yet to find a good way to make Tracker behave itself) and have recently acquired a new-to-me laptop that has Windows 10 installed. I was wondering if someone could help me work out a step-by-step to image the existing Windows 10 install to a SSD, shrink the Win10 partition 
[07:39] <PowerUser76>  image my LUKS-encrypted Lubuntu to the free space on the aforementioned SSD then expand the LUKS partition to fill the remainder of the drive as the Lubuntu source is a 120GB SSD and then install/fix grub for a dual boot situation. I need Windows 10 for very very little. 'It's easier to install Windows 10 to the SSD then install Lubuntu and I'll just have to suck it up is an acceptable answer' Thank you in advance.
[23:10] <flosc> do files get lost when disk space is finished?
[23:11] <flosc> i am having this feeling, is it possible?
[23:11] <kc2bez> flosc: Do you mean when your drive is full?
[23:11] <flosc> i mean other files (that have nothing to do with the last operation)
[23:12] <flosc> yes, when no more free space
[23:12] <kc2bez> Sure, I guess all kinds of bad things can happen.
[23:13] <flosc> i don't understand if you are serious or joking
[23:13] <kc2bez> Anything that is in memory can't be written back to disk.
[23:13] <kc2bez> So if something is in use (even in the background) it could get corrupted.
[23:14] <flosc> suppose i have 400 mb free disk space, and i copy a 500mb file
[23:14] <flosc> then i get an error
[23:14] <flosc> operation cannot go forward
[23:15] <flosc> why should i worry about other files getting erased?
[23:15] <flosc> other files that have nothing to do with this operation
[23:15] <flosc> i dont understand
[23:15] <kc2bez> They may be in use by the system.
[23:16] <flosc> can you give me a probability?
[23:16] <flosc> i mean, am i probably ok or not?
[23:16] <kc2bez> Log files for example write all the time.
[23:17] <kc2bez> Well if your system is still running you might be ok
[23:17] <kc2bez> You should free some space while it is running
[23:17] <flosc> other files (not log files) should be ok?
[23:18] <kc2bez> I can't say that for sure.
[23:19] <flosc> so linux could delete a random file in this kind of situation?
[23:19] <kc2bez> If you free some space it might not be a bad idea to follow up with a fsck using a live disk.
[23:21] <flosc> but why would we want to have linuntu delete random files in this situation -  i mean wouldn't it be better to just stop (as it clearly is a mistake of the user)?
[23:21] <flosc> why would they do it like that?
[23:22] <kc2bez> It won't delete random files. It will only corrupt things that are in use.
[23:22] <kc2bez> Programs that are running have many files in use.
[23:23] <flosc> so reaching full capacity is always a big mistake?
[23:24] <kc2bez> It isn't good, no.
[23:24] <wxl> it can make some things just not work altogether
[23:26] <flosc> as of now, everything looks normal - i am just afraid i lost files or damaged the system
[23:28] <flosc> or "corrupted" - not sure what it means
[23:28] <kc2bez> corrupted = damaged
[23:29] <flosc> ok
[23:29] <kc2bez> Backups are a good thing to have if things look normal too.
[23:29] <flosc> yes but not my computer
[23:30] <flosc> that's why i am so worried
[23:31] <flosc> sorry , and thanks for your help
[23:31] <drea_mert> "as of now, everything looks normal" sounds like it is not too late for a backup ;-)
[23:31] <kc2bez> You are welcome, good luck flosc
[23:32] <flosc> thanks
[23:32] <flosc> ;-)