> Those changes weren't managing to get flushed to the old disk with the now-RO filesystem, but they were apparently hanging out in buffers and were available f

> Those changes weren't managing to get flushed to the old disk with the now-RO filesystem, but they were apparently hanging out in buffers and were available for reading... or something? That makes sense, right? This is a fun issue that I've run into before. We had remote FreeBSD 11 boxes using ZFS. ZFS said the pool was fine, OS said the drive was fine, writes appear to work, but they are only going to RAM and are lost on reboot (which happens once you run out of memory, the box locks up, and someone on-site pulls the plug). Dealing with drives going bad with no indication is an interesting problem, especially when on reboot they appear to be working expect they have "time-traveled" backwards (to when the drive first went bad).