linux-toradex.git/fs/nfs/flexfilelayout, branch v4.4.76

pNFS/flexfiles: Fix layoutcommit after a commit to DS

2016-10-07T13:23:45+00:00

commit c001c87a63aa2f35358e33eb05e45e4cbcb34f54 upstream.

We should always do a layoutcommit after commit to DS, except if
the layout segment we're using has set FF_FLAGS_NO_LAYOUTCOMMIT.

Fixes: d67ae825a59d ("pnfs/flexfiles: Add the FlexFile Layout Driver")
Signed-off-by: Trond Myklebust 
Signed-off-by: Greg Kroah-Hartman

pNFS/flexfiles: Fix an XDR encoding bug in layoutreturn

2016-02-25T20:01:18+00:00

commit 082fa37d1351a41afc491d44a1d095cb8d919aa2 upstream.

We must not skip encoding the statistics, or the server will see an
XDR encoding error.

Signed-off-by: Trond Myklebust 
Signed-off-by: Greg Kroah-Hartman

pNFS/flexfiles: Fix an Oopsable typo in ff_mirror_match_fh()

2016-02-25T20:01:18+00:00

commit 86fb449b07b8215443a30782dca5755d5b8b0577 upstream.

Jeff reports seeing an Oops in ff_layout_alloc_lseg. Turns out
copy+paste has played cruel tricks on a nested loop.

Reported-by: Jeff Layton 
Signed-off-by: Trond Myklebust 
Signed-off-by: Greg Kroah-Hartman

pNFS/flexfiles: Add support for FF_FLAGS_NO_IO_THRU_MDS

2015-11-02T18:50:37+00:00

For loosely coupled pNFS/flexfiles systems, there is often no advantage
at all in going through the MDS for I/O, since the MDS is subject to
the same limitations as all other clients when talking to DSes. If a
DS is unresponsive, I/O through the MDS will fail.

For such systems, the only scalable solution is to have the pNFS clients
retry doing pNFS, and so the protocol now provides a flag that allows
the pNFS server to signal this.

If LAYOUTGET returns FF_FLAGS_NO_IO_THRU_MDS, then we should assume that
the MDS wants the client to retry using these devices, even if they were
previously marked as being unavailable. To do so, we add a helper,
ff_layout_mark_devices_valid() that will be called from layoutget.

Signed-off-by: Trond Myklebust

pNFS/flexfiles: When mirrored, retry failed reads by switching mirrors

2015-11-02T18:50:35+00:00

If the pNFS/flexfiles file is mirrored, and a read to one mirror fails,
then we should bump the mirror index, so that we retry to a different
mirror. Once we've iterated through all mirrors and all failed, we can
return the layout and issue a new LAYOUTGET.

Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: Clean up ff_layout_write_done_cb/ff_layout_commit_done_cb

2015-09-02T22:24:54+00:00

Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: Mark the layout for return in ff_layout_io_track_ds_error()

2015-09-02T22:24:26+00:00

When I/O cannot complete due to a fatal error on the DS, ensure that we
invalidate the corresponding layout segment and return it.

Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: Mark layout for return if the mirrors are invalid

2015-09-01T22:12:11+00:00

If a read-write layout has an invalid mirror, then we should
mark it as invalid, and return it.
If a read-only layout has an invalid mirror, then mark it as invalid
and check if there is still at least one valid mirror before we return
it.

Note: Also fix incorrect use of pnfs_generic_mark_devid_invalid().
We really want nfs4_mark_deviceid_unavailable().

Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: RW layouts are valid only if all mirrors are valid

2015-09-01T22:12:11+00:00

Unlike read layouts, the writeable layout cannot fall back to using only
one of the mirrors. It need to write to all of them.

Signed-off-by: Trond Myklebust

NFSv4.1/flexfiles: Fix incorrect usage of pnfs_generic_mark_devid_invalid()

2015-09-01T22:12:11+00:00

Unlike the files layout, flexfiles does not test for the NFS_DEVICEID_INVALID
flag. Instead it relies on NFS_DEVICEID_UNAVAILABLE.
Fix is to replace with nfs4_mark_deviceid_unavailable().

Signed-off-by: Trond Myklebust