From owner-freebsd-questions Sat Oct 21 13:26: 6 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mtu.ru (ns.mtu.ru [195.34.32.10]) by hub.freebsd.org (Postfix) with ESMTP id AAE4437B4C5 for ; Sat, 21 Oct 2000 13:26:02 -0700 (PDT) X-Recipient: freebsd-questions@FreeBSD.ORG Received: from winnt (ppp109-2.dialup.mtu-net.ru [212.188.109.2]) by mtu.ru (Postfix) with SMTP id 56A3F75E4 for ; Sun, 22 Oct 2000 00:25:56 +0400 (MSD) (envelope-from admin@rustar.ru) From: "sergey" To: Subject: FreeBSD 4.0 RELEASE I/O problems Date: Fri, 22 Sep 2000 00:27:01 +0400 Message-ID: <01c0240a$4c9722a0$020000c6@winnt> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C0242B.D3A8C2A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C0242B.D3A8C2A0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Helo! Dear developers I have some troubles with FreeBSD on my server: sometimes (not planed - may be depends of the moon phase...) problems = with i/o : for exapmle I set command (usualy somethink with file system like chmod = or mkdir) - so after setting command it not return in shell=20 jast wait... I try to kill it fom another console but no effect the = process has D mode in ps order. Last time there was next situation : I have big partition /space with many sites so in one directory I typed = command chown and it didn`t return in shell so = I waite some time but it still doesn`t return in shell, then I took = another console and began kill it but kill -9 didn`t work and with = others signals didn`t work too... So chown command was in memory and = blocked other process that tryed to access in this directory, in the = last chance i set 'shutdown -r NOW' but after 10 seconds it tells 'Some = proccess would not die'=20 We changed all hardware, changed ide harddrivers to SCSI but this = problem sometimes we have... This not problem with chown command - it = can be with commands that work with disk i/o - mkdir for example ... Please help me with this problem, may be you know this, and it was fixed = in 4.1 or 4.1.1 Our server: P3/393/18.2GB IBM UW SCSI/ Adaptec 2940 UW SCSI controller Best Regards Sergey sergeyyy@yahoo.com ------=_NextPart_000_0007_01C0242B.D3A8C2A0 Content-Type: text/html; charset="windows-1251" Content-Transfer-Encoding: quoted-printable
Helo!
Dear = developers
I have some troubles with FreeBSD = on my=20 server:
sometimes (not planed - may be = depends of the=20 moon phase...)  problems with i/o :
for exapmle I set command (usualy = somethink=20 with file system like chmod or mkdir) - so after setting command it not = return=20 in shell  
jast wait... I try to kill it fom = another=20 console but no effect the process has D mode in ps order. = Last   time=20 there was next situation :
I have big partition /space with = many sites=20 so in one directory I typed command chown <user:group> = <directory>=20 and it didn`t return in shell so I waite some time but it still doesn`t = return=20 in shell, then I took another console and began kill it but kill -9 = <PID>=20 didn`t work and with others signals didn`t work too... So chown command = was in=20 memory and blocked other process that tryed to access in this directory, = in the=20 last chance i set 'shutdown -r NOW' but after 10 seconds it tells 'Some = proccess=20 would not die' 
We changed all hardware, changed = ide=20 harddrivers to SCSI but this problem sometimes we have... This not = problem with=20 chown command - it can be with commands that work with disk i/o - mkdir = for=20 example  ... 
Please help me with this problem, = may be you=20 know this, and it was fixed in 4.1 or 4.1.1 
Our server: 
P3/393/18.2GB IBM UW SCSI/ = Adaptec 2940 UW=20 SCSI controller 
 
Best = Regards
Sergey
sergeyyy@yahoo.com
 
 
------=_NextPart_000_0007_01C0242B.D3A8C2A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message