[Bugs] [Bug 1793042] Client receives no error when triggering autocommit with WRITE FOP

bugzilla at redhat.com bugzilla at redhat.com
Mon Jan 20 15:45:34 UTC 2020


https://bugzilla.redhat.com/show_bug.cgi?id=1793042



--- Comment #3 from david.spisla at iternity.com ---
I forgot to give you our volume options:

Volume Name: repo2
Type: Replicate
Volume ID: 47b9d9e4-be80-4138-8a4c-d3fb77ba2db0
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: fs-davids-c1-n1:/gluster/brick3/glusterbrick
Brick2: fs-davids-c1-n2:/gluster/brick3/glusterbrick
Brick3: fs-davids-c1-n3:/gluster/arbiter3/glusterbrick (arbiter)
Options Reconfigured:
diagnostics.client-log-level: INFO
diagnostics.brick-log-level: INFO
performance.client-io-threads: off
nfs.disable: on
transport.address-family: inet
user.smb: disable
features.read-only: off
features.worm: off
features.worm-file-level: on
features.retention-mode: enterprise
features.default-retention-period: 120
network.ping-timeout: 10
features.cache-invalidation: on
features.cache-invalidation-timeout: 600
performance.nl-cache: on
performance.nl-cache-timeout: 600
client.event-threads: 32
server.event-threads: 32
cluster.lookup-optimize: on
performance.stat-prefetch: on
performance.cache-invalidation: on
performance.md-cache-timeout: 600
performance.cache-samba-metadata: on
performance.cache-ima-xattrs: on
performance.io-thread-count: 64
cluster.use-compound-fops: on
performance.cache-size: 512MB
performance.cache-refresh-timeout: 10
performance.read-ahead: off
performance.write-behind-window-size: 4MB
performance.write-behind: off
storage.build-pgfid: on
features.utime: on
storage.ctime: on
cluster.quorum-type: auto
features.bitrot: on
features.scrub: Active
features.scrub-freq: daily

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list