Hang on one sec Isn't this completely true for ALL filesystems,
except that others can't detect that corruption has occurred?
Mike is absolutely correct (and on the earlier email as well). No
matter what the
criticism of ZFS, every other filesystem has it far worse. I've been
carryin
> Thinking this would be simple, I removed BE_disk2_slice4 and rebooted.
> I did get messages that update_archive couldn't be written to BE_disk1_slice0
> on going down.
> Perhaps that is why on the reboot, I find I am in the same spot?
When you say reboot, I presume you mean init 0 or init 6 an
In this state, I cannot lumount disk2_slice4. It is busy. That also makes sense
based on the
lustatus output but how do I get this straightened out?
Did you luactivate the boot environment or just add a grub menu entry for
it ?
I'm reasonably sure the problem is caused by my grub menu, bu
> As long as you've gone through the prerequisite patch list then I can't see
> any particular problems.
I have and there isn't :-) Most of the problems I have helped
customers through were related to patches not being applied or not
installing the LU packages from U4. I've done this particul
