This is a multipart message in MIME format.
uwXgvNCO8H_related
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Type: multipart/related;
boundary="--uwXgvNCO8H_related" charset="utf-8"
What about umount -f -l ?From: Users
This is a multipart message in MIME format.
Rq39EWBVFo_related
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Type: multipart/related;
boundary="--Rq39EWBVFo_related" charset="utf-8"
It does not matter if ip resource starts on n=
On 11.04.2023 17:35, Miro Igov wrote:
Hello,
I have a node nas-sync-test1 with NFS server and NFS export running and
another node intranet-test1 with data_1 fs mount:
primitive data_1 Filesystem \
params device="nas-sync-test1:/home/pharmya/NAS" fstype=nfs
options=v4
gfs2-utils contains the tools needed to create, check, modify and
inspect gfs2 filesystems along with support scripts needed on every gfs2
cluster node.
This minor release includes fixes for a small number of issues
discovered in 3.5.0, including test failures that occur on 32-bit
On Tue, 2023-04-11 at 17:31 +0300, Miro Igov wrote:
> I fixed the issue by changing location definition from:
>
> location intranet-ip_on_any_nginx intranet-ip \
> rule -inf: opa-nginx_1_active eq 0 \
> rule -inf: opa-nginx_2_active eq 0
>
> To:
>
> location
Hello,
I have a node nas-sync-test1 with NFS server and NFS export running and
another node intranet-test1 with data_1 fs mount:
primitive data_1 Filesystem \
params device="nas-sync-test1:/home/pharmya/NAS" fstype=nfs
options=v4 directory="/data/synology/pharmya_office/NAS_Sync/NAS"
I fixed the issue by changing location definition from:
location intranet-ip_on_any_nginx intranet-ip \
rule -inf: opa-nginx_1_active eq 0 \
rule -inf: opa-nginx_2_active eq 0
To:
location intranet-ip_on_any_nginx intranet-ip \
rule opa-nginx_1_active eq 1 \
