From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] vac messages
Date: Thu, 18 Dec 2008 08:06:33 -0800 [thread overview]
Message-ID: <dd6fe68a0812180806p509f7144qf504f112ca0aa4e0@mail.gmail.com> (raw)
In-Reply-To: <27f336d87c8b94e5634f3f804514c37e@ipgp.jussieu.fr>
> I'm doing some nightly backups in a cron from a linux server with p9p
> vac. Venti runs on a plan 9 filserver. From what I can unvac afterwards,
> it seems like it's going fine, however I'm getting these kind of messages
> in the mail sent by the cron daemon:
>
> either
>
> vac: vtcachelocal: asked for block #5395928; only 144918656 blocks
When did you last update? I fixed a bug that would produce
messages like this in
http://hg.pdos.csail.mit.edu/hg/plan9/rev/206d0c2fc7b5
on October 26.
Russ
next prev parent reply other threads:[~2008-12-18 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 12:47 Mathieu Lonjaret
2008-12-18 16:06 ` Russ Cox [this message]
2008-12-18 16:29 ` Mathieu Lonjaret
2008-12-22 15:04 ` Mathieu Lonjaret
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=dd6fe68a0812180806p509f7144qf504f112ca0aa4e0@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/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).