On 03/05/2019 08:09, Borja Marcos via freebsd-stable wrote:
The right way to use disks is to give ZFS access to the plain CAM devices, not thorugh some so-called JBOD on a RAID controller which, at least for a long time, has been a *logical* “RAID0” volume on a single disk. That additional layer can completely break the semantics of transaction writes and cache flushes. With some older cards it can be tricky to achieve, from patching source drivers to enabling a sysctl tunable or even flashing the card to turn it into a plain HBA with no RAID features (or minimal ones).
Oddly enough I got bitten by something like this yesteray. I have a machine containing an HP P400 RAID controller, which is nice enough, but I run ZFS so I have made the drives all into RAID-0 as being as close as I can get to accessing the raw SAS drives.
BSD seems them as da0, da1, da2, da3 - but the RAID controller oly presents one of them to the BIOS, so my booting has to be all from that drive. This has been da0 for as long as I can remember, but yesteday it decided to start using what BSD sees as da1. Of course this is very hard to recognise as da0 and da1 are pretty much mirrors of each other. Spent a long time trying to work out why the fixes I was applying to da0 were not being used at boot time.
( Having to use Windows XP to talk to the iLo due to browsers dropping support for the old ciphers doesnt help either, what do other people with oldish HP hardware do about this ? I know its off topic, but theres a lot of it out there... )
-pete. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
