From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201939] There is no 'no space' message when using xfs with nfs.
Date: Mon, 10 Dec 2018 23:19:46 +0000 [thread overview]
Message-ID: <bug-201939-201763-NwEnCJ5mDC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201939-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201939
Christian Kujau (lists@nerdbynature.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lists@nerdbynature.de
--- Comment #2 from Christian Kujau (lists@nerdbynature.de) ---
> kernel : nfs server 3.4.113 vanilla, nfs client 2.6.32-573.el6.x86_64
Both kernel versions have been EOL for a long time (or is the server maybe on
4.4.113 instead?), please either try to reproduce with recent kernel version or
contact the vendor about this issue.
That being said, there have been some problems with NFS & ENOSPC in the (very
distant) past:
> NFS behaviour when filesystem is 100% full
> https://technicalprose.blogspot.com/2013/11/nfs-behaviour-when-filesystem-is-100.html
> NFS corruption on ENOSPC
> https://www.redhat.com/archives/linux-lvm/2010-December/msg00030.html
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-12-10 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 12:52 [Bug 201939] New: There is no 'no space' message when using xfs with nfs bugzilla-daemon
2018-12-09 12:55 ` [Bug 201939] " bugzilla-daemon
2018-12-10 23:19 ` bugzilla-daemon [this message]
2018-12-11 2:05 ` bugzilla-daemon
2018-12-11 2:32 ` bugzilla-daemon
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=bug-201939-201763-NwEnCJ5mDC@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@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