search for: nch20909

Displaying 8 results from an estimated 8 matches for "nch20909".

2018 Apr 09
2
New 3.12.7 possible split-brain on replica 3
...private/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/dir11/dir12_Archiv/azipfiledir.zip/OC_DEFAULT_MODULE/problematicfile' Size: 0 Blocks: 0 IO Block: 131072 regular empty file Device: 1eh/30d Inode: 13600685574951729371 Links: 1 Access: (0644/-rw-r--r--) Uid: (20909/nch20909) Gid: (20909/nch20909) Access: 2018-04-09 08:58:54.311556621 +0200 Modify: 2018-04-09 08:58:54.311556621 +0200 Change: 2018-04-09 08:58:54.423555611 +0200 Birth: - ?? ??????? Original Message ??????? On April 9, 2018 9:49 AM, mabi <mabi at protonmail.ch> wrote: > ?? > > Here w...
2018 Apr 09
2
New 3.12.7 possible split-brain on replica 3
...7/dir8/dir9/dir10/dir11/dir12_Archiv/azipfiledir.zip/OC_DEFAULT_MODULE/problematicfile' > > > > Size: 0 Blocks: 0 IO Block: 131072 regular empty file > > > > Device: 1eh/30d Inode: 13600685574951729371 Links: 1 > > > > Access: (0644/-rw-r--r--) Uid: (20909/nch20909) Gid: (20909/nch20909) > > > > Access: 2018-04-09 08:58:54.311556621 +0200 > > > > Modify: 2018-04-09 08:58:54.311556621 +0200 > > > > Change: 2018-04-09 08:58:54.423555611 +0200 > > > > Birth: - > > > > ??????? Original Message ?????...
2018 Apr 09
0
New 3.12.7 possible split-brain on replica 3
...2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/dir11/dir12_Archiv/azipfiledir.zip/OC_DEFAULT_MODULE/problematicfile' > Size: 0 Blocks: 0 IO Block: 131072 regular empty file > Device: 1eh/30d Inode: 13600685574951729371 Links: 1 > Access: (0644/-rw-r--r--) Uid: (20909/nch20909) Gid: (20909/nch20909) > Access: 2018-04-09 08:58:54.311556621 +0200 > Modify: 2018-04-09 08:58:54.311556621 +0200 > Change: 2018-04-09 08:58:54.423555611 +0200 > Birth: - > ?? > > ??????? Original Message ??????? > > On April 9, 2018 9:49 AM, mabi <mabi at protonm...
2018 Apr 09
0
New 3.12.7 possible split-brain on replica 3
...10/dir11/dir12_Archiv/azipfiledir.zip/OC_DEFAULT_MODULE/problematicfile' >>> >>> Size: 0 Blocks: 0 IO Block: 131072 regular empty file >>> >>> Device: 1eh/30d Inode: 13600685574951729371 Links: 1 >>> >>> Access: (0644/-rw-r--r--) Uid: (20909/nch20909) Gid: (20909/nch20909) >>> >>> Access: 2018-04-09 08:58:54.311556621 +0200 >>> >>> Modify: 2018-04-09 08:58:54.311556621 +0200 >>> >>> Change: 2018-04-09 08:58:54.423555611 +0200 >>> >>> Birth: - >>> >>> ?????...
2018 Apr 09
2
New 3.12.7 possible split-brain on replica 3
...ULT_MODULE/problematicfile' > > > > > > > > Size: 0 Blocks: 0 IO Block: 131072 regular empty file > > > > > > > > Device: 1eh/30d Inode: 13600685574951729371 Links: 1 > > > > > > > > Access: (0644/-rw-r--r--) Uid: (20909/nch20909) Gid: (20909/nch20909) > > > > > > > > Access: 2018-04-09 08:58:54.311556621 +0200 > > > > > > > > Modify: 2018-04-09 08:58:54.311556621 +0200 > > > > > > > > Change: 2018-04-09 08:58:54.423555611 +0200 > > > >...
2018 Apr 09
0
New 3.12.7 possible split-brain on replica 3
..._MODULE/problematicfile' >>>>> >>>>> Size: 0 Blocks: 0 IO Block: 131072 regular empty file >>>>> >>>>> Device: 1eh/30d Inode: 13600685574951729371 Links: 1 >>>>> >>>>> Access: (0644/-rw-r--r--) Uid: (20909/nch20909) Gid: (20909/nch20909) >>>>> >>>>> Access: 2018-04-09 08:58:54.311556621 +0200 >>>>> >>>>> Modify: 2018-04-09 08:58:54.311556621 +0200 >>>>> >>>>> Change: 2018-04-09 08:58:54.423555611 +0200 >>>>&g...
2018 Apr 09
0
New 3.12.7 possible split-brain on replica 3
Here would be also the corresponding log entries on a gluster node brick log file: [2018-04-09 06:58:47.363536] W [MSGID: 113093] [posix-gfid-path.c:84:posix_remove_gfid2path_xattr] 0-myvol-private-posix: removing gfid2path xattr failed on /data/myvol-private/brick/.glusterfs/12/67/126759f6-8364-453c-9a9c-d9ed39198b7a: key = trusted.gfid2path.2529bb66b56be110 [No data available] [2018-04-09
2018 Apr 09
2
New 3.12.7 possible split-brain on replica 3
Hello, Last Friday I upgraded my GlusterFS 3.10.7 3-way replica (with arbitrer) cluster to 3.12.7 and this morning I got a warning that 9 files on one of my volumes are not synced. Ineeded checking that volume with a "volume heal info" shows that the third node (the arbitrer node) has 9 files to be healed but are not being healed automatically. All nodes were always online and there