(chosen a random message) On 2019-11-03 15:30, Ravi Pokala wrote: > Uh.... > > I've had a log device in my boot-pool for months, and have booted without > issue: > > [threepio:~] rpokala% zpool status zroot > pool: zroot > state: ONLINE > scan: scrub repaired 0 in 0 days 00:04:36 with 0 errors on Mon Oct 28 > 03:10:59 2019 > config: > > NAME STATE READ WRITE CKSUM > zroot ONLINE 0 0 0 > nvd1p4 ONLINE 0 0 0 > logs > nvd0p1 ONLINE 0 0 0 > > errors: No known data errors
This is not supported, and it's not trivial to support it, because in order to support it, the bootloader would have to know how to replay zilogs, which would add quite a lot of code to it. It's unlikely that you actually hit a problem, however, because the critical contents to boot the system is rarely written to, and as a result it's quite likely that the readable, consistent state of your /boot/ is good enough to boot the system. That's said, it's still because you were lucky, and the code was not designed to work that way... Cheers,
signature.asc
Description: OpenPGP digital signature
