Displaying 20 results from an estimated 26 matches for "bitd".
Did you mean:
bit
2017 Jun 20
2
trash can feature, crashed???
...:83:glusterd_proc_stop] 0-management: quotad already
stopped
[2017-06-16 16:08:14.412027] I [MSGID: 106568]
[glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: quotad service is
stopped
[2017-06-16 16:08:14.412217] I [MSGID: 106132]
[glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd already
stopped
[2017-06-16 16:08:14.412243] I [MSGID: 106568]
[glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: bitd service is
stopped
[2017-06-16 16:08:14.412422] I [MSGID: 106132]
[glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: scrub already
stopped
[2017-06-16 16:08:14.41...
2017 Jun 20
0
trash can feature, crashed???
...> management: quotad already stopped
> [2017-06-16 16:08:14.412027] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-
> management: quotad service is stopped
> [2017-06-16 16:08:14.412217] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-
> management: bitd already stopped
> [2017-06-16 16:08:14.412243] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-
> management: bitd service is stopped
> [2017-06-16 16:08:14.412422] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-
> management: scrub already stopped
>...
2017 Nov 07
2
Enabling Halo sets volume RO
...:83:glusterd_proc_stop] 0-management: quotad already stopped
[2017-11-07 22:20:15.235512] I [MSGID: 106568] [glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: quotad service is stopped
[2017-11-07 22:20:15.235572] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd already stopped
[2017-11-07 22:20:15.235585] I [MSGID: 106568] [glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: bitd service is stopped
[2017-11-07 22:20:15.235638] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: scrub already stopped
[2017-11-07 22:20:15.23...
2017 Nov 08
0
Enabling Halo sets volume RO
...nagement: quotad
> already stopped
> [2017-11-07 22:20:15.235512] I [MSGID: 106568]
> [glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: quotad
> service is stopped
> [2017-11-07 22:20:15.235572] I [MSGID: 106132]
> [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd
> already stopped
> [2017-11-07 22:20:15.235585] I [MSGID: 106568]
> [glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: bitd service
> is stopped
> [2017-11-07 22:20:15.235638] I [MSGID: 106132]
> [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: scrub
> already...
2017 Dec 15
3
Production Volume will not start
...3079] I [MSGID: 106567] [glusterd-svc-mgmt.c:197:glusterd_svc_start] 0-management: Starting glustershd service
[2017-12-15 18:46:09.005173] I [rpc-clnt.c:1044:rpc_clnt_connection_init] 0-quotad: setting frame-timeout to 600
[2017-12-15 18:46:09.005569] I [rpc-clnt.c:1044:rpc_clnt_connection_init] 0-bitd: setting frame-timeout to 600
[2017-12-15 18:46:09.005673] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd already stopped
[2017-12-15 18:46:09.005689] I [MSGID: 106568] [glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: bitd service is stopped
[2017-12-15 1...
2017 Dec 18
0
Production Volume will not start
...vc-mgmt.c:197:glusterd_svc_start]
> 0-management: Starting glustershd service
>
> [2017-12-15 18:46:09.005173] I [rpc-clnt.c:1044:rpc_clnt_connection_init]
> 0-quotad: setting frame-timeout to 600
>
> [2017-12-15 18:46:09.005569] I [rpc-clnt.c:1044:rpc_clnt_connection_init]
> 0-bitd: setting frame-timeout to 600
>
> [2017-12-15 18:46:09.005673] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop]
> 0-management: bitd already stopped
>
> [2017-12-15 18:46:09.005689] I [MSGID: 106568] [glusterd-svc-mgmt.c:229:glusterd_svc_stop]
> 0-management: bitd se...
2018 Mar 21
2
Brick process not starting after reinstall
...D: 106132]
[glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: quotad
already stopped
[2018-03-20 13:34:14.243866] I [MSGID: 106568]
[glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: quotad
service is stopped
[2018-03-20 13:34:14.243928] I
[rpc-clnt.c:1044:rpc_clnt_connection_init] 0-bitd: setting
frame-timeout to 600
[2018-03-20 13:34:14.244474] I [MSGID: 106132]
[glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd
already stopped
[2018-03-20 13:34:14.244514] I [MSGID: 106568]
[glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: bitd
service is stopped
[2018-03-20 1...
2018 Mar 21
0
Brick process not starting after reinstall
....c:83:glusterd_proc_stop] 0-management: quotad
> already stopped
> [2018-03-20 13:34:14.243866] I [MSGID: 106568]
> [glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: quotad
> service is stopped
> [2018-03-20 13:34:14.243928] I
> [rpc-clnt.c:1044:rpc_clnt_connection_init] 0-bitd: setting
> frame-timeout to 600
> [2018-03-20 13:34:14.244474] I [MSGID: 106132]
> [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd
> already stopped
> [2018-03-20 13:34:14.244514] I [MSGID: 106568]
> [glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: bitd
&g...
2017 Nov 30
2
Problems joining new gluster 3.10 nodes to existing 3.8
....c:83:glusterd_proc_stop] 0-management: quotad
already stopped
[2017-11-30 20:12:26.329558] I [MSGID: 106568]
[glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: quotad
service is stopped
[2017-11-30 20:12:26.329850] I [MSGID: 106132]
[glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd
already stopped
[2017-11-30 20:12:26.329879] I [MSGID: 106568]
[glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: bitd service
is stopped
[2017-11-30 20:12:26.330202] I [MSGID: 106132]
[glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: scrub
already stopped
[2017-11-30 20:12:26.33024...
2018 Mar 20
0
brick processes not starting
...D: 106132]
[glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: quotad
already stopped
[2018-03-20 13:34:14.243866] I [MSGID: 106568]
[glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: quotad
service is stopped
[2018-03-20 13:34:14.243928] I
[rpc-clnt.c:1044:rpc_clnt_connection_init] 0-bitd: setting
frame-timeout to 600
[2018-03-20 13:34:14.244474] I [MSGID: 106132]
[glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd
already stopped
[2018-03-20 13:34:14.244514] I [MSGID: 106568]
[glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: bitd
service is stopped
[2018-03-20 1...
2017 Dec 01
0
Problems joining new gluster 3.10 nodes to existing 3.8
...nagement: quotad
> already stopped
> [2017-11-30 20:12:26.329558] I [MSGID: 106568]
> [glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: quotad
> service is stopped
> [2017-11-30 20:12:26.329850] I [MSGID: 106132]
> [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd
> already stopped
> [2017-11-30 20:12:26.329879] I [MSGID: 106568]
> [glusterd-svc-mgmt.c:229:glusterd_svc_stop] 0-management: bitd service
> is stopped
> [2017-11-30 20:12:26.330202] I [MSGID: 106132]
> [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: scrub
> already...
2018 Apr 18
0
Bitrot strange behavior
Hi Cedric,
Any file is picked up for signing by the bitd process after the
predetermined wait of 120 seconds. This default value is captured in the
volume option 'features.expiry-time' and is configurable - in your case,
it can be set to 0 or 1.
Point 2 is correct. A file corrupted before the bitrot signature is
generated will not be success...
2023 Jan 19
1
really large number of skipped files after a scrub
...en scrubbed. Why are so many files skipped?
>
> See:
>
> gluster volume bitrot gv0 scrub status
>
> Volume name : gv0
>
> State of scrub: Active (Idle)
>
> Scrub impact: aggressive
>
> Scrub frequency: daily
>
> Bitrot error log location: /var/log/glusterfs/bitd.log
>
> Scrubber error log location: /var/log/glusterfs/scrub.log
>
>
> =========================================================
>
> Node: localhost
>
> Number of Scrubbed files: 8112
>
> Number of Skipped files: 51209
>
> Last completed scrub time: 2022-12-1...
2018 Apr 16
2
Bitrot strange behavior
Hello,
I am playing around with the bitrot feature and have some questions:
1. when a file is created, the "trusted.bit-rot.signature? attribute
seems only created approximatively 120 seconds after its creations
(the cluster is idle and there is only one file living on it). Why ?
Is there a way to make this attribute generated at the same time of
the file creation ?
2. corrupting a file
2018 Apr 18
1
Bitrot strange behavior
...r, it would be good to triggered it during a scrub, or with a different tool. Is something like this planned ?
Cheers
?
C?dric Lemarchand
> On 18 Apr 2018, at 07:53, Sweta Anandpara <sanandpa at redhat.com> wrote:
>
> Hi Cedric,
>
> Any file is picked up for signing by the bitd process after the predetermined wait of 120 seconds. This default value is captured in the volume option 'features.expiry-time' and is configurable - in your case, it can be set to 0 or 1.
>
> Point 2 is correct. A file corrupted before the bitrot signature is generated will not be s...
2017 Aug 16
0
Is transport=rdma tested with "stripe"?
...c-mgmt.c:83:glusterd_proc_stop] 0-management: nfs already stopped
[2017-08-16 10:38:48.916008] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: nfs service is stopped
[2017-08-16 10:38:48.916189] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd already stopped
[2017-08-16 10:38:48.916210] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: bitd service is stopped
[2017-08-16 10:38:48.916232] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: scrub already stopped
[2017-08-16 10:38:48.91624...
2017 Aug 15
2
Is transport=rdma tested with "stripe"?
On Tue, Aug 15, 2017 at 01:04:11PM +0000, Hatazaki, Takao wrote:
> Ji-Hyeon,
>
> You're saying that "stripe=2 transport=rdma" should work. Ok, that
> was firstly I wanted to know. I'll put together logs later this week.
Note that "stripe" is not tested much and practically unmaintained. We
do not advise you to use it. If you have large files that you
2017 Aug 18
1
Is transport=rdma tested with "stripe"?
...3:glusterd_proc_stop] 0-management: nfs already stopped
> [2017-08-16 10:38:48.916008] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: nfs service is stopped
> [2017-08-16 10:38:48.916189] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: bitd already stopped
> [2017-08-16 10:38:48.916210] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: bitd service is stopped
> [2017-08-16 10:38:48.916232] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: scrub already stopped
> [2017-08-16...
2018 Apr 18
0
Bitrot - Restoring bad file
On 04/17/2018 06:25 PM, Omar Kohl wrote:
> Hi,
>
> I have a question regarding bitrot detection.
>
> Following the RedHat manual (https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html/administration_guide/bitrot-restore_corrupt_file) I am trying out bad-file-restoration after bitrot.
>
> "gluster volume bitrot VOLNAME status" gets me the
2018 Apr 17
2
Bitrot - Restoring bad file
Hi,
I have a question regarding bitrot detection.
Following the RedHat manual (https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html/administration_guide/bitrot-restore_corrupt_file) I am trying out bad-file-restoration after bitrot.
"gluster volume bitrot VOLNAME status" gets me the GFIDs that are corrupt and on which Host this happens.
As far as I can tell