=== NeoFAT32_ is now known as NeoFAT32 === arraybolt3_ is now known as arraybolt3 === arraybolt3_ is now known as arraybolt3 [02:37] !ping [02:37] pong! [02:37] bang! [02:37] * arraybolt3 falls over dead [02:39] "the latency of this corpse is..." [02:40] Just kidding. [02:40] * arraybolt3 goes back to setting up a ZFS pool [02:41] it is just zpool create really :D [02:43] Alright that was pretty easy. [02:43] i hope it was z2 [02:44] good morning [02:44] ZFS mirrored array across two 6TB disks. [02:44] Now I just need to know if checksumming is enabled or not. [02:46] i made a 4 x 4TB one downstairs under XCP-ng, for a test run [02:46] Does anyone know how to query whether checksumming is enabled or not on ZFS? [02:46] It is enabled by default [02:46] Oh good. [02:47] Now I just need to find out how to make it reliably automount. [02:47] (If it doesn't automount by default already.) [02:47] Yo uh should enable compression [02:48] That's not enabled by default [02:48] zstd probably [02:48] It should auto mount on Ubuntu at least [02:48] It does automount! Woot! [02:49] I don't need compression or dedup I don't think, this is just for backups, and *maybe* some VMs. [02:49] For VMS compression is good [02:49] So make sure to enable it there [02:49] You can enable it for subvolumes [02:50] Oh it is good? OK, then I guess I'll do it. [02:50] For compressed backups it is kind of useless of course [02:50] And I technically have enough RAM to dedup... but I don't want to hurt performance too bad, nor do I want 30 of my 32 GB to be eaten for that. [02:50] But for VMs it is actually faster [02:50] Do not dedup if you don't absolutely have to [02:51] weird, i had always been under the impression that compression was an unnecessary risk [02:51] It really eats ram like hell [02:51] There really is no risk in compression:) [02:52] i think there was back in win9x days [02:53] Windows 2000, 7-zip seemed to eat data rather than compress it. [02:53] Anything else I should enable? Just put compression into action. [02:53] And also disabled drive spindown. [02:53] not really. the other defaults are fine [02:53] if you plan to use VMs make sure to create a thin pool [02:54] I don't know what a thin pool is... [02:54] (thin provisioning) [02:54] Oh for the VM disk images? [02:54] Yeah that's easy. GNOME Boxes and VirtualBox both do that by default. [02:54] oh ok [02:54] well i use my VMs directly on a zfs volume :) [02:54] (I'm a total newbie to ZFS, I just now started playing with it because it appeared to be safer for my data than a pure RAID1.) [02:55] if you use qcow images for example they support compression too [02:55] so you dont need ZFS fot that [02:55] i dont know how virtualbox handles it [02:55] This is mainly my backup solution. [02:55] I intend on throwing any important disk images and the like onto this. [02:56] That way I don't lose them, even if one drive dies. And I also intend to compress them, encrypt, and upload to the cloud. [02:56] I just figured I could also use the spare free space to hold VMs for my work. [02:56] on *that* connection? :D [02:56] if you only store compressed files you can disable compression of course [02:56] but even then you will not see much performance impact with zstd [02:56] it really does not need much [02:57] daftykins: Hey, it doesn't need to go fast. It's just another layer of security. [02:58] for a pure backup drive you could have just used mdadm of course [02:58] but ZFS is fun to play with [02:58] mdadm won't catch silent data corruption in a RAID1. [02:58] ZFS will. [02:58] true [02:59] it does at least does a verification from time to time :D [02:59] -does [03:00] NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT [03:00] tank 58.2T 14.7T 43.5T - - 10% 25% 1.00x ONLINE - [03:00] i can do some more backups [03:01] oof [03:01] Holy... smoke. What on earth. [03:01] wanna swap with my 256GB ssd lol? [03:02] let me think.. no :D [03:02] haha [03:03] * arraybolt3 has a 120 GB SSD in one of my laptops [03:03] arraybolt3: well they're not great 'cloud backups' if they didn't make it :D [03:03] my ubuntu runs from a 120GB SSD [03:03] i better get to bed, ttfn \o [03:03] nn daftykins === ledeni_ is now known as ledeni [04:21] !ping [04:21] pong! [04:42] Hi, why are viewers like okular and text editors like kate using CPU even when minimized or on another virtualdesktop, when the screen is locked and the display is off? In ubuntu/linux Is that not an option for an app to notify the OS something like, "I'm going to sleep, wake me in one of the following circumstances: data to port N, action on my [04:42] window."  ? [06:59] On GNOME or KDE do idle GUI programs need to be awakened by the kernel in order to confirm that they have no tasks to do? [08:19] !ping [08:19] pong! [08:19] (Internet being unstable, testing a lot.) [09:23] Guest99, monitor the CPU/RAM usage for a while with a background script while the PC is 'sleeping'/locked and send the result to the maintainers. [09:23] That's what i would do. [09:24] i think the editor is calculating bitcoins for lotuspsychje to buy a new Ubuntu bluray. [09:24] :P === EriC^ is now known as EriC^^ [13:51] and so !lunar is now active to use [13:51] tnx for the addy! [13:59] BrassPin88: we discussed before, #ubuntu isnt a chat to bother users with offtopic, please respect that [14:03] lotuspsychje sorry, have a pleasant day. [14:08] Alright so I set up the ZFS mirror last night, copied my data to it, everything seemed to work, and then I had a power outage. The data still appears to be there (it was hours after the transfer that the power cut out), how likely is it that the data survived intact do you guys think? [14:08] (I'm about to SHA256SUM all of it for good measure.) === ledeni_ is now known as ledeni [16:53] arraybolt3: I don't see why it would be a problem (generally speaking, file system issues after a power outage happen to files/directories that are being written to at that moment) [16:55] That's what I'm hoping. [18:00] arraybolt3: why not scrub? [18:04] murmel: I don't know if that will tell me if the data on the array perfectly matches the data from the original disk or not. [18:05] arraybolt3: I guess, but at the same time, shouldn't you first make sure that the transfer was okay? (I mean before the outage?) [18:06] i mean something like rsync ;) [18:06] Eh, not a horrible idea, though I think pcmanfm-qt uses rsync in the background, not entirely sure though. [18:07] arraybolt3: oh, yeah with transfers like these, I rather use rsync directly, so I can read the output etc [18:11] I'm scared of rsync :P [18:11] oO [18:11] arraybolt3: what's so scary? [18:12] Tons of command-line switches that do I-dont-know-what. [18:12] that's what manpages are for [18:12] cp is just, take data, plop copy elsewhere. [18:12] arraybolt3: yeah and you have no idea, if source == target [18:13] JanC: I KNOW. But I have tons of other stuff I'm doing, I have to find time to learn stuff like that. [18:13] and if you regularly have to do the same and don't want to look up the options every time, make an alias or so [18:13] I can definitely recommend the -v switch xD [18:14] (I meant that in a funny way, not a mean one.) [18:15] murmel: Which does...? [18:15] Verbose? [18:15] on a system with a GUI, there is also grsync [18:15] arraybolt3: yes [18:17] oh wow that's quite the handy gui, if someone wants to use rsync [18:17] Same reason I don't hardly use tar, too many bells and whistles. [18:18] eh, it's just getting used to it [18:19] ideally the defaults are all you need by default :) [18:21] and like I said: when you need to do the same from time to time, make an alias (or a bash function or script when it's more complicated) [18:21] Yeah, I can do all that. Just need to find time. [18:23] I mean you can always find time if you want to ;) reading the rsync manpage takes maybe 10 mins or so? write out the options you want/need [19:48] Alright, all my file verification succeeded and all the data was intact. Woot! [19:48] That took *forever*, but hey, it was 2.2 TB, what did I expect? [21:10] UWN: Issue760 released to our viewing public: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue760 :D === arraybolt3_ is now known as arraybolt3