* [Bug 201939] New: There is no 'no space' message when using xfs with nfs.
@ 2018-12-09 12:52 bugzilla-daemon
2018-12-09 12:55 ` [Bug 201939] " bugzilla-daemon
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: bugzilla-daemon @ 2018-12-09 12:52 UTC (permalink / raw)
To: linux-xfs
https://bugzilla.kernel.org/show_bug.cgi?id=201939
Bug ID: 201939
Summary: There is no 'no space' message when using xfs with
nfs.
Product: File System
Version: 2.5
Kernel Version: 3.4.113
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: XFS
Assignee: filesystem_xfs@kernel-bugs.kernel.org
Reporter: gbkwon@gmail.com
Regression: No
hi all
I use xfs filesystem over nfs
I am using the xfs file system via NFS on two Linux servers.
Even though xfs is full, you will not get a 'no space' message through nfs.
The server's load average goes up and the kworker consumes the CPU.
The server's nfs service is not responding.
When ext3 is full in the same environment, I get a 'no space' message.
Which part of nfs and xfs should be checked?
Below is the environment I am using.
kernel : nfs server 3.4.113 vanilla, nfs client 2.6.32-573.el6.x86_64
nfs : nfs v3 with tcp
==================================================================
nfs server
==================================================================
/dev/mapper/lv2 500G 500G 20K 100% /lv2
/lv2
0.0.0.0/0.0.0.0(rw,async,wdelay,nohide,nocrossmnt,insecure,no_root_squash,no_all_squash,no_subtree_check,insecure_locks,no_acl,fsid=1543743056,anonuid=65534,anongid=65534)
==================================================================
nfs client
==================================================================
10.0.0.20:/lv2 500G 500G 32K 100% /mnt/2
nfsstat -m
/mnt/2 from 10.0.0.20:/lv2
Flags:
rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=10.0.0.20,mountvers=3,mountport=2047,mountproto=udp,local_lock=none,addr=10.0.0.20
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 201939] There is no 'no space' message when using xfs with nfs.
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 ` bugzilla-daemon
2018-12-10 23:19 ` bugzilla-daemon
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: bugzilla-daemon @ 2018-12-09 12:55 UTC (permalink / raw)
To: linux-xfs
https://bugzilla.kernel.org/show_bug.cgi?id=201939
--- Comment #1 from gbkwon@gmail.com ---
Please see the log below.
top - 21:54:10 up 58 min, 0 users, load average: 8.50, 8.37, 8.83
Tasks: 347 total, 2 running, 345 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us, 4.2%sy, 0.0%ni, 95.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
12368 root 20 0 0 0 0 S 12 0.0 4:32.44 kworker/2:2
11092 root 20 0 0 0 0 S 10 0.0 4:42.57 kworker/3:1
11166 root 20 0 0 0 0 R 9 0.0 2:09.47 kworker/5:1
12473 root 20 0 0 0 0 S 8 0.0 2:09.36 kworker/4:2
2944 root 20 0 0 0 0 D 6 0.0 2:09.10 nfsd
2953 root 20 0 0 0 0 D 6 0.0 2:24.65 nfsd
3024 root 20 0 0 0 0 D 6 0.0 2:23.12 nfsd
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 201939] There is no 'no space' message when using xfs with nfs.
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
3 siblings, 0 replies; 5+ messages in thread
From: bugzilla-daemon @ 2018-12-10 23:19 UTC (permalink / raw)
To: linux-xfs
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 201939] There is no 'no space' message when using xfs with nfs.
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
3 siblings, 0 replies; 5+ messages in thread
From: bugzilla-daemon @ 2018-12-11 2:05 UTC (permalink / raw)
To: linux-xfs
https://bugzilla.kernel.org/show_bug.cgi?id=201939
--- Comment #3 from gbkwon@gmail.com ---
Thanks for your reply.
The same problem does not occur in 3.18 kernels.
Unfortunately, I have must to use 3.4 kernel.
If I add 'noac' to the nfs mount option, there is no such problem.
However, the 'noac' option causes a performance penalty of more than 50%.
I want to fix the problem without adding the 'noac' option.
If I add the 'actimeo=0' option to the nfs mount option, the problem happens,
but after about 5 minutes the problem disappears.
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 201939] There is no 'no space' message when using xfs with nfs.
2018-12-09 12:52 [Bug 201939] New: There is no 'no space' message when using xfs with nfs bugzilla-daemon
` (2 preceding siblings ...)
2018-12-11 2:05 ` bugzilla-daemon
@ 2018-12-11 2:32 ` bugzilla-daemon
3 siblings, 0 replies; 5+ messages in thread
From: bugzilla-daemon @ 2018-12-11 2:32 UTC (permalink / raw)
To: linux-xfs
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-12-11 2:32 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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).