OpenSUSE MicroOS
21–30 of 35 posts
Re: OpenSUSE MicroOS
#22Love it, I just not gone use anything with BTRFS. Any chance I can get the same with ZFS instead?
> just not gone use anything with BTRFS. Why? (Legitimately asking, I haven't played around much with using different filesystems.)
Because of the nature of snapshots, the partition gradually fills up after big system updates. The usual `df` command is inaccurate with btrfs. Instead there's a set of btrfs specific tooling that you need to learn which can show the actual space in use.
Freeing up unused space from older snapshots also requires manual work. I often had to start removing the oldest snapshot and it'd turn out that it didn't free up enough space. Continue repeating the step of deleting oldest snapshot and hoping it frees up enough space.
It's possible the tooling is better/convenient now, but I prefer to stick with ext4 now.
Re: OpenSUSE MicroOS
#23This is awesome work on the part of the openSuse team! I have always liked the steady improvement openSuse and SuseEL have made over the last 5 years or so. While they are sort of the underdog still (just look at their numbers compared to RH), the fact that at least we have an alternative to RHEL in SEL for when companies require support contracts, is a huge benefit to users. I try not to talk about Canonical for...…
I assume you mean SLE instead of "SEL"?
Re: OpenSUSE MicroOS
#24Re: OpenSUSE MicroOS
#25So this is their alternative to fedora CoreOS and RH CoreOS ?
Re: OpenSUSE MicroOS
#26Earlier quoted context omitted.
A filesystem should systematically from the ground up be designed to be safe, specially one making the claims of BTRFS. BTRFS however went threw a number of cycles where it was considered save and then end up having issues. Of course there were always features considered unstable. It eating my own data, using non of the unstable features at the time. Maybe I could have recovered it but neither me nor the best IT pers…
Micro-OS uses BTRFS for operating system only. User data defaults to XFS. The transactional-server role mounts the operating system as read only with /var and /etc being virtual file systems that are committed each shutdown. You can use whatever you want including ZFS for your data.
Re: OpenSUSE MicroOS
#27Earlier quoted context omitted.
> just not gone use anything with BTRFS. Why? (Legitimately asking, I haven't played around much with using different filesystems.)
A filesystem should systematically from the ground up be designed to be safe, specially one making the claims of BTRFS. BTRFS however went threw a number of cycles where it was considered save and then end up having issues. Of course there were always features considered unstable. It eating my own data, using non of the unstable features at the time. Maybe I could have recovered it but neither me nor the best IT pers…
Re: OpenSUSE MicroOS
#28This is awesome work on the part of the openSuse team! I have always liked the steady improvement openSuse and SuseEL have made over the last 5 years or so. While they are sort of the underdog still (just look at their numbers compared to RH), the fact that at least we have an alternative to RHEL in SEL for when companies require support contracts, is a huge benefit to users. I try not to talk about Canonical for...…
I assume you mean SLE instead of "SEL"?