linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: urgrue <urgrue@tumsan.fi>
To: linux-admin@vger.kernel.org
Subject: coda, or alternative?
Date: Wed, 5 Mar 2003 15:51:14 +0200	[thread overview]
Message-ID: <20030305135114.GA25930@fede2.tumsan.fi> (raw)

i have two servers connected via gigabit ethernet. the one on the "far 
end" is basically a backup server from which i've mounted a few drives, 
to which the near-end server writes directly. the line is very reliable 
but it does have its problems once in a while.

NFS is awful, absolutely AWFUL, when there's a connection problem. it 
can end up hanging the whole machine (because many processes/scripts 
try to write to the mounted drive, and they all hang, eventually 
gumming up the whole system).

but i'd really like it mounted, as the amount of data that needs to be 
transferred is a bit loo large to let collect up on the near-end 
server. it doesnt matter if all attempts to write to the mount totally 
fail when the line is down, just so long as the machine survives nicely.

so i'm looking at coda, but everywhere i see warnings like "barely read 
for production use", "experimental", "development", etc....

samba has been good to me in other situations, but i'm a bit reluctant 
to use it because it doesnt behave all that nicely either (needs manual 
remounting often, etc. plus, linux pride counts ;)

is coda good enough despite these warnings, or are there other 
alternatives?

                 reply	other threads:[~2003-03-05 13:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030305135114.GA25930@fede2.tumsan.fi \
    --to=urgrue@tumsan.fi \
    --cc=linux-admin@vger.kernel.org \
    /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).