text
stringlengths
9
408
[1713.20 --> 1718.22] I'm curious about how I might go about upgrading here and prioritize backup ergonomics.
[1718.64 --> 1723.84] Right now, I don't have snapshots and I'm considering switching to ZFS or ButterFS.
[1724.34 --> 1724.76] Brackets.
[1724.98 --> 1725.80] Please don't fight.
[1725.80 --> 1731.74] How can I do this without purchasing a huge external hard drive to move everything over
[1731.74 --> 1733.02] whilst I build a new volume?
[1733.72 --> 1739.10] Also, NFS seems kind of antiquated and I'm wondering if this is the fastest way to mount
[1739.10 --> 1740.28] things over the network.
[1740.56 --> 1741.40] Is there a better option?
[1741.94 --> 1742.14] Hmm.
[1742.44 --> 1743.76] A little NFS hate there, huh?
[1744.08 --> 1745.28] No, I used to think that too.
[1745.74 --> 1748.68] You know, actually, that's sort of the beauty of NFS is that it's so simple.
[1748.82 --> 1750.14] It is extremely efficient.
[1750.14 --> 1753.14] But there are lots of ways to transfer files over the network.
[1753.62 --> 1754.10] It is old.
[1754.28 --> 1759.24] But, you know, one way you could look at old is tested, you know, reliable.
[1759.74 --> 1759.88] Right.
[1760.14 --> 1760.50] Boring.
[1761.06 --> 1762.40] And it's still in production.
[1762.72 --> 1764.28] So this is an interesting question.
[1764.38 --> 1768.24] It's like, I want to do something that's kind of risky, like switch to ZFS or ButterFS,
[1768.24 --> 1773.54] but I don't want to have to purchase an external hard drive to back everything up to.
[1773.94 --> 1777.08] And there's definitely part of me that's like, that's just not how it works.
[1777.24 --> 1781.06] I just want to say, you know, when you're messing with important data, you do kind of
[1781.06 --> 1787.48] want to externalize it because you can convert an extended four partition in place to ButterFS.
[1787.80 --> 1789.22] I've done it a couple of times, actually.
[1789.48 --> 1793.52] I was just having a conversation with somebody earlier this morning about just that thing.
[1793.52 --> 1794.98] And it'll work.
[1795.80 --> 1798.48] But I can't tell you it's risk free.
[1798.76 --> 1799.72] It is absolutely not.
[1800.60 --> 1802.26] And so I don't know how you get around that.
[1802.32 --> 1806.54] Do you have any ideas on maybe like pulling other disks on your LAN or I mean, something
[1806.54 --> 1807.24] out of the box?
[1807.88 --> 1808.28] Not really.
[1808.64 --> 1813.30] I mean, it's it goes back to that whole raid is not a backup type thing.
[1813.44 --> 1819.12] So even if you have a volume mirrored on two drives, unless that data exists somewhere
[1819.12 --> 1823.50] else as well, I would pretty much say that data doesn't actually exist at all.
[1823.72 --> 1827.10] Because if that mirror was to go pop, that data is gone.
[1827.30 --> 1830.18] So this is probably not what you want to hear.
[1830.66 --> 1835.58] But I would buy that external hard drive, mirror everything onto that external hard drive,
[1835.84 --> 1841.78] free up the two drives that you want to put ZFS or ButterFS onto, and then you should be
[1841.78 --> 1842.24] good to go.
[1842.76 --> 1844.28] That I completely agree with.
[1844.50 --> 1849.72] And now, as an aside, I want to just acknowledge that I do feel like we go about our daily lives
[1849.72 --> 1854.48] totally underutilizing lots of free space on the systems on our LAN.
[1854.64 --> 1858.10] And I know there's a couple of projects out there to crack this nut.
[1858.16 --> 1863.02] But if anybody listening is using something and has been using it for a little bit to take
[1863.02 --> 1867.54] advantage of maybe, you know, a machine over here that's connected via Ethernet that has
[1867.54 --> 1868.76] 120 gigs free.
[1868.76 --> 1871.08] And this machine over here that has a terabyte free.
[1871.18 --> 1874.20] And I have a machine over here that has 500 gigs and a machine over here that has four
[1874.20 --> 1874.98] terabytes free.
[1875.42 --> 1881.40] And I just need temporarily, I just need somewhere to store an extra seven terabytes a day.
[1881.44 --> 1887.30] It's like, could I pool everything somehow together and then somehow trust that this network
[1887.30 --> 1889.34] file system would work?
[1889.34 --> 1893.10] And you could, there's ways you could hack it together, especially with, you know, on
[1893.10 --> 1894.58] Linux with different mount points and all of that.
[1894.64 --> 1897.04] But I just don't, I just don't know of a solid one.
[1897.16 --> 1899.08] So selfhosted.show slash contact.
[1899.40 --> 1903.98] If anyone out there has something just out of curiosity, just be a fun thought experiment
[1903.98 --> 1905.82] to pool the storage on my network.
[1906.02 --> 1909.28] I don't think I'd use it for anything in production or for backup though.
[1909.64 --> 1910.70] I just don't think I would.
[1911.30 --> 1916.94] The next one comes from Mike and he's responding to a question I proposed last week about using
[1916.94 --> 1921.74] home assistant automations to cycle the charging of batteries on and off.
[1921.80 --> 1927.06] So that way devices don't sit at a hundred percent charged for days or they don't stay
[1927.06 --> 1928.20] at zero percent charge.
[1928.28 --> 1931.24] You may be something in the 40 to 60 percent range.
[1931.50 --> 1935.48] It'd be lovely to have an option to say today, I want everything charged to a hundred percent
[1935.48 --> 1938.50] because we're going on a road trip today and we need everything charged up.
[1938.70 --> 1942.90] And we got a couple ideas suggested and I liked Mike's and I wanted to give it a read
[1942.90 --> 1943.08] here.
[1943.12 --> 1946.92] He says, since there's really no out of the box solution right now, I'm going to
[1946.92 --> 1951.78] I'm creating a script that scrapes my laptop's battery info and then we'll publish it to
[1951.78 --> 1956.88] my home assistant's MQTT broker and then home assistant will act on that data to power
[1956.88 --> 1958.84] cycle my laptop's power supply.
[1959.26 --> 1960.10] Keep up the show.
[1960.22 --> 1960.48] Thanks.
[1960.62 --> 1962.48] And Mike, good idea.
[1962.56 --> 1963.66] That's great for the laptops.
[1963.98 --> 1970.28] The impossible nut that I'm trying to crack is like iOS devices, maybe even drone batteries,
[1970.62 --> 1975.40] things that don't even have an OS to scrape from, but you'd almost need like a time-based
[1975.40 --> 1975.86] system.
[1975.86 --> 1978.34] I suppose I'm still chewing on it right now.
[1978.46 --> 1984.86] I just kind of do it manually and it's not bad, but an example of a system that I probably
[1984.86 --> 1990.68] don't unplug and cycle the battery as frequently as I should are those fire tablets that are
[1990.68 --> 1991.84] plugged in and mounted on the wall.
[1992.02 --> 1995.68] I do power cycle them on occasion, but not regularly.
[1995.68 --> 2000.50] And with the home assistant app on Android, like there is something I could do there, but
[2000.50 --> 2002.46] I'm not looking for onesie twosie solutions.
[2002.58 --> 2004.86] I'm kind of looking for something that would work for everything.
[2005.20 --> 2010.62] I'm going to plug something that our community started about six months ago called Halcyon,
[2010.72 --> 2012.86] home assistant Linux companion app.
[2013.24 --> 2016.42] And there's a link in the show notes, halcyon.casa.
[2016.42 --> 2023.86] It's a Rust based application designed to run on Linux systems to present those metrics
[2023.86 --> 2024.56] to home assistant.
[2025.26 --> 2028.14] It's early days and it needs some love and some work still.
[2028.30 --> 2032.70] But if you're interested in that, check out, there's a dedicated channel in the discord
[2032.70 --> 2033.68] for Halcyon as well.