Concerns with BtrFS and ReFS
-
@scottalanmiller said in Concerns with BtrFS and ReFS:
@MattSpeller said in Concerns with BtrFS and ReFS:
We use EXT4 in our linux storage appliances - yet they seem to be pushing btrfs?
Synology and ReadyNAS seem to push BtrFS. It makes things easier for them.
For production, everyone I know pushes XFS. Fast and reliable. Pretty much the only big factors in storage.
XFS also has
xfsdumpandxfsrestore. It's not exactly the same as btrfs but it does give some backup ability. It also has dedupe but it's somewhat limited last I saw https://hooks.technology/2018/03/xfs-deduplication-with-reflinks/ -
@dafyre said in Concerns with BtrFS and ReFS:
@scottalanmiller said in KVM and Back Ups:
@fuznutz04 said in KVM and Back Ups:
@scottalanmiller said in KVM and Back Ups:
@fuznutz04 said in KVM and Back Ups:
@scottalanmiller said in KVM and Back Ups:
@fuznutz04 said in KVM and Back Ups:
For example, I had a developer fubar a server the other day. Completely unrecoverable. It was hosted at vultr, and I used their backup service. I was able to completely restore the server from their snapshot backup. That’s what I am after.
That's not crash consistent. So THAT level of backup KVM can do without anything special, it's just taking a snapshot of the storage. You have that with any system because it is done at the storage layer.
What tools can I use to do that (scheduled) with KVM on fedora?
If you want the Vultr style (or ProxMox risky style), you can do that right from the storage layer. So first determine the storage that you are going to use. ZFS, BtrFS, XFS, LVM, etc. Then you use the native tools (if you want) to snap it. Everything except the scheduling is just built in.
What is the latest recommendation for storage now? LVM?
LVM, ZFS, BtrFS are all fine. I've not used this but here is a script to do LVM backups...
I am going on record here as recommending that you stay away from BtrFS... far, far away. I can't say anything about ZFS as I haven't used that... But around my office, we avoid BtrFS like the plague.
I don't have any real world experience with data loss but I've read a lot of cases where people have had it. I think a lot of that might stem from people trying to use RAID 5/6 with it and that is somehow still unstable. I'm guessing that's why Red Hat dropped it and decided to make Stratis.
-
@stacksofplates said in Concerns with BtrFS and ReFS:
@dafyre said in Concerns with BtrFS and ReFS:
@scottalanmiller said in KVM and Back Ups:
@fuznutz04 said in KVM and Back Ups:
@scottalanmiller said in KVM and Back Ups:
@fuznutz04 said in KVM and Back Ups:
@scottalanmiller said in KVM and Back Ups:
@fuznutz04 said in KVM and Back Ups:
For example, I had a developer fubar a server the other day. Completely unrecoverable. It was hosted at vultr, and I used their backup service. I was able to completely restore the server from their snapshot backup. That’s what I am after.
That's not crash consistent. So THAT level of backup KVM can do without anything special, it's just taking a snapshot of the storage. You have that with any system because it is done at the storage layer.
What tools can I use to do that (scheduled) with KVM on fedora?
If you want the Vultr style (or ProxMox risky style), you can do that right from the storage layer. So first determine the storage that you are going to use. ZFS, BtrFS, XFS, LVM, etc. Then you use the native tools (if you want) to snap it. Everything except the scheduling is just built in.
What is the latest recommendation for storage now? LVM?
LVM, ZFS, BtrFS are all fine. I've not used this but here is a script to do LVM backups...
I am going on record here as recommending that you stay away from BtrFS... far, far away. I can't say anything about ZFS as I haven't used that... But around my office, we avoid BtrFS like the plague.
I don't have any real world experience with data loss but I've read a lot of cases where people have had it. I think a lot of that might stem from people trying to use RAID 5/6 with it and that is somehow still unstable. I'm guessing that's why Red Hat dropped it and decided to make Stratis.
yeah, there is a strong tendency with these kinds of filesystems to see them as "magic" and try to do things in ways you would never do with a different kind of FS, even though the risks are the same.
-
Had a customer this week have BtrFS cause all kinds of performance issues. Made a NAS unusable. Switched to ext4, everything was fine.
-
BtrFS is what Synology uses?
-
@FATeknollogee said in Concerns with BtrFS and ReFS:
BtrFS is what Synology uses?
It is what it optionally uses, yes.
-
@scottalanmiller said in Concerns with BtrFS and ReFS:
@FATeknollogee said in Concerns with BtrFS and ReFS:
BtrFS is what Synology uses?
It is what it optionally uses, yes.
I think that is the default FS?
-
@FATeknollogee said in Concerns with BtrFS and ReFS:
@scottalanmiller said in Concerns with BtrFS and ReFS:
@FATeknollogee said in Concerns with BtrFS and ReFS:
BtrFS is what Synology uses?
It is what it optionally uses, yes.
I think that is the default FS?
I believe that it is now. So people need to watch out for that, you rarely want it.
-
@scottalanmiller said in Concerns with BtrFS and ReFS:
@FATeknollogee said in Concerns with BtrFS and ReFS:
@scottalanmiller said in Concerns with BtrFS and ReFS:
@FATeknollogee said in Concerns with BtrFS and ReFS:
BtrFS is what Synology uses?
It is what it optionally uses, yes.
I think that is the default FS?
I believe that it is now. So people need to watch out for that, you rarely want it.
Can it be "easily" changed?
-
@FATeknollogee said in Concerns with BtrFS and ReFS:
@scottalanmiller said in Concerns with BtrFS and ReFS:
@FATeknollogee said in Concerns with BtrFS and ReFS:
@scottalanmiller said in Concerns with BtrFS and ReFS:
@FATeknollogee said in Concerns with BtrFS and ReFS:
BtrFS is what Synology uses?
It is what it optionally uses, yes.
I think that is the default FS?
I believe that it is now. So people need to watch out for that, you rarely want it.
Can it be "easily" changed?
Yes, if you catch it before you deploy.
-
@Obsolesce ReFS is unstable, unfortunately. I saw the case when after power outage ReFS volume become RAW...
