text
stringlengths
7
369
[1528.32 --> 1530.00] read a couple of times probably,
[1531.18 --> 1532.44] MergerFS does everything I need.
[1532.58 --> 1535.02] What are you hinting at there, Chris?
[1535.34 --> 1537.42] Well, so the word on the street,
[1537.54 --> 1539.18] although we'll see if this really pans out,
[1539.24 --> 1540.22] but the word on the street
[1540.22 --> 1542.02] is that we're going to see BcacheFS
[1542.02 --> 1543.62] hit the Linux kernel
[1543.62 --> 1545.22] in about the next six months or so,
[1545.30 --> 1546.06] maybe a little bit longer,
[1546.32 --> 1547.26] but it's nigh.
[1547.96 --> 1549.62] And the developer, Kent Overstreet,
[1549.72 --> 1551.22] recently said that his goal
[1551.22 --> 1553.74] is to essentially make a file system
[1553.74 --> 1554.92] that does just that.
[1555.00 --> 1555.68] It kind of replaces,
[1556.28 --> 1559.10] or it offers the advantages of XFS,
[1559.30 --> 1561.44] which XFS is a very solid,
[1561.54 --> 1562.92] very tried and true file system.
[1563.30 --> 1565.52] And with some of the benefits of ButterFS,
[1565.76 --> 1567.20] like copy on write,
[1567.40 --> 1568.74] snapshots, stuff like that.
[1568.90 --> 1569.32] That's pretty cool.
[1569.60 --> 1570.64] He was asked recently,
[1570.90 --> 1572.08] who's using BcacheFS?
[1572.24 --> 1573.64] Is anybody using it in production?
[1573.88 --> 1574.74] And he said, well,
[1574.78 --> 1577.20] I do know that a lot of video shops
[1577.20 --> 1579.74] that are dealing with multiple 4K streams
[1580.26 --> 1581.46] are using BcacheFS.
[1581.46 --> 1583.18] And it made me think,
[1583.28 --> 1584.04] like, I think every time
[1584.04 --> 1585.84] I've switched a major file system,
[1585.94 --> 1589.00] it's been to solve a performance problem
[1589.00 --> 1590.72] or a scalability problem.
[1591.20 --> 1593.30] Like, I really finally gave in
[1593.30 --> 1594.92] and tried ButterFS for real
[1594.92 --> 1597.42] when I needed to solve storage issues
[1597.42 --> 1598.30] on a Raspberry Pi,
[1598.42 --> 1599.92] and I just wasn't going to use ZFS.
[1600.26 --> 1601.30] I had no choice.
[1601.50 --> 1602.90] So I had to learn ButterFS,
[1603.20 --> 1603.92] and then I learned that
[1603.92 --> 1604.96] I actually liked it quite a bit.
[1605.08 --> 1606.46] But I only did it
[1606.46 --> 1607.76] when I was trying to solve,
[1607.80 --> 1609.02] like, a new problem.
[1609.02 --> 1611.18] And I just wonder, you know,
[1611.24 --> 1613.22] like, BcacheFS is going to come along one day.
[1613.78 --> 1614.76] It's going to be great,
[1614.84 --> 1615.64] no doubt about it.
[1615.74 --> 1619.70] But I'm kind of of the school of thought
[1619.70 --> 1620.82] that when it comes to my data,
[1621.44 --> 1622.98] I like to give that stuff years.
[1623.34 --> 1624.74] You know, years of cooking,
[1625.06 --> 1626.80] years of other people using it in production.
[1626.96 --> 1627.78] That's just one area
[1627.78 --> 1630.12] where I'll kind of tap the brakes a little bit.
[1630.22 --> 1631.22] And so that's why it took me a while
[1631.22 --> 1632.84] to come around to ButterFS,
[1633.00 --> 1633.40] to be honest.
[1633.94 --> 1636.24] That's really what I love about ZFS.
[1636.24 --> 1637.80] I know it has a bit of a learning curve
[1637.80 --> 1639.52] and a bit of an aura around it,
[1639.72 --> 1642.10] but what are you laughing at?
[1642.12 --> 1642.58] An aura.
[1642.92 --> 1644.06] I think a bit of an aura
[1644.06 --> 1645.08] is a funny way to put it.
[1645.32 --> 1645.48] Yeah.
[1645.84 --> 1646.44] But it does.
[1646.78 --> 1648.18] I mean, just listen to you and Alan
[1648.18 --> 1649.38] back in the day on TechSnap.
[1649.50 --> 1650.60] Like, you made it sound like
[1650.60 --> 1652.30] this massive, complex beast,
[1652.34 --> 1653.02] and actually it's not.
[1653.10 --> 1655.24] It's just two drives in a mirror, right?
[1655.38 --> 1656.18] I mean, that's it.
[1656.22 --> 1657.06] That's what I use anyway.
[1658.56 --> 1658.88] Yeah.
[1659.32 --> 1659.82] It does.
[1659.92 --> 1660.80] It can be very complex,
[1661.02 --> 1661.68] but yeah.
[1662.58 --> 1663.72] Not so bad, really.
[1663.72 --> 1666.10] So I'm glad that you got it found.
[1666.26 --> 1667.72] I'm sorry there was actually the drive
[1667.72 --> 1668.54] and not the cable, though.
[1668.56 --> 1669.26] That does stink.
[1669.68 --> 1670.52] Well, so this presents
[1670.52 --> 1671.56] an interesting opportunity
[1671.56 --> 1672.92] for content, actually.
[1673.18 --> 1675.10] So this will be the first shut drive
[1675.10 --> 1676.20] that I've had fail on me.
[1676.82 --> 1679.00] I don't have the plastic casing anymore.
[1679.12 --> 1679.78] I chucked that out
[1679.78 --> 1680.90] as a matter of principle.
[1681.70 --> 1682.80] So I'm really interested
[1682.80 --> 1683.68] to see what happens
[1683.68 --> 1685.66] when I send this 12 terabyte drive,
[1685.72 --> 1687.40] which is only about 15 months old,
[1687.50 --> 1688.58] back to Western Digital.