9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil: disk is full
Date: Wed, 12 Mar 2003 11:43:22 +0000	[thread overview]
Message-ID: <5f8e0c9e7b39e0e6086945e534c7cd64@vitanuova.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]

> Yes, you can get away with snap -a occasionally
> during the write buffer, perhaps combined with
> stop mkfs |rc and restarting it.

i've just replaced my laptop disk (the old one died, but i managed to
back it up), and i thought this might be the right time to start using
fossil rather than kfs.

having read the "setting up fossil" page on the wiki, i thought i'd
give myself a fossil partition of 1.5GB and a venti partition of 19GB.

when copying in the (2.4GB) backup mkfs archive, i tried to use the
above mentioned technique, so i ran something like:

	while() {
		echo snap -a >> /srv/fscons
		stop mkext | rc
		sleep 1
		start mkext | rc
		sleep 300
	}

i did this in a hurry, and realise now that sleeping for only 1 second
was naive - maybe it should have slept for 300?

anyway, i left it overnight, and came back to many disk full messages,
and a broken fossil (traceback attached).

it seems a pity there's no way of doing this that doesn't rely on
guesswork: perhaps one might be able to put fossil into a mode where
if the disk fills up it would trigger an automatic snap -a and block
writers until it had all been written to venti?

in the meantime, what sort of numbers in the above script are likely
to keep fossil from filling up?

  cheers,
    rog.

[-- Attachment #2.1: Type: text/plain, Size: 312 bytes --]

The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Disposition: attachment; filename=fossil.trace
	Content-Type: text/plain; charset="US-ASCII"
	Content-Transfer-Encoding: 7bit

[-- Attachment #2.2: fossil.trace.suspect --]
[-- Type: application/octet-stream, Size: 2811 bytes --]

% db 1521
386 binary
page fault
/sys/src/libc/9sys/abort.c:6 abort/               	CMPL	0,$0
$C
abort() /sys/src/libc/9sys/abort.c:6 called from _assert+3a /sys/src/libc/port/_assert.c:12
_assert(s=35e79) /sys/src/libc/port/_assert.c:7 called from fileDecRef+38 /sys/src/cmd/fossil/file.c:1127
fileDecRef(f=8e7478) /sys/src/cmd/fossil/file.c:1121 called from fsSnapshot+82 /sys/src/cmd/fossil/fs.c:571
       	fileDecRef.p/         	0x8eab98
       	fileDecRef.qq/         	0x0
fsSnapshot(fs=7d668, doarchive=1) /sys/src/cmd/fossil/fs.c:460 called from fsysSnap+74 /sys/src/cmd/fossil/9fsys.c:345
       	fsSnapshot.dst/         	0x8e7478
       	fsSnapshot.src/         	0x59968
fsysSnap(argv=7fffce40, argc=0, fsys=59a28) /sys/src/cmd/fossil/9fsys.c:329 called from fsysXXX+12e /sys/src/cmd/fossil/9fsys.c:1407
       	fsysSnap.usage/         	0x37739
       	fsysSnap.doarchive/         	0x1
       	fsysSnap._argc/         	0x6b680061
       	fsysSnap._args/         	0x56b4e
fsysXXX(argv=7fffce3c, name=8c9aa0, argc=2) /sys/src/cmd/fossil/9fsys.c:1376 called from cmdFsysXXX+3f /sys/src/cmd/fossil/9fsys.c:1423
       	fsysXXX.i/         	0xe
       	fsysXXX.fsys/         	0x59a28
       	fsysXXX.r/         	0x4f268
cmdFsysXXX(argv=7fffce3c, argc=2) /sys/src/cmd/fossil/9fsys.c:1414 called from cliExec+e0 /sys/src/cmd/fossil/Ccli.c:58
cliExec(buf=4ad20) /sys/src/cmd/fossil/Ccli.c:37 called from consProc+23c /sys/src/cmd/fossil/Ccons.c:304
       	cliExec.p/         	0x56b48
       	cliExec.argv/         	0x56b48
       	cliExec.argc/         	0x2
       	cliExec.i/         	0x11
       	cliExec.r/         	0x1
       	cliExec..safe/         	0x8e7678
consProc() /sys/src/cmd/fossil/Ccons.c:223 called from vtThread+30 /sys/src/libventi/plan9-thread.c:63
       	consProc.q/         	0x4afe8
       	consProc.n/         	0x8
       	consProc.buf/         	0x70616e73
       	consProc.r/         	0x14
       	consProc..safe/         	0x2000
       	consProc.i/         	0x7
       	consProc.wbuf/         	0x0
       	consProc.argv/         	0x20f72
       	consProc.argc/         	0x14
       	consProc.lp/         	0x0
vtThread(rock=0, f=1ac8) /sys/src/libventi/plan9-thread.c:47 called from consInit+44 /sys/src/cmd/fossil/Ccons.c:384
consInit() /sys/src/cmd/fossil/Ccons.c:376 called from main+117 /sys/src/cmd/fossil/fossil.c:72
main(argv=7fffefd4, argc=0) /sys/src/cmd/fossil/fossil.c:22 called from _main+31 /sys/src/libc/386/main9.s:16
       	main.cmd/         	0x4afc8
       	main.tflag/         	0x0
       	main.ncmd/         	0x1
       	main._argc/         	0x63
       	main._args/         	0x386f3
       	main.p/         	0x7fffeff2
       	main.i/         	0x0
       	main..safe/         	0x0--upas-pwzwxxhvwzolfvgkhmsqwfjljx--

             reply	other threads:[~2003-03-12 11:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 11:43 rog [this message]
2003-03-12 12:02 ` Axel Belinfante
2003-03-12 17:33   ` Russ Cox
2003-03-12 20:47 ` Russ Cox
2003-03-12 20:49 ` Russ Cox
2003-03-19 20:09 ` Axel Belinfante
  -- strict thread matches above, loose matches on Subject: below --
2003-03-07  3:48 Kenji Arisawa
2003-03-07  7:52 ` Fco.J.Ballesteros
2003-03-07  8:17   ` Lucio De Re
2003-03-07  8:33     ` Fco.J.Ballesteros
2003-03-07  8:33   ` Kenji Arisawa
2003-03-07  8:43     ` Kenji Arisawa
2003-03-07  8:59       ` Lucio De Re
2003-03-07  9:11         ` Fco.J.Ballesteros
2003-03-07  9:19           ` Lucio De Re
2003-03-07 22:16         ` Axel Belinfante
2003-03-07 23:02           ` Russ Cox
2003-03-07  9:08       ` Fco.J.Ballesteros

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5f8e0c9e7b39e0e6086945e534c7cd64@vitanuova.com \
    --to=rog@vitanuova.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).