From owner-freebsd-hackers Fri Jan 29 09:31:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14809 for freebsd-hackers-outgoing; Fri, 29 Jan 1999 09:31:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14803 for ; Fri, 29 Jan 1999 09:31:56 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA16100; Fri, 29 Jan 1999 09:27:33 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdA16092; Fri Jan 29 17:27:24 1999 Date: Fri, 29 Jan 1999 09:27:17 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Kris Kennaway cc: Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: softupdates on / In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk has responded and said that I was wrong.. The code to do what I suggested was never completed. julian On Fri, 29 Jan 1999, Kris Kennaway wrote: > On Thu, 28 Jan 1999, Julian Elischer wrote: > > > The eventual aim is to never use NON softupdates mode.. > > The system is not supposed to bonb with "filesystem full" when there are > > uncommitted delete operations on the softupdates queues. > > if it does, then there is a bug. It's suposed to kick off some faster > > reconciliation and hang around for a bit. > > Unless I'm mistaking you, this is in fact what happens: > > [morden|root] 21:34 ~ df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd0s2a 32254 21244 8430 72% / > /dev/wd0s2f 596286 534890 13694 98% /usr > /dev/wd1s3e 496367 456461 197 100% /usr2 > /dev/wd1s3f 396895 360004 5140 99% /home > /dev/wd0s2e 29727 7705 19644 28% /var > /dev/wd0s1 872640 848720 23920 97% /c > /dev/wd1s1 1023824 942256 81568 92% /d > /dev/wd1s5 511760 486472 25288 95% /e > procfs 4 4 0 100% /proc > mfs:31 20598 16 18936 0% /tmp > localhost:/ 0 0 0 100% /crypt > > [morden|root] 21:34 ~ pwd > /home/kkenn > [morden|root] 21:34 ~ mount > ... > /dev/wd1s3f on /home (local, soft-updates, writes: sync 1123 async 11409) > [morden|root] 21:34 ~ dd if=/dev/zero of=bigfile bs=1024k count=20 > 20+0 records in > 20+0 records out > 20971520 bytes transferred in 11.454656 secs (1830829 bytes/sec) > [morden|root] 21:34 ~ df > > ... > > /dev/wd1s3f 396895 382092 -16948 105% /home > > [morden|root] 21:34 ~ rm bigfile > > [In another window, as a regular user] > > [morden|kkenn] 21:35 ~ cp /etc/motd . > > /home: write failed, file system is full > cp: ./motd: No space left on device > > This persists for 30 seconds exactly, until the clock expires and the > space is reclaimed. Given the state of fullness of my partitions, I run into > this quite frequently. I had always assumed it was just the way things were > with soft-updates. > > Kris > > ----- > (ASP) Microsoft Corporation (MSFT) announced today that the release of its > productivity suite, Office 2000, will be delayed until the first quarter > of 1901. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message