Red Hat Enterprise Linux 7.4 released
Red Hat Enterprise Linux 7.4 offers new automation capabilities designed to limit IT complexity while enhancing workload security and performance for traditional and cloud-native applications. This provides a powerful, flexible operating system backbone to address enterprise IT needs across physical servers, virtual machines and hybrid, public and multi-cloud footprints." See the release notes for more details.
Posted Aug 1, 2017 18:55 UTC (Tue)
by ubhofmann (subscriber, #47368)
[Link] (20 responses)
"The Btrfs file system has been in Technology Preview state since the initial release of Red Hat Enterprise Linux 6. Red Hat will not be moving Btrfs to a fully supported feature and it will be removed in a future major release of Red Hat Enterprise Linux."
Does anybody know the reasons for this decision?
Posted Aug 1, 2017 19:43 UTC (Tue)
by dany (guest, #18902)
[Link] (15 responses)
Posted Aug 1, 2017 19:54 UTC (Tue)
by jhoblitt (subscriber, #77733)
[Link] (3 responses)
Posted Aug 1, 2017 20:01 UTC (Tue)
by Paf (subscriber, #91811)
[Link]
Posted Aug 2, 2017 9:50 UTC (Wed)
by danieldk (subscriber, #27876)
[Link] (1 responses)
Posted Aug 2, 2017 20:53 UTC (Wed)
by nix (subscriber, #2304)
[Link]
Posted Aug 1, 2017 22:51 UTC (Tue)
by flussence (guest, #85566)
[Link] (10 responses)
It's an okay FS on my desktop, and I guess it works for Facebook where they can afford to do RAID6 at the building level, but this sucks hard for anyone wanting to use it on a normal-sized server.
Posted Aug 1, 2017 23:15 UTC (Tue)
by neilbrown (subscriber, #359)
[Link] (8 responses)
That may be a good reason to disable btrfs RAID support. It doesn't seem like a good reason to dump btrfs altogether. If you want RAID6, use md/raid6 (or "hardware RAID") underneath btrfs.
Posted Aug 2, 2017 2:18 UTC (Wed)
by smckay (guest, #103253)
[Link]
I know the answer to exactly zero of these questions but I suspect their answers are relevant to RH's decision to dump btrfs.
Posted Aug 2, 2017 21:25 UTC (Wed)
by wx (guest, #103979)
[Link] (6 responses)
No, don't do that.
In an md raid, a disk failure will cause the contents of the _entire_ disk to be resynced as md does not differentiate between used and unused disk space - only the filesystem one layer up has that info. With today's disks a resync takes ages and puts a lot of stress on the other disks in the array significantly increasing the risk of additional drive failures in the worst possible situation: in an already degraded state.
Customers who understand and care about these issues are already using ZFS (not necessarily under Linux) and have no reason to switch. At the end of the day there's just no business case for Red Hat in btrfs besides catering to customers who absolutely insist on using Linux but are afraid of legal trouble wrt the CDDL (which Canonical decided would not happen a while back and which hasn't happened to Canonical yet, at least not on public record).
Posted Aug 2, 2017 23:37 UTC (Wed)
by quotemstr (subscriber, #45331)
[Link] (4 responses)
Posted Aug 3, 2017 8:30 UTC (Thu)
by Wol (subscriber, #4433)
[Link] (3 responses)
md-raid works at the partition level. It knows nothing, cares nothing, about the file system above it so even if you sent a discard to md it wouldn't have a clue what to do with it.
Cheers,
Posted Aug 8, 2017 15:39 UTC (Tue)
by meuh (guest, #22042)
[Link] (2 responses)
If FS initiate TRIM request (discard), beside forwarding the request to HDD, MD can record that one or more stripe are not storing useful information any more (such flag would be invalided by a write on the stripe). Going to the status of each stripes during recover, MD can process only the useful part of the RAID array.
Posted Aug 9, 2017 7:45 UTC (Wed)
by matthias (subscriber, #94967)
[Link] (1 responses)
Posted Aug 13, 2017 14:47 UTC (Sun)
by Wol (subscriber, #4433)
[Link]
Yes, it might be a nice addition, but it's added complexity, and it would need somebody to step up to the plate and implement it (plus it would require mucking about with the layout - there may or may not be somewhere to store the fact that stripes are empty or in use).
Cheers,
Posted Aug 3, 2017 8:29 UTC (Thu)
by Wol (subscriber, #4433)
[Link]
But firstly if the failed disk is even partially recoverable, that will massively reduce the stress on the array. (As always, we need developers - getting that to work seamlessly is on the hit list of jobs needing doing :-(
Secondly, if you've been scrubbing the array like you're supposed to, you know very well that the array is good and will have no trouble coping with a rebuild.
And thirdly, how on earth is ZFS supposed to know what is on the failed disk, other than by doing a scan of the rest of the disks, stressing them in exactly the same way as md-raid!?
(And yes, md-raid does scan the entire underlying partition like you suggest, but there are easy - if controversial - ways round that.)
Cheers,
Posted Aug 21, 2017 17:05 UTC (Mon)
by anton (subscriber, #25547)
[Link]
Posted Aug 2, 2017 6:53 UTC (Wed)
by richard77 (guest, #117898)
[Link] (1 responses)
Posted Aug 3, 2017 4:14 UTC (Thu)
by joib (subscriber, #8541)
[Link]
phoronix (yes, sigh), reports that RH is developing stratis, which is some kind of management daemon + API/CLI tying together LVM + XFS. Perhaps the Permabit stuff too one day. http://phoronix.com/scan.php?page=news_item&px=Strati...
Posted Aug 2, 2017 12:55 UTC (Wed)
by cesarb (subscriber, #6266)
[Link]
A comment at HN explains the probable reason: https://news.ycombinator.com/item?id=14909843
Posted Aug 3, 2017 19:11 UTC (Thu)
by jhhaller (guest, #56103)
[Link]
But, having put together a BTRFS RAID 5, I wouldn't recommend it, even if the data loss problems get fixed. Scrubbing a large RAID 5 filesystem is interminably slow. BTRFS is happy to let all writes go to RAM until a flush is requested. At that point, the system comes to a grinding halt while all that data is written out to the drives.
Posted Aug 2, 2017 6:01 UTC (Wed)
by imgx64 (guest, #78590)
[Link] (1 responses)
Posted Aug 2, 2017 10:12 UTC (Wed)
by evad (subscriber, #60553)
[Link]
Posted Aug 2, 2017 21:51 UTC (Wed)
by kbrantley (guest, #70638)
[Link] (2 responses)
On the authentication front I get it; they're really pushing IdM and rightfully so (anonymous LDAP access isn't enough these days, and IdM does all of the security for you out of the gate). But, there are a lot more uses of OpenLDAP than just identity management...
Posted Aug 3, 2017 0:02 UTC (Thu)
by evad (subscriber, #60553)
[Link] (1 responses)
Posted Aug 28, 2017 20:43 UTC (Mon)
by dpal (guest, #88301)
[Link]
Let me clarify last comment a bit.
Thank you,
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Wol
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Wol
Btrfs has been deprecated?
Wol
We recently played around with Btrfs and RAID1, and what we saw looked somewhat rough (it's relatively easy to get the filesystem into an unrecoverable read-only state; then you have to copy the data over), but we did not experience data loss. You can read about our experience here.
Btrfs has been deprecated?
Btrfs has been deprecated?
https://www.redhat.com/it/about/press-releases/red-hat-ac...
Btrfs has been deprecated?
Btrfs has been deprecated?
Btrfs has been deprecated?
Red Hat Enterprise Linux 7.4 released
Red Hat Enterprise Linux 7.4 released
OpenLDAP server deprecated?
OpenLDAP server deprecated?
OpenLDAP server deprecated?
Red Hat does not offer 389-ds as a supported option. The bits are there in RHEL and used and supported in context of IdM or Red Hat Directory Server product but not if installed by themselves.
If you need a solution that serves your identity management needs - IdM is the one. It is included with RHEL subscription without extra cost. If you need a directory server as a back end for your applications Red Hat Directory Server is the way to go. It is a separate product with a price tag. If you need a simple LDAP server for development or testing in many cases IdM can fit the bill. If you want an LDAP server for back end for an application and plan to use it in production you probably want a dedicated dev/test RHDS environment anyways. If you want something to play with you can use 389-ds package on RHEL which will not be supported but will work or you can use CentOS in this case. In general there is plenty of options for every taste. If some use case is missing or some of the assumptions about the use of LDAP server functionality is wrong, Red Hat will be grad to hear your feedback, just open a support case or post a comment here.
Dmitri