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: Tue, 11 Dec 2018 02:32:17 +0000 [thread overview]
Message-ID: <bug-201939-201763-5DhRoGKjsO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201939-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201939
Eric Sandeen (sandeen@sandeen.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |sandeen@sandeen.net
Resolution|--- |PATCH_ALREADY_AVAILABLE
--- Comment #4 from Eric Sandeen (sandeen@sandeen.net) ---
(In reply to gbkwon from comment #3)
> Thanks for your reply.
>
> The same problem does not occur in 3.18 kernels.
>
> Unfortunately, I have must to use 3.4 kernel.
So, it seems you have reported a bug in a 6 year old kernel which has already
been fixed - 4 years ago. Which means that it's not a bug now.
This is an upstream bug tracker, not a user support forum. You may wish to ask
your distribution for further support of the old kernel, or possibly try a user
mailing list. You could also spot-check kernels in between, or do a full
bisect, to look for the commit(s) which fixed the old bug.
But because this issue has apparently already been resolved in upstream
kernels, I'm closing this bug.
Thanks,
-Eric
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2018-12-11 2:32 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
2018-12-11 2:05 ` bugzilla-daemon
2018-12-11 2:32 ` bugzilla-daemon [this message]
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-5DhRoGKjsO@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