On Fri, Jul 12, 2024 at 05:49:24PM GMT, Zorro Lang wrote:
> On Sun, Jun 30, 2024 at 11:52:43PM +0200, Daniel Gomez via B4 Relay wrote:
> > From: Daniel Gomez <da.gomez@xxxxxxxxxxx>
> >
> > MOUNT_OPTIONS for scratch devices do not have specific fs mount options
> > values (such as TMPFS_MOUNT_OPTIONS) from the config section. So, allow
> > the scratch mount options to inherit section config values by reading
> > them from _common_mount_opts().
> >
> > Move $* to the end so scratch device can be umount/mount. Otherwise, we
> > end up with multiple mounts in the same scratch directory.
> >
> > Signed-off-by: Daniel Gomez <da.gomez@xxxxxxxxxxx>
> > ---
> > common/rc | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/common/rc b/common/rc
> > index 51827119c..627dbaaaa 100644
> > --- a/common/rc
> > +++ b/common/rc
> > @@ -231,8 +231,8 @@ _scratch_mount_options()
> > {
> > _scratch_options mount
> >
> > - echo `_common_dev_mount_options $*` $SCRATCH_OPTIONS \
> > - $SCRATCH_DEV $SCRATCH_MNT
> > + echo `_common_mount_opts` $SCRATCH_OPTIONS \
> > + $SCRATCH_DEV $SCRATCH_MNT $*
>
> Oh, you want to get the "specific fs mount options". But sorry this
> change brings in many regression failures, e.g. generic/219, generic/691,
> generc/381, generic/382 ... fail (on ext4 and so on).
I'm assuming the scratch device should have the default mount options provided
by _common_mount_opts(). Otherwise, I would have to include the default mount
options ('-o size=1G <section-mount-option>') in every section of my config. So,
why a scratch device should not have the defaults?
>
> Thanks,
> Zorro
>
> > }
> >
> > _supports_filetype()
> >
> > --
> > 2.43.0
> >
> >
> >
