Linux-NFS Archive on lore.kernel.org
 help / Atom feed
* There is no 'no space' message when using xfs with nfs.
@ 2018-12-09 13:07 Guk-Bong Kwon
  2019-01-10 20:09 ` bfields
  0 siblings, 1 reply; 2+ messages in thread
From: Guk-Bong Kwon @ 2018-12-09 13:07 UTC (permalink / raw)
  To: linux-nfs, linux-fsdevel, linux-kernel

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: There is no 'no space' message when using xfs with nfs.
  2018-12-09 13:07 There is no 'no space' message when using xfs with nfs Guk-Bong Kwon
@ 2019-01-10 20:09 ` bfields
  0 siblings, 0 replies; 2+ messages in thread
From: bfields @ 2019-01-10 20:09 UTC (permalink / raw)
  To: Guk-Bong Kwon; +Cc: linux-nfs, linux-fsdevel, linux-kernel

On Sun, Dec 09, 2018 at 10:07:26PM +0900, Guk-Bong Kwon wrote:
> 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?

I don't know.  I'd be inclined to ask the xfs folks.  But 3.4 is 6 years
old, and they may want you to reproduce on more recent upstream.

It might help to look at the traffic in wireshark and try to figure out
which rpc calls are not getting responses from the server.

--b.

> 
> 
> 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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-12-09 13:07 There is no 'no space' message when using xfs with nfs Guk-Bong Kwon
2019-01-10 20:09 ` bfields

Linux-NFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-nfs/0 linux-nfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-nfs linux-nfs/ https://lore.kernel.org/linux-nfs \
		linux-nfs@vger.kernel.org linux-nfs@archiver.kernel.org
	public-inbox-index linux-nfs


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-nfs


AGPL code for this site: git clone https://public-inbox.org/ public-inbox