antongribok

It's funny that you link to a comment from 6 years ago. Just a month after that there was a pretty big bug in ZFS that corrupted data.

https://github.com/openzfs/zfs/issues/7401

Corresponding HN discussion at the time: https://news.ycombinator.com/item?id=16797644

I know it's not the same thing, but Quickemu happily works over SSH too.

Run it on a remote system via ssh, and it will "X-Forward" the Qemu console on my local Wayland session in Fedora.

First time I ran it, thinking I was doing a headless mode, and it popped up a window, was quite surprising. :)

If you are only using those two tools, then you only have a system for replication (and snapshots), but not a backup system.

If there is a data corruption bug in ZFS, it will propagate to your remote and corrupt data there.

I hope you have something else in place besides those two tools.

Galaxy S10+ came out in 2019. I believe this was the last flagship to have a microSD card slot.

Sage is one of the nicest, down to earth, super smart individuals I've met.

I've talked to him at a few OpenStack and Ceph conferences, and he's always very patient answering questions.

Not sure about putting DBs on CephFS directly, but Ceph RBD can definitely run RDBMS workloads.

You need to pay attention to the kind of hardware you use, but you can definitely get Ceph down to 0.5-0.6 ms latency on block workloads doing single thread, single queue, sync 4K writes.

Source, I run Ceph at work doing pretty much this.

It's been a while since I've done some benchmarks, but it can definitely do 40MB/s sustained writes, which is very good given the single 1GbE links on each node, and 5TB SMR drives.

Latency is hilariously terrible though. It's funny to open a text file over the network in vi, paste a long blob of text and watch it sync that line by line over the network.

If by "rub" you mean scrub, then yes, although I increased the scrub intervals. There's no need to scrub everything every week.

I run Ceph on some Raspberry Pi 4s. It's super reliable, and with cephadm it's very easy[1] to install and maintain.

My household is already 100% on Linux, so having a native network filesystem that I can just mount from any laptop is very handy.

Works great over Tailscale too, so I don't even have to be at home.

[1] I run a large install of Ceph at work, so "easy" might be a bit relative.

I work at a Fortune 50 company and the pendulum for us has already swung back around. 5 years ago it was all "move everything to public". Now, we're building a bunch of on-prem infra and there are huge projects to move workloads back.

For us, on-prem is about half the cost for compute and storage vs public cloud.

Reading this for some reason reminded me of the Virtual Barber Shop:

https://m.youtube.com/watch?v=IUDTlvagjJA

(Use headphones and close your eyes.)

I posted this and can answer your question.

I don't live in UK, and don't generally read the local news section of BBC, so this was displayed on the side when I was reading a story about the volcanic activity in Iceland.

I clicked on the story, because it was about electric busses, a subject I'm interested in, since we don't have any where I live.

After clicking on the story, I was a bit disappointed with the lack of detail.

I decided to post here, because I figured if it got any traction, someone on here would post a bit more detail.

The top comment on here currently is exactly what I was hoping to see, and I'm glad I posted the story.

I love my LG washer/dryer combo. Yes, it takes a bit longer, but it's half the work from my point of view.

I only load and unload clothes once (not twice).

I only program a machine once (not twice).

One big feature my LG has is it will keep rotating the drum a half a turn every few minutes, so you can take the dry, clean clothes out much, much later, and they will not be wrinkled.

As others have said, if you're limited on space in your house it's a bonus. In my case I converted the space that would have been taken up by a second unit stacked vertically into large storage area with shelves.

Aren't we already seeing rent prices going down?

I live in the city with excellent reception and it takes me less than a day to make enough money to afford the latest flagship phone, yet I hate being forced to upgrade my phone.

I like my current S10+ which is 3.5 years old, and the fact that it's no longer on the latest Android version is completely ridiculous.

I don't even know what I can upgrade to if I want to keep using my microSD card and my wired headset.

This reminded me about the actual house used in the movie. There is a decent article on it:

https://www.fancypantshomes.com/movie-homes/the-real-life-ho...

I've never had data loss with either ZFS or btrfs.

For me on Fedora, uptime is better and maintenance overhead is lower on btrfs.

I guess I meant it as having a separate repair tool, but yes, you're of course correct.

To me it was always weird to not have a separate tool for being able to do an offline ZFS repair.

With regards to data corruption, I mean, this is exactly why I moved to btrfs, because it's able to catch bit rot same as ZFS.

I think ultimately this is why ZFS data corruption bugs always are such a big deal... It's because in a lot of tech circles ZFS is put on this infallible pedestal where it can never do any harm to your data.

The packaging was a major reason for switching to btrfs. I run sudo dnf upgrade and that's it, my system is upgraded. Zero issues ever. With ZFS I had to pin to older kernel versions, not to mention a bunch of manual steps and cleanup after any major version upgrade (every 6-12 months).

Re btrfs raid 5/6, yes everyone knows about this, and this is why I have it only on my backup system. My primary data which holds 15TB of family photos and videos is on raid 1. The offsite is there only for the time my house burns down.[1]

[1] I watched my neighbor's house go up in flames 2 years ago, and it finally got me going on setting up remote backups. The fire spread to 3 other houses, and everything happened very, very quickly. No one got hurt, but multiple families got displaced for more than a year. Besides having backups , it's also a good reminder to have adequate insurance. One neighbor did not.

Btrfs does not have native encryption.

I use LUKS / dm-crypt on entire drive partitions. Did that with ZFS too, and by the time ZFS got this feature I was already planning my migration to btrfs.

I like encrypting with LUKS, because I can have a drive configured with mine and my wife's password. Either one of us can take that drive, plug it in, and Gnome will put a nice graphical prompt asking for a password, then decrypt the drive and mount the filesystem.

If I get hit by a bus, LUKS makes it much easier for my family to get access to important data without having to have that data sit around somewhere in plaintext.

Yeah, of course you should be doing that. I was just trying to say that people shouldn't pretend like having snapshot-based, filesystem-level replication alone (which can be a very efficient way of replicating data changes) is a good backup strategy.

The reason, and the difference, is that all these other filesystems have check and repair (and sometimes multiple) tools.

Please correct me, but ZFS has none.

For me it was the previous data corruption bug [1] that killed any enthusiasm for ZoL. After that annoyances like the caching issues you mention and the constant kernel upgrades breaking DKMS on Fedora just stopped being worth it for me.

I finally moved to btrfs earlier this year, and so far I'm glad I did.

I run raid1 on my primary array, and raid5 on my off-site backup array at my mom's apartment connecting with Tailscale.

Replication is with rsync and borg, not snapshots.

Yes, it's more painful to replace disks after a failure, but once you get a bit used to it, it's really no big deal.

On my main workstation/laptop the dedupe and compression work much better than my experience with ZFS.

[1] https://news.ycombinator.com/item?id=16797644

Here's an example of a nasty data corruption bug in ZFS from not that long ago: https://github.com/openzfs/zfs/issues/7401

Corresponding HN discussion at the time: https://news.ycombinator.com/item?id=16797644

This is why you should always have proper backups, and a great reminder that snapshots are not backups.

Thanks for that!

This reminded me how as a kid for about a decade I used the CDROM burning software Nero Burning ROM [0] without any idea that it was a reference to the Roman emperor Nero [1] and the Great Fire of Rome [2] until my mom saw me using it and educated me.

[0] https://www.nero.com/eng/products/nero-burning-rom/

[1] https://en.wikipedia.org/wiki/Nero

[2] https://en.wikipedia.org/wiki/Great_Fire_of_Rome

I use Paperless with Tailscale.

On my mobile I use Firefox, and for me it works great.

I traveled for a month in Europe this summer and never had any issues.

Snapshots is not a backup.

Since others are suggesting x86 instead of ARM, I highly recommend an LG Gram (either 16 or 17) that comes with an 80 Wh battery, and stock Fedora.

With Power Profiles in Gnome set to "Power Saver" you'll easily last more than a day. Standby power is excellent.

LG has other, smaller models as well, but I think they come with smaller batteries that aren't quite as good a balance of power and weight.

My father said: We're not rich enough to by cheap things.

I wonder if the original saying has been translated multiple times before getting to English.

I really like the LG Gram series.

I had one of the first generation Gram 17, and this Jan got the 16 (same 16:10 resolution as the 17).

My wife has been using Gram 14, and she really likes it.

All 3 laptops have been exclusively on Fedora. Zero issues.

I really like the screen, the weight, and the excellent battery. On the older model, sleep was not very good in terms of using low power, but with the two latest (last year) models, sleep is ultra low power. Of course the massive battery helps a lot.

Trackpad is great, keyboard is great. It's awesome to have dual NVMe slots, although not so great to have non-upgradable RAM.

I can do a full work day on battery charged to 80%, including multiple long Zoom calls.