Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 19 Feb 2003 17:29:42 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id h1K1Te3v016088 for ; Wed, 19 Feb 2003 17:29:40 -0800 Received: from relay1.corp.sgi.com (ether-spindle.corp.sgi.com [192.26.51.29]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h1K1cKG8020768 for ; Wed, 19 Feb 2003 17:38:20 -0800 Received: from Liberator (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id RAA52139; Wed, 19 Feb 2003 17:37:48 -0800 (PST) Subject: RE: sync doesn't do the job From: Eric Sandeen To: Jason Li Cc: "'linux-xfs@oss.sgi.com'" In-Reply-To: <7CBD7127AB037F439CB8146275AE261E37CEBA@hq-ex-6> References: <7CBD7127AB037F439CB8146275AE261E37CEBA@hq-ex-6> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 19 Feb 2003 19:38:00 -0600 Message-Id: <1045705082.23242.21.camel@Liberator> Mime-Version: 1.0 X-archive-position: 2798 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1251 Lines: 47 Jason - one other thing that occurred to me... does the CF system do write-caching? Might be interesting to test this on a spinning disk, if you can. (and if it's IDE, explicitly turn off write caching). I tried the reboot -f test on essentially top of tree devel code, on a scsi drive, and it worked fine. I also tested it on 1.1 code (which we released for vanilla kernel 2.4.18, and Red Hat 2.4.9-based - I tested the Red Hat kernel), and it also worked fine. (I left out the "(show dirty buffers)" part, not sure what you're doing there.) You said it's 1.1 on linux 2.4.19 - I wonder if the forward port may have caused problems? -Eric On Wed, 2003-02-19 at 19:18, Jason Li wrote: > > Hi Eric, > > Thanks for replying. > > I tried the following script: > for i in `seq 1 100` do echo $i>>myfile done; > sync > (show dirty buffers) > reboot -f > and > for i in `seq 1 100` do echo $i>>myfile done; > sync > (show dirty buffers) > mount -ro / > reboot > Both failed to get the 100 numbers in the file. > > Another thing I tried is to show dirty buffers (with a hack) -- both showed > no dirty buffer from the linux side. > > We can try 1.2, but for now we need to understand where the problem is. > > Best regards, > Jason