[LTP] [PATCH] nfs: Adapt the lib to allow to test in 2-host mode

Sebastian Chlad sebastian.chlad@suse.com
Mon Feb 23 18:01:14 CET 2026


On Mon, Feb 23, 2026 at 5:54 PM Cyril Hrubis <chrubis@suse.cz> wrote:
>
> Hi!
> > > Signed-off-by: Sebastian Chlad <sebastian.chlad@suse.com>
> > > ---
> > >  testcases/network/nfs/nfs_stress/nfs_lib.sh | 22 +++++++++++++++++----
> > >  1 file changed, 18 insertions(+), 4 deletions(-)
> >
> > > diff --git a/testcases/network/nfs/nfs_stress/nfs_lib.sh b/testcases/network/nfs/nfs_stress/nfs_lib.sh
> > > index 1ac8bd657..e52f96a5a 100644
> > > --- a/testcases/network/nfs/nfs_stress/nfs_lib.sh
> > > +++ b/testcases/network/nfs/nfs_stress/nfs_lib.sh
> > > @@ -45,7 +45,7 @@ TST_SKIP_FILESYSTEMS="exfat,ext2,ext3,fuse,ntfs,vfat,tmpfs"
> > >  TST_MOUNT_DEVICE=1
> > >  TST_FORMAT_DEVICE=1
> > >  TST_NEEDS_ROOT=1
> > > -TST_NEEDS_CMDS="$TST_NEEDS_CMDS mount exportfs mount.nfs"
> > > +TST_NEEDS_CMDS="$TST_NEEDS_CMDS mount mount.nfs"
>
> I guess that in the furture we want separate scripts for the different
> hosts so that each of them can have proper metadata. I suppose that the
> TST_MOUNT_DEVICE does not apply to the rhost either.
>
> And with that we would need some kind of "master file" that would
> explain which script should be executed on which host etc. But I guess
> that it would be tricky to desing this properly.

Or at least its a bit of a longterm as I see it. As of now, in the
2-host NFS setup, I install nfs-server components to artificially
satisfy the test's requirements.
The patch is the easiest way to untangle that, AFAIK.

cheers,
Seb/

>
> --
> Cyril Hrubis
> chrubis@suse.cz


More information about the ltp mailing list