Linux-NFS Archive on
 help / color / Atom feed
* generic/495: swap on sparse file over NFS
@ 2019-09-23 20:00 bfields
  2019-09-23 20:21 ` Darrick J. Wong
  0 siblings, 1 reply; 2+ messages in thread
From: bfields @ 2019-09-23 20:00 UTC (permalink / raw)
  To: fstests; +Cc: linux-nfs

I'm updating to a newer xfstests and seeing:

generic/495     - output mismatch (see
    --- tests/generic/495.out   2019-09-18 17:28:00.834721480 -0400
    +++ /root/xfstests-dev/results//generic/495.out.bad 2019-09-20 13:34:01.1568
89741 -0400
    @@ -1,5 +1,4 @@
     QA output created by 495
     File with holes
    -swapon: Invalid argument
     Empty swap file (only swap header)
     swapon: Invalid argument

If I understand correctly, it's requiring swapon to fail on a sparse
file, which isn't going to happen on NFS, where the sparsenes of the
file isn't really the client's concern.

Is it really correct to *require* swapon to fail in this case?


^ 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 --
2019-09-23 20:00 generic/495: swap on sparse file over NFS bfields
2019-09-23 20:21 ` Darrick J. Wong

Linux-NFS Archive on

Archives are clonable:
	git clone --mirror 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/ \
	public-inbox-index linux-nfs

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone