On Fri, Jul 25, 2008 at 05:22:56PM -0400, Robert Healey wrote: >Greetings. I managed to work around the problem I was having with > >> Except from dmesg: > >> Jul 17 16:32:42 compute-4-10 kernel: LustreError: > >> 3834:0:(ldlm_lock.c:430:__ldlm_handle2lock()) > >ASSERTION(lock->l_resource > >> != NULL) > >> failed > >This looks like bug 15269. >by moving from RHEL 5.2 on a v20z to RHEL 4.6 on Thumper, ran into a >different problem which appears to be a deal breaker for me. I forcibly >failed one of the drives in the raid-1 mirror for the MDT and the file >system promptly stopped responding to clients. The rest of the machine >worked just fine. A reboot of both the client + server cleared the
md doing failover shouldn't hang or stop anything. pulling disks on md raid5 and raid1's has worked fine for me in the past. what does /proc/mdstat look like? dmesg? how did you forcibly fail the disk? >problem. Its looking like Solaris/ZFS might be a better answer for me. they're not really comparable filesystems. or do you mean you'll use Lustre's ZFS on OSS's? I didn't think that was available yet... cheers, robin _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
