From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@9fans.net
Subject: Re: [9fans] venti
Date: Fri, 9 Jan 2009 10:44:43 +0100 [thread overview]
Message-ID: <10bfefea89ce073c1640dd187f77ec79@plan9.cs.bell-labs.com> (raw)
In-Reply-To: <dac0a5820901090020x3fbec0b1x880b1abaecefd50b@mail.gmail.com>
> i noticed something odd with venti and i am just trying to see if this
> is an issue and if this needs to be addressed.
>
> i think, by default, plan9 installation sets localhost as the address
> for venti in plan9.ini. but at some point i wanted venti to announce
> any (*) address. for some reason, i simply started venti/venti -a
> 'tcp!*!17034' to make it so. after this, i did vac from another
> machine and it archived data. after sometime, i realized i may be
> running venti on the same venti data area twice. when i did 'ps', it
> looked like that. then i rebooted the machine and then tried
> 'dumpvacroots.new' command (from contrib). i noticed that venti arena
> was corrupted. this is what i remember and if required i can try to
> reproduce the issue.
>
> the question i have is, is there any protection that prevents someone
> from doing this accidentally? something like the last active venti
> arena is marked 'IN_USE' so that if another instance of venti is
> started (with read-write access), it can check for this? i agree user
> has to be careful but given that venti archive is so critical, we
> should avoid any accidental damage.
Hmm. Running two ventis on the same data is, of course, bad. It's also
something I haven't seen happen before. A check could be put in by having
venti put some sort of lock somewhere on the disk. But that would lead
to problems if venti doesn't shut down properly: venti would be gone
but the lock would still be there. You run the risk of not being able
to boot your machine. I think you should just learn to be careful.
Sape
next prev parent reply other threads:[~2009-01-09 9:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 8:20 Tharaneedharan Vilwanathan
2009-01-09 9:44 ` Sape Mullender [this message]
2009-01-09 12:18 ` Richard Miller
2009-01-09 12:38 ` Sape Mullender
2009-01-09 13:39 ` erik quanstrom
2009-01-09 20:11 ` Dave Eckhardt
2009-01-09 20:27 ` erik quanstrom
2009-01-09 22:18 ` Dave Eckhardt
2009-01-09 22:27 ` erik quanstrom
2009-01-09 20:34 ` Steve Simon
2009-01-09 21:08 ` Roman V. Shaposhnik
-- strict thread matches above, loose matches on Subject: below --
2007-10-04 1:51 Russ Cox
2007-10-07 20:51 ` Steve Simon
2007-07-03 4:58 [9fans] Venti Lucio De Re
2007-03-30 16:32 [9fans] venti Steve Simon
2003-02-06 1:11 Kenji Arisawa
2003-02-06 1:21 ` Russ Cox
2002-11-29 18:59 Russ Cox
2002-11-29 18:27 Russ Cox
2002-06-13 20:58 [9fans] bug or a feature? Dan Cross
2002-06-13 21:34 ` Tharaneedharan Vilwanathan
2002-06-13 22:51 ` [9fans] venti Tharaneedharan Vilwanathan
2002-06-14 2:19 ` Sean Quinlan
2002-06-14 5:05 ` Tharaneedharan Vilwanathan
2002-01-30 20:35 George Michaelson
[not found] <rob@plan9.bell-labs.com>
2002-01-30 5:52 ` rob pike
2002-01-30 6:23 ` George Michaelson
2002-01-30 8:07 ` paurea
2002-01-30 11:17 ` Boyd Roberts
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=10bfefea89ce073c1640dd187f77ec79@plan9.cs.bell-labs.com \
--to=sape@plan9.bell-labs.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).