From owner-nwchem-users@emsl.pnl.gov Fri Feb 2 22:59:49 2007 Received: from odyssey.emsl.pnl.gov (localhost [127.0.0.1]) by odyssey.emsl.pnl.gov (8.13.8/8.13.8) with ESMTP id l136xmmX013133 for ; Fri, 2 Feb 2007 22:59:49 -0800 (PST) Received: (from majordom@localhost) by odyssey.emsl.pnl.gov (8.13.8/8.13.8/Submit) id l136xmup013132 for nwchem-users-outgoing-0915; Fri, 2 Feb 2007 22:59:48 -0800 (PST) X-Authentication-Warning: odyssey.emsl.pnl.gov: majordom set sender to owner-nwchem-users@emsl.pnl.gov using -f X-Ironport-SG: Med_Throttle X-Ironport-SBRS: -1.8 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aj0KAPvBw0VCxGT0Umdsb2JhbACOWAEUDwYGHpEcAQEBAQ X-IronPort-AV: i="4.13,275,1167638400"; d="scan'208"; a="12866022:sNHT17520034" DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=oiz9iiIoyionJNtJ2Ge/tSiThEtjjoNCW20jJNv/UJHdcTtWrDwzvFtBGXp647Q+U8uLlWtSInQecaetcDh61RUUqyFf9fSGf7TbHG8J0uLa8n2tflklKCcrIplPfWlQ6rH4CR+PRHOGr6mg22A4fepGi7Gz50JprBixb8Ad2Zo=; X-YMail-OSG: DFDLDQ0VM1mOUhoJUPLx9g8IZSa5jHweLiUHgMNASGK4xc.XCtRiscz8jky.joDy.vT7CSiR1HxbpKajg0X77MiQtIyobtsGRxCbpEzhX8OlGq0OhSMI Date: Fri, 2 Feb 2007 22:59:44 -0800 (PST) From: Francesco Pietra Subject: Re: [NWCHEM] unclassified error while m05-2x dft To: Edoardo Apra Cc: users nwchem In-Reply-To: <45C3B88B.9030400@ornl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <613074.55706.qm@web58911.mail.re1.yahoo.com> Sender: owner-nwchem-users@emsl.pnl.gov Precedence: bulk Hi Edoardo: The swap directory is 7GB, I am the only user on the machine, so that problems of lack of space can be ruled out. We paid attention to a disk error. However, since I replaced Maxtor (with the particular model I had, I met problems of memory blurring, likely - experts said - because of conflicts of HDs with nVidia chips) with WD Raptor (in Linux-driven raid1) I had no more problems of disk/memory, even on memory-demanding procedures lasting weeks. I/O problems with swap seem the most likely alternative. Thank you for the suggestion. I restarted the procedure, which is going on strongly (as it was before the crash) toward density convergence. For example in the last two iters, it improved from 0.21D-5 to 0.13D-05, for a required accuracy 0.10D-05. Whether the alleged I/O errors arose from inadequacy of the main board (Tyan S2895 K8WE) is difficult to investigate because Tyan Europe on a previous occasion refused to answer when the OS is Linux. They simply said: unsupported OS. My appeal to Tyan Taiwan remained unanswered. Therefore, I am not going to pose questions to Tyan. Next time I'll be more careful in choosing a mainboard from the Linux supported list. Have a good weekend francesco --- Edoardo Apra wrote: > Francesco Pietra wrote: > > >Read Failed > > > > > > > int2e_buf_read:asynch IO failed 1301 > > > Francesco > this error message tells me that you just had an I/O > problem on your > scratch directory. > This I/O problem might be caused by a I/O Hardware > problem or by the > fact that you have ran out of space in the scratch > directory. > > Edo > > -- > ORNL, bldg 6012 > 1 Bethel Valley Rd, MS 6367, Oak Ridge, TN 37831 > Tel: (865) 574-4992 Fax: (865) 574-0680 > > ____________________________________________________________________________________ Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097