<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<font size="2" face="Courier 10 Pitch">hi guys.<br>
<br>
I have a replica volume which is mounted via loopback and mounts a
okey.<br>
</font><font size="2" face="Courier 10 Pitch">-> $ mount | grep
VMs<br>
127.0.0.1:/VMsy on /00-VMsy type fuse.glusterfs
(rw,relatime,user_id=0,group_id=0,allow_other,max_read=131072)<br>
<br>
</font><font size="2" face="Courier 10 Pitch">However, when
something begins to operate on this fuse mounted path, then errors
show:<br>
...<br>
The message "W [MSGID: 114031]
[client-rpc-fops_v2.c:1881:client4_0_seek_cbk] 0-VMsy-client-0:
remote operation failed. [{errno=6}, {error=No such device or
address}]" repeated 163398 times between [2025-06-25
11:01:29.439813 +0000] and [2025-06-25 11:02:34.980956 +0000]<br>
...<br>
This above is a result of simple 'cp' off the fuse mount to a
separate filesystem. 'cp' gets stuck forever.<br>
<br>
</font><font size="2" face="Courier 10 Pitch">However, one peer, out
of there, does not suffer from this issue - this box works as
expected, nicely.<br>
Now - this issue does not occur at all, on any of three boxes, if
volume is mounted this way:<br>
10.1.1.100,10.1.1.101,10.1.1.99:/VMsy<br>
<br>
All three peers/boxes are "virtually" identical, yet there is one
more "oddity" on the peer which does _not_ fail with above error,
namely:<br>
-> $ du -xh /00-VMsy//enc.vdb.back1.proxmox.qcow2<br>
71G /00-VMsy//enc.vdb.back1.proxmox.qcow2<br>
where other two:<br>
-> $ du -sh /00-VMsy//enc.vdb.back1.proxmox.qcow2<br>
2.9G /00-VMsy//enc.vdb.back1.proxmox.qcow2<br>
'df' also reports that way.<br>
71G is virtual size of qcow2 file.<br>
I'd put aside for now - still an interesting question - mount any
other way VS mount to 127.0.0.1 and ask: how to make "failing"
boxes to behave like the box which is error-free?<br>
All thoughts are much appreciated.<br>
<br>
Volume Name: VMsy<br>
Type: Replicate<br>
Volume ID: b843d9ea-b500-4b4c-9f0a-f2bae507d491<br>
Status: Started<br>
Snapshot Count: 0<br>
Number of Bricks: 1 x (2 + 1) = 3<br>
Transport-type: tcp<br>
Bricks:<br>
Brick1: 10.1.1.100:/devs/00.GLUSTERs/VMsy<br>
Brick2: 10.1.1.101:/devs/00.GLUSTERs/VMsy<br>
Brick3: 10.1.1.99:/devs/00.GLUSTERs/VMsy-arbiter (arbiter)<br>
...<br>
<br>
-> $ gluster --version<br>
glusterfs 11.1<br>
<br>
</font>
</body>
</html>