[14:54] How can i solve this issue: transcode: 0001: Unable to open libx264 encoder [14:59] raidghost: to begin with, by defining its context. [15:01] blackflow: tvheadend is using it [15:05] !details | raidghost [15:05] raidghost: Please elaborate; your question or issue may not seem clear or detailed enough for people to help you. Please give more detailed information; for example, we might need errors, steps, relevant configuration files, Ubuntu version, and hardware information. Use a !pastebin to avoid flooding the channel. [16:49] teward: Yes (to the question about LVM2 in case that was you). [17:41] teward: you mean shrink an actual partition (a "PV"), and not an LV? [20:01] Anyone knows if it's now okay to restart systemd-journald, in bionic? systemd version is 237, and if I'm not mistaken, this was supposedly fixed in v235? https://github.com/systemd/systemd/issues/6620 [20:02] tl;dr restarting journald nuked open FDs so services were busted.... [20:02] I can't TIAS because I don't have proper test coverage for all open FD cases.... [20:05] and according to this comment in that bug report, it's still not okay to stop journald, but it's okay to restart, as long as services handle EPIPE properly? gah..... https://github.com/systemd/systemd/issues/6620#issuecomment-325947296 [20:06] to be on the safe side, as I need this for configuration automation, I'll just ban modifying journald.conf at run time. [20:45] ahasenack: i solved it but I had to GUI it to find a tool that would work. I shrunk the LV down, and then was trying to shrink the PV to free up some space for a dual boot. [20:45] turns out the system doesn't like that muchl [20:46] (ended up having to borrow Kubuntu's kvpm to get it to 'just work' >.>) [20:55] teward: I generally just use "pvresize --setphysicalvolumesize 1234S" and that makes it easy to resize the containing partition to the same number of sectors [20:56] note that is 1234 S (for Sectors) [20:57] TJ-: i tried that, the underlying LVM system started freaking for some reason about "real size being larger than specified size" [20:57] *shrugs* [20:58] teward: did you check that no LVs were using the extents that were being lost? [20:59] yep [20:59] TJ-: ultimately, it's fixed now so it's more idle musing why it wouldn't work as is [21:00] *shrugs* [21:00] yeah, I've never had an issue. I check with "pvdisplay -m" [21:03] TJ-: the other lesson to learn from this would be "Don't try and do this when you're dead tired" because that may have been a factor [21:03] but meh [21:03] yes, I agree there 1*10^9 :) [21:04] well before I mess with this more, I think i'mma have to backup the server anyways (full disk image, anyone? >.>) [21:14] teward: I've got an empty 8TB archive drive sitting about but can't resolve to use it because there still don't seem to be any file-systems designed to work with shingled drives, despite some earlier experiemental work Ted T'so did on ext4. Grrrr. [21:17] heh === ChunkzZ is now known as heathsfriend === heathsfriend is now known as Chunky === Chunky is now known as ChinkzZ === ChinkzZ is now known as ChunkzZ