From owner-freebsd-stable Fri Aug 30 9:30:41 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D441337B400 for ; Fri, 30 Aug 2002 09:30:38 -0700 (PDT) Received: from mtiwmhc22.worldnet.att.net (mtiwmhc22.worldnet.att.net [204.127.131.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51E9D43E65 for ; Fri, 30 Aug 2002 09:30:38 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from prime ([12.88.88.38]) by mtiwmhc22.worldnet.att.net (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020830163037.YJDB1817.mtiwmhc22.worldnet.att.net@prime> for ; Fri, 30 Aug 2002 16:30:37 +0000 Message-ID: <00f601c25042$91171d70$0301a8c0@prime> From: "Charles Swiger" To: References: <111517111196.20020830165525@tz.ru> Subject: Re: Samba problem. Date: Fri, 30 Aug 2002 12:30:34 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sergey A Nasedkin wrote: > I have a problem with samba port. When I copy files to machine > running samba after short period it take 95-99% using cpu. > Data writing on disk created with vinum. The problem was detected > on FreeBSD 4.5.I've try to use samba 2.2.3a and 2.2.5 . Does anybody > have same problem ? Any suggestion ? You've got a lot of variables, here. Try to exclude some by: 1) trying samba on a non-RAIDed disk (ie, not with vinum) I think samba now tries to use something around a 64K block size, so using a 64K stripe size may prove beneficial (ie, using RAID-0 striping instead of simple filesystem concatenation). 2) Try doing local I/O, perhaps the iozone test suite, and see what your CPU usage looks like. 3) Give us the relevant details of 'dmesg', if you can...double check things like whether the drives are going in UDMA mode or falling back to PIO, for example, would certainly make I/O CPU intensive. 4) Your machine appears to be low on memory for a 400 GB fileserver; disk caching in RAM is one of the most cost-efficient ways of improving performance. -Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message