From: Robert White <rwhite@pobox.com>
To: russell@coker.com.au, linux-btrfs@vger.kernel.org
Subject: Re: strange 3.16.3 problem (er... never mind 8-)
Date: Tue, 21 Oct 2014 08:23:31 -0700 [thread overview]
Message-ID: <54467A73.5030804@pobox.com> (raw)
In-Reply-To: <201410212142.22754.russell@coker.com.au>
On 10/21/2014 03:42 AM, Russell Coker wrote:
> I've just upgraded the Dom0 (NFS server) from 3.16.3 to 3.16.5 and it all
> works.
>
> Prior to upgrading the Dom0 I had the same problem occur with different file
> names. All the names in question were truncated names of files that exist.
> It seems that 3.16.3 has a bug with NFS serving files with long names.
>
> Thanks for all the suggestions.
>
Well never mind my message from a few minutes ago...
But thanks for finding that problem/solution. I've been having an NFS
problem of my own and it is from a server running 3.16.3... so you may
have just made my day. 8-)
next prev parent reply other threads:[~2014-10-21 15:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 3:54 strange 3.16.3 problem Russell Coker
[not found] ` <CAHGunUkzXZ-ybUR_y3tHzGwtn_45gq8YQJyEqteBX3zqWzUakA@mail.gmail.com>
2014-10-18 10:29 ` Russell Coker
2014-10-18 13:33 ` Robert White
2014-10-18 23:41 ` Russell Coker
2014-10-19 5:37 ` Duncan
2014-10-19 10:19 ` Duncan
2014-10-20 17:37 ` Robert White
2014-10-20 20:21 ` Goffredo Baroncelli
2014-10-21 9:50 ` Duncan
2014-10-21 10:16 ` inode_cache " Roman Mamedov
2014-10-21 12:08 ` Duncan
2014-10-21 16:40 ` Goffredo Baroncelli
2014-10-22 7:12 ` Duncan
2014-10-19 10:46 ` Chris Samuel
2014-10-20 4:38 ` Duncan
2014-10-20 13:02 ` Zygo Blaxell
2014-10-20 13:19 ` Austin S Hemmelgarn
2014-10-21 10:13 ` Russell Coker
2014-10-21 10:42 ` Russell Coker
2014-10-21 15:23 ` Robert White [this message]
2014-10-21 12:25 ` Duncan
2014-10-21 15:10 ` Robert White
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=54467A73.5030804@pobox.com \
--to=rwhite@pobox.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.