[14:54] <raidghost> How can i solve this issue: transcode: 0001: Unable to open libx264 encoder
[14:59] <blackflow> raidghost: to begin with, by defining its context.
[15:01] <raidghost> blackflow: tvheadend is using it
[15:05] <blackflow> !details | raidghost
[16:49] <vlt> teward: Yes (to the question about LVM2 in case that was you).
[17:41] <ahasenack> teward: you mean shrink an actual partition (a "PV"), and not an LV?
[20:01] <blackflow> 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] <blackflow> tl;dr restarting journald nuked open FDs so services were busted....
[20:02] <blackflow> I can't TIAS because I don't have proper test coverage for all open FD cases....
[20:05] <blackflow> 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] <blackflow> 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] <teward> 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] <teward> turns out the system doesn't like that muchl
[20:46] <teward> (ended up having to borrow Kubuntu's kvpm to get it to 'just work' >.>)
[20:55] <TJ-> 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] <TJ-> note that is 1234 S (for Sectors)
[20:57] <teward> TJ-: i tried that, the underlying LVM system started freaking for some reason about "real size being larger than specified size"
[20:57] <teward> *shrugs*
[20:58] <TJ-> teward: did you check that no LVs were using the extents that were being lost?
[20:59] <teward> yep
[20:59] <teward> TJ-: ultimately, it's fixed now so it's more idle musing why it wouldn't work as is
[21:00] <teward> *shrugs*
[21:00] <TJ-> yeah, I've never had an issue. I check with "pvdisplay -m"
[21:03] <teward> 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] <teward> but meh
[21:03] <TJ-> yes, I agree there 1*10^9 :)
[21:04] <teward> well before I mess with this more, I think i'mma have to backup the server anyways (full disk image, anyone?  >.>)
[21:14] <TJ-> 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] <teward> heh