From: Guk-Bong Kwon <gbkwon@gmail.com>
To: linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: There is no 'no space' message when using xfs with nfs.
Date: Sun, 9 Dec 2018 22:07:26 +0900 [thread overview]
Message-ID: <CAJ-WH_xqdJVyA7mMmoqAkbJoOcsvgm9cF--NQADfd+pp_oRbEw@mail.gmail.com> (raw)
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
==================================================================
server top log
==================================================================
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
next reply other threads:[~2018-12-09 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 13:07 Guk-Bong Kwon [this message]
2019-01-10 20:09 ` There is no 'no space' message when using xfs with nfs J. Bruce Fields
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=CAJ-WH_xqdJVyA7mMmoqAkbJoOcsvgm9cF--NQADfd+pp_oRbEw@mail.gmail.com \
--to=gbkwon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).