From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] losing files with ftpfs(4)
Date: Wed, 8 Sep 2004 00:03:54 +0200 [thread overview]
Message-ID: <05e501c49526$93826a30$f5667d50@SOMA> (raw)
In-Reply-To: <ee9e417a040907144117762279@mail.gmail.com>
> This is just a fundamental limitation of ftpfs.
> It can't reliably try the create until it has all
> the data that is supposed to be in the file.
> But it doesn't know it has all the data until
> the close, at which point mv will think it's
> okay to remove the original.
1 point for NFS's rename call. -2 points for NFS's lack
of a close op and writes in a 'random' order.
ftp's RNFR/RNTO ops do mv(1).
not that i'm advocating breaking mv.
did this 'disk full' patch get applied?
brahma% diff /n/sources/plan9/sys/src/cmd/ip/ftpfs/proto.c .
991,992c991
< getreply(&ctlin, msg, sizeof(msg), 0);
< return off;
---
> return getreply(&ctlin, msg, sizeof(msg), 0) == Success ? off : -1;
next prev parent reply other threads:[~2004-09-07 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 21:11 Alberto Cortes
2004-09-07 21:41 ` Russ Cox
2004-09-07 22:03 ` boyd, rounin [this message]
2004-09-07 23:07 ` jmk
2004-09-07 23:09 ` boyd, rounin
2004-09-08 1:53 ` Joseph Holsten
2004-09-08 2:32 ` Russ Cox
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='05e501c49526$93826a30$f5667d50@SOMA' \
--to=boyd@insultant.net \
--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).