From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201939] New: There is no 'no space' message when using xfs with nfs.
Date: Sun, 09 Dec 2018 12:52:29 +0000 [thread overview]
Message-ID: <bug-201939-201763@https.bugzilla.kernel.org/> (raw)
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.
next reply other threads:[~2018-12-09 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 12:52 bugzilla-daemon [this message]
2018-12-09 12:55 ` [Bug 201939] There is no 'no space' message when using xfs with nfs bugzilla-daemon
2018-12-10 23:19 ` bugzilla-daemon
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@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 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.