From: Boaz Harrosh <openosd@gmail.com>
To: didier <did447@gmail.com>, "J. Bruce Fields" <bfields@fieldses.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Chris Perl <cperl@janestreet.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Chris Perl <chris.perl@gmail.com>
Subject: Re: File Read Returns Non-existent Null Bytes
Date: Tue, 03 Mar 2015 11:09:18 +0200 [thread overview]
Message-ID: <54F57A3E.9070202@gmail.com> (raw)
In-Reply-To: <CAJRYxuJt_1_NFW5Hsed3GhS75y2D7aHnPS5srkPV+KJzWi90MA@mail.gmail.com>
On 03/02/2015 11:33 PM, didier wrote:
<>
> Yes, writing something like;
> tail -f foo
> doesn't work if readers and writer aren't on the same client
>
s/doesn't/might not/
There are some implementations ie server/client combination that this works
just perfectly fine.
> IMO it's the most surprising for someone with a posix background on local fs.
Cheers
Boaz
next prev parent reply other threads:[~2015-03-03 9:09 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 20:56 File Read Returns Non-existent Null Bytes Chris Perl
2015-02-23 22:34 ` Trond Myklebust
2015-02-25 17:04 ` Chris Perl
2015-02-25 17:37 ` Trond Myklebust
2015-02-25 21:02 ` Chris Perl
2015-02-25 21:47 ` Trond Myklebust
2015-02-25 21:53 ` Chris Perl
2015-02-25 22:15 ` Trond Myklebust
2015-02-26 12:41 ` Chris Perl
2015-02-26 13:29 ` Trond Myklebust
2015-02-26 13:42 ` Chris Perl
2015-02-26 14:10 ` Chris Perl
2015-02-26 15:22 ` Simo Sorce
2015-02-26 15:34 ` Trond Myklebust
2015-02-26 15:36 ` Simo Sorce
2015-02-26 15:45 ` Chris Perl
2015-02-26 15:56 ` Simo Sorce
2015-02-27 1:48 ` Harshula
2015-02-27 13:17 ` Chris Perl
2015-02-26 16:00 ` Chris Perl
2015-02-26 23:43 ` Trond Myklebust
2015-02-26 15:37 ` Trond Myklebust
2015-02-27 22:40 ` J. Bruce Fields
2015-02-27 23:33 ` Chuck Lever
2015-03-02 15:19 ` Chris Perl
2015-03-02 15:57 ` Chuck Lever
2015-03-02 20:58 ` J. Bruce Fields
2015-03-02 21:15 ` Chuck Lever
2015-03-03 13:29 ` Chris Perl
2015-03-03 15:30 ` Chuck Lever
2015-03-03 17:44 ` Trond Myklebust
2015-03-03 19:57 ` Chuck Lever
2015-03-02 21:33 ` didier
2015-03-03 9:09 ` Boaz Harrosh [this message]
[not found] ` <CAHHaOubVomDJ5uePb7DFGizZ0TBsyC-tJN5p6-RWOYKQC2oxvA@mail.gmail.com>
2015-02-27 20:13 ` Chris Perl
2015-02-25 22:32 ` Chuck Lever
2015-02-26 0:37 ` Trond Myklebust
2015-02-26 0:43 ` Trond Myklebust
2015-02-26 1:27 ` Trond Myklebust
2015-02-26 15:08 ` Chuck Lever
2015-02-26 16:26 ` fsx size error (was: File Read Returns Non-existent Null Bytes) Chuck Lever
2015-02-26 17:27 ` Trond Myklebust
2015-02-26 19:00 ` Chuck Lever
2015-02-26 23:06 ` Trond Myklebust
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=54F57A3E.9070202@gmail.com \
--to=openosd@gmail.com \
--cc=bfields@fieldses.org \
--cc=chris.perl@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=cperl@janestreet.com \
--cc=did447@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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