It works. Thanks, Aravinda.
According to Red Hat's documentation, I can see the hidden folders by using ls
-l command. It seems that this is different from the content in the Red Hat
document.
[root@pgsql-1 ~]# ls -la /mnt/glusterfs_disperse_vol_2/
... cannot see any hidden directory ...
[root@pgsql-1 ~]# ls -la /mnt/glusterfs_disperse_vol_2/.snaps_disperse_vol_2
total 40
drwxr-xr-x 3 root root 8192 Dec 20 20:28 snap_disperse_vol_2
drwxr-xr-x 3 root root 8192 Dec 20 20:28 snap_disperse_vol_2_2
drwxr-xr-x 3 root root 8192 Dec 21 15:37
snap_disperse_vol_2_3_GMT-2021.12.21-07.39.00
drwxr-xr-x 3 root root 8192 Dec 21 15:37 snap_disperse_vol_2_test1
drwxr-xr-x 3 root root 8192 Dec 21 15:37 snap_disperse_vol_2_test2
--
Lee.T
At 2021-12-22 14:09:55, "Aravinda VK" <[email protected]> wrote:
Observed one more thing from your Volume info. Snaps directory is configured as
----
features.snapshot-directory: .snaps_disperse_vol_2
----
Try `ls /media3/.snaps_disperse_vol_2` and `ls
/mnt/disperse_vol_2/.snaps_disperse_vol_2`
On 22-Dec-2021, at 11:07 AM, samfisher1 <[email protected]> wrote:
.snaps directory doesn't exist.
[root@pgsql-1 ~]# df -hT /mnt/glusterfs_disperse_vol_2
Filesystem Type Size Used Avail Use% Mounted on
pgsql-1:/disperse_vol_2.tcp fuse.glusterfs 38G 525M 38G 2%
/mnt/glusterfs_disperse_vol_2
[root@pgsql-1 ~]# ls -la /mnt/glusterfs_disperse_vol_2/.snap*
ls: cannot access /mnt/glusterfs_disperse_vol_2/.snap*: No such file or
directory
[root@pgsql-1 ~]# ls -la /mnt/glusterfs_disperse_vol_2/.snaps
ls: cannot access /mnt/glusterfs_disperse_vol_2/.snaps: No such file or
directory
It makes me crazy, I don't have any clues to solve this problem.
--
Lee.T
At 2021-12-22 12:30:27, "Aravinda VK" <[email protected]> wrote:
I think `.snaps` is not shown when you do `ls` it is a virtual directory.
Please confirm if it is not visible when you run ls command as below.
ls /media3/.snaps
In the fuse example, Snap volume itself is mounted and not using User
Serviceable snapshots feature. Try mounting as below and see if .snaps
directory is visible.
mount -t glusterfs 10.10.10.1:/disperse_vol_2 /mnt/disperse_vol_2
ls /mnt/disperse_vol_2/.snaps
Aravinda Vishwanathapura
https://kadalu.io
On 22-Dec-2021, at 8:37 AM, samfisher1 <[email protected]> wrote:
Tks, Aravinda
The snapshot is already activated and you can see the snapshot status is
started in the previous command output.
--
Lee.T
At 2021-12-21 20:13:47, "Aravinda VK" <[email protected]> wrote:
Is the Snapshot activated?
gluster snapshot activate <snapname>
Aravinda Vishwanathapura
https://kadalu.io
On 21-Dec-2021, at 4:06 PM, samfisher1 <[email protected]> wrote:
Sorry for disturbing you... Uh, I met a very strange GlusterFS problem: I can
access snapshots by using FUSE mount and it works fine. However, when I test
Gluster USER-SERVICEABLE snapshots feature, I find I cannot see .snap directory
in the NFS shared directory. So pls help me solve this problem, many thanks~
My Gluster version is glusterfs 8.6. My OS version is CentOS 7.9.2009
Here is gluster volume and snapshot info.
```
[root@pgsql-1 media-cifs]# gluster v info disperse_vol_2
Volume Name: disperse_vol_2
Type: Disperse
Volume ID: a8bd1d15-20c0-43af-a66e-eb166bd92f4c
Status: Started
Snapshot Count: 5
Number of Bricks: 1 x (4 + 2) = 6
Transport-type: tcp
Bricks:
Brick1: pgsql-1:/run/gluster/snaps/1c51095f455d4b93b1dd2fcfdfdb6127/brick1/data
Brick2: pgsql-2:/run/gluster/snaps/1c51095f455d4b93b1dd2fcfdfdb6127/brick2/data
Brick3: pgsql-3:/run/gluster/snaps/1c51095f455d4b93b1dd2fcfdfdb6127/brick3/data
Brick4: pgsql-1:/run/gluster/snaps/1c51095f455d4b93b1dd2fcfdfdb6127/brick4/data
Brick5: pgsql-2:/run/gluster/snaps/1c51095f455d4b93b1dd2fcfdfdb6127/brick5/data
Brick6: pgsql-3:/run/gluster/snaps/1c51095f455d4b93b1dd2fcfdfdb6127/brick6/data
Options Reconfigured:
features.show-snapshot-directory: on
features.snapshot-directory: .snaps_disperse_vol_2
features.uss: enable
storage.fips-mode-rchecksum: on
transport.address-family: inet
nfs.disable: on
features.quota: off
features.inode-quota: off
features.quota-deem-statfs: off
features.barrier: disable
snap-activate-on-create: disable
cluster.enable-shared-storage: enable
```
Here is the snapshot info:
```
[root@pgsql-1 media-cifs]# gluster snap info snap_disperse_vol_2_test1
Snapshot : snap_disperse_vol_2_test1
Snap UUID : 8cab3954-3055-43aa-b34f-bbff58375881
Created : 2021-12-21 09:23:43
Snap Volumes:
Snap Volume Name : 4dd90c9a08f1449fb865a368676ebd61
Origin Volume name : disperse_vol_2
Snaps taken for disperse_vol_2 : 5
Snaps available for disperse_vol_2 : 251
Status : Started
```
But I can not see any .snaps directory in the media3 directory.
```
[root@pgsql-1 media-cifs]# mount -t nfs 10.10.10.1:/disperse_vol_2 /media3/
[root@pgsql-1 media-cifs]# ls -a /media3
. 21.txt 24.txt 27.txt 2.txt 32.txt 35.txt
.. 22.txt 25.txt 28.txt 30.txt 33.txt 36.txt
```
I can access snapshot by using FUSE mount and it works fine.
```
[root@pgsql-1 media-cifs]# mount -t glusterfs
10.10.10.1:/snaps/snap_disperse_vol_2_test1/disperse_vol_2 /mnt/snap/
[root@pgsql-1 media-cifs]# ls /mnt/snap/
20.txt 23.txt 26.txt 29.txt 31.txt 34.txt 37.txt 3.txt 42.txt 45.txt
48.txt 50.txt 7.txt
21.txt 24.txt 27.txt 2.txt 32.txt 35.txt 38.txt 40.txt 43.txt 46.txt
49.txt 5.txt 8.txt
22.txt 25.txt 28.txt 30.txt 33.txt 36.txt 39.txt 41.txt 44.txt 47.txt
4.txt 6.txt 9.txt
```
I haven't any clues to solve this problems, pls help me. tks~
--
Lee.T
________
Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
[email protected]
https://lists.gluster.org/mailman/listinfo/gluster-users
Aravinda Vishwanathapura
https://kadalu.io
________
Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
[email protected]
https://lists.gluster.org/mailman/listinfo/gluster-users