On Oct 29, 2004, at 7:48 PM, Mike Tancsa wrote:
Same result the other poor schmuck got when he tried it. There was also a suggestion that HT be turned off. Kinda defeats the whole
HT works against you unless the scheduler is specifically aware of it, and right now the ULE scheduler is broken. For sure turn HT off in your BIOS and make sure you use SCHED_4BSD and NOT ULE
I turned off HT on my Dell PE400SC (uses Intel ICH5 chipset) almost instantly after installing FreeBSD. Partitioning and labeling my SATA drives went just fine. System is on a PATA drive. Even striping the two SATA drives with Vinum followed by newfs was fine. System locked hard the instant I actually tried to use the SATA drives. Reformatted without vinum and had similar lock/panic. This was possibly 5.2.1-p10. Have darn near the latest 5.3 on it now and its running nicely w/o HT.
Pretty sure ULE was the scheduler being used when I had problems as I remember when SCHED_4BSD was the new default. IMO, when it worked, ULE ran smoother. Now it seems that one process can hog the filesystem resources and block out another doing the exact same thing but to another file.
That instance with HT was the first and only time FreeBSD messed up a filesystem and I've had at least one FreeBSD machine running 24/7 since 2.0.0-RELEASE. As a result I'm not much in the mood to re-enable HT now that I have real data on the drives.
-- David Kelly N4HHE, [EMAIL PROTECTED] ======================================================================== Whom computers would destroy, they must first drive mad.
_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
