Re: [Gluster-users] Trying out changelog xlator - human readable output?
Hello Sunny,
thank you for the hint. Ich will try this out!
Regards
David
Am Mo., 16. März 2020 um 11:49 Uhr schrieb Sunny Kumar :
> Hi David,
>
> Link is here:
>
> Changelog parser: https://github.com/aravindavk/gluster_georep_scripts
>
> /sunny
>
> On Mon, Mar 16, 2020 at 10:47 AM Sunny Kumar wrote:
> >
> > Hi David,
> >
> > You can try this Gluster Changelog Parser[1] which converts changelog
> > into human readable format.
> >
> > [1].https://github.com/kotreshhr/gluster-geo-rep
> >
> > /sunny
> >
> > On Mon, Mar 16, 2020 at 10:41 AM David Spisla
> wrote:
> > >
> > > Dear Gluster Community,
> > > I trying out the changelog xlator to evaluate if it can be used as a
> kind of audit log when accessing a volume via nfs. Here is the entry in the
> CHANGELOG file when performing $ echo test >> file1.txt && chmod 444
> file1.txt :
> > >
> > > GlusterFS Changelog | version: v1.2 | encoding : 2
> > >
> Ef845378a-f8d4-4dd2-a0fc-946e3d247f84234366553465534ac80f4db-3a41-42f6-b831-49cd9882a564/file1.txtDf845378a-f8d4-4dd2-a0fc-946e3d247f84Mf845378a-f8d4-4dd2-a0fc-946e3d247f8438
> > >
> > > How one can make it human readable e.g. with full path information?
> > >
> > > Regards
> > > David Spisla
> > >
> > > ps Below my volume info!
> > >
> > > Here is my volume setting:
> > > fs-davids-c2-n1:~ # gluster vo info repo2
> > >
> > > Volume Name: repo2
> > > Type: Replicate
> > > Volume ID: 8b7b64d3-6019-4dac-b2cf-b78e78172724
> > > Status: Started
> > > Snapshot Count: 0
> > > Number of Bricks: 1 x (2 + 1) = 3
> > > Transport-type: tcp
> > > Bricks:
> > > Brick1: fs-davids-c2-n1:/gluster/brick3/glusterbrick
> > > Brick2: fs-davids-c2-n2:/gluster/brick3/glusterbrick
> > > Brick3: fs-davids-c2-n3:/gluster/arbiter3/glusterbrick (arbiter)
> > > Options Reconfigured:
> > > changelog.changelog: on
> > > changelog.rollover-time: 36000
> > > features.scrub-freq: daily
> > > features.scrub: Active
> > > features.bitrot: on
> > > cluster.quorum-type: auto
> > > features.default-retention-period: 120
> > > storage.ctime: on
> > > features.utime: on
> > > storage.build-pgfid: on
> > > performance.write-behind: off
> > > performance.write-behind-window-size: 4MB
> > > performance.read-ahead: off
> > > performance.cache-refresh-timeout: 10
> > > performance.cache-size: 512MB
> > > cluster.use-compound-fops: on
> > > performance.io-thread-count: 64
> > > performance.cache-ima-xattrs: on
> > > performance.cache-samba-metadata: on
> > > performance.md-cache-timeout: 600
> > > performance.cache-invalidation: on
> > > performance.stat-prefetch: on
> > > cluster.lookup-optimize: on
> > > server.event-threads: 32
> > > client.event-threads: 32
> > > performance.nl-cache-timeout: 600
> > > performance.nl-cache: on
> > > features.cache-invalidation-timeout: 600
> > > features.cache-invalidation: on
> > > network.ping-timeout: 10
> > > features.retention-mode: enterprise
> > > features.worm-file-level: on
> > > features.worm: off
> > > features.read-only: off
> > > user.smb: disable
> > > transport.address-family: inet
> > > nfs.disable: on
> > > performance.client-io-threads: off
> > > changelog.capture-del-path: on
> > > changelog.encoding: ascii
> > >
> > > Changelog settings:
> > > fs-davids-c2-n1:~ # gluster vo get repo2 all | grep changelog
> > > changelog.changelog on
> > > changelog.changelog-dir {{ brick.path
> }}/.glusterfs/changelogs
> > > changelog.encoding ascii
> > > changelog.rollover-time 36000
> > > changelog.fsync-interval5
> > > changelog.changelog-barrier-timeout 120
> > > changelog.capture-del-path on
> > >
> > >
> > >
> > >
> > > Community Meeting Calendar:
> > >
> > > Schedule -
> > > Every Tuesday at 14:30 IST / 09:00 UTC
> > > Bridge: https://bluejeans.com/441850968
> > >
> > > Gluster-users mailing list
> > > Gluster-users@gluster.org
> > > https://lists.gluster.org/mailman/listinfo/gluster-users
>
>
Community Meeting Calendar:
Schedule -
Every Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Trying out changelog xlator - human readable output?
Hi David,
Link is here:
Changelog parser: https://github.com/aravindavk/gluster_georep_scripts
/sunny
On Mon, Mar 16, 2020 at 10:47 AM Sunny Kumar wrote:
>
> Hi David,
>
> You can try this Gluster Changelog Parser[1] which converts changelog
> into human readable format.
>
> [1].https://github.com/kotreshhr/gluster-geo-rep
>
> /sunny
>
> On Mon, Mar 16, 2020 at 10:41 AM David Spisla wrote:
> >
> > Dear Gluster Community,
> > I trying out the changelog xlator to evaluate if it can be used as a kind
> > of audit log when accessing a volume via nfs. Here is the entry in the
> > CHANGELOG file when performing $ echo test >> file1.txt && chmod 444
> > file1.txt :
> >
> > GlusterFS Changelog | version: v1.2 | encoding : 2
> > Ef845378a-f8d4-4dd2-a0fc-946e3d247f84234366553465534ac80f4db-3a41-42f6-b831-49cd9882a564/file1.txtDf845378a-f8d4-4dd2-a0fc-946e3d247f84Mf845378a-f8d4-4dd2-a0fc-946e3d247f8438
> >
> > How one can make it human readable e.g. with full path information?
> >
> > Regards
> > David Spisla
> >
> > ps Below my volume info!
> >
> > Here is my volume setting:
> > fs-davids-c2-n1:~ # gluster vo info repo2
> >
> > Volume Name: repo2
> > Type: Replicate
> > Volume ID: 8b7b64d3-6019-4dac-b2cf-b78e78172724
> > Status: Started
> > Snapshot Count: 0
> > Number of Bricks: 1 x (2 + 1) = 3
> > Transport-type: tcp
> > Bricks:
> > Brick1: fs-davids-c2-n1:/gluster/brick3/glusterbrick
> > Brick2: fs-davids-c2-n2:/gluster/brick3/glusterbrick
> > Brick3: fs-davids-c2-n3:/gluster/arbiter3/glusterbrick (arbiter)
> > Options Reconfigured:
> > changelog.changelog: on
> > changelog.rollover-time: 36000
> > features.scrub-freq: daily
> > features.scrub: Active
> > features.bitrot: on
> > cluster.quorum-type: auto
> > features.default-retention-period: 120
> > storage.ctime: on
> > features.utime: on
> > storage.build-pgfid: on
> > performance.write-behind: off
> > performance.write-behind-window-size: 4MB
> > performance.read-ahead: off
> > performance.cache-refresh-timeout: 10
> > performance.cache-size: 512MB
> > cluster.use-compound-fops: on
> > performance.io-thread-count: 64
> > performance.cache-ima-xattrs: on
> > performance.cache-samba-metadata: on
> > performance.md-cache-timeout: 600
> > performance.cache-invalidation: on
> > performance.stat-prefetch: on
> > cluster.lookup-optimize: on
> > server.event-threads: 32
> > client.event-threads: 32
> > performance.nl-cache-timeout: 600
> > performance.nl-cache: on
> > features.cache-invalidation-timeout: 600
> > features.cache-invalidation: on
> > network.ping-timeout: 10
> > features.retention-mode: enterprise
> > features.worm-file-level: on
> > features.worm: off
> > features.read-only: off
> > user.smb: disable
> > transport.address-family: inet
> > nfs.disable: on
> > performance.client-io-threads: off
> > changelog.capture-del-path: on
> > changelog.encoding: ascii
> >
> > Changelog settings:
> > fs-davids-c2-n1:~ # gluster vo get repo2 all | grep changelog
> > changelog.changelog on
> > changelog.changelog-dir {{ brick.path
> > }}/.glusterfs/changelogs
> > changelog.encoding ascii
> > changelog.rollover-time 36000
> > changelog.fsync-interval5
> > changelog.changelog-barrier-timeout 120
> > changelog.capture-del-path on
> >
> >
> >
> >
> > Community Meeting Calendar:
> >
> > Schedule -
> > Every Tuesday at 14:30 IST / 09:00 UTC
> > Bridge: https://bluejeans.com/441850968
> >
> > Gluster-users mailing list
> > Gluster-users@gluster.org
> > https://lists.gluster.org/mailman/listinfo/gluster-users
Community Meeting Calendar:
Schedule -
Every Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Trying out changelog xlator - human readable output?
Hi David,
You can try this Gluster Changelog Parser[1] which converts changelog
into human readable format.
[1].https://github.com/kotreshhr/gluster-geo-rep
/sunny
On Mon, Mar 16, 2020 at 10:41 AM David Spisla wrote:
>
> Dear Gluster Community,
> I trying out the changelog xlator to evaluate if it can be used as a kind of
> audit log when accessing a volume via nfs. Here is the entry in the CHANGELOG
> file when performing $ echo test >> file1.txt && chmod 444 file1.txt :
>
> GlusterFS Changelog | version: v1.2 | encoding : 2
> Ef845378a-f8d4-4dd2-a0fc-946e3d247f84234366553465534ac80f4db-3a41-42f6-b831-49cd9882a564/file1.txtDf845378a-f8d4-4dd2-a0fc-946e3d247f84Mf845378a-f8d4-4dd2-a0fc-946e3d247f8438
>
> How one can make it human readable e.g. with full path information?
>
> Regards
> David Spisla
>
> ps Below my volume info!
>
> Here is my volume setting:
> fs-davids-c2-n1:~ # gluster vo info repo2
>
> Volume Name: repo2
> Type: Replicate
> Volume ID: 8b7b64d3-6019-4dac-b2cf-b78e78172724
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1 x (2 + 1) = 3
> Transport-type: tcp
> Bricks:
> Brick1: fs-davids-c2-n1:/gluster/brick3/glusterbrick
> Brick2: fs-davids-c2-n2:/gluster/brick3/glusterbrick
> Brick3: fs-davids-c2-n3:/gluster/arbiter3/glusterbrick (arbiter)
> Options Reconfigured:
> changelog.changelog: on
> changelog.rollover-time: 36000
> features.scrub-freq: daily
> features.scrub: Active
> features.bitrot: on
> cluster.quorum-type: auto
> features.default-retention-period: 120
> storage.ctime: on
> features.utime: on
> storage.build-pgfid: on
> performance.write-behind: off
> performance.write-behind-window-size: 4MB
> performance.read-ahead: off
> performance.cache-refresh-timeout: 10
> performance.cache-size: 512MB
> cluster.use-compound-fops: on
> performance.io-thread-count: 64
> performance.cache-ima-xattrs: on
> performance.cache-samba-metadata: on
> performance.md-cache-timeout: 600
> performance.cache-invalidation: on
> performance.stat-prefetch: on
> cluster.lookup-optimize: on
> server.event-threads: 32
> client.event-threads: 32
> performance.nl-cache-timeout: 600
> performance.nl-cache: on
> features.cache-invalidation-timeout: 600
> features.cache-invalidation: on
> network.ping-timeout: 10
> features.retention-mode: enterprise
> features.worm-file-level: on
> features.worm: off
> features.read-only: off
> user.smb: disable
> transport.address-family: inet
> nfs.disable: on
> performance.client-io-threads: off
> changelog.capture-del-path: on
> changelog.encoding: ascii
>
> Changelog settings:
> fs-davids-c2-n1:~ # gluster vo get repo2 all | grep changelog
> changelog.changelog on
> changelog.changelog-dir {{ brick.path }}/.glusterfs/changelogs
> changelog.encoding ascii
> changelog.rollover-time 36000
> changelog.fsync-interval5
> changelog.changelog-barrier-timeout 120
> changelog.capture-del-path on
>
>
>
>
> Community Meeting Calendar:
>
> Schedule -
> Every Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://bluejeans.com/441850968
>
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
Community Meeting Calendar:
Schedule -
Every Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] Trying out changelog xlator - human readable output?
Dear Gluster Community,
I trying out the changelog xlator to evaluate if it can be used as a kind
of audit log when accessing a volume via nfs. Here is the entry in the
CHANGELOG file when performing $ echo test >> file1.txt && chmod 444
file1.txt :
GlusterFS Changelog | version: v1.2 | encoding : 2
Ef845378a-f8d4-4dd2-a0fc-946e3d247f84234366553465534ac80f4db-3a41-42f6-b831-49cd9882a564/file1.txtDf845378a-f8d4-4dd2-a0fc-946e3d247f84Mf845378a-f8d4-4dd2-a0fc-946e3d247f8438
How one can make it human readable e.g. with full path information?
Regards
David Spisla
ps Below my volume info!
Here is my volume setting:
fs-davids-c2-n1:~ # gluster vo info repo2
Volume Name: repo2
Type: Replicate
Volume ID: 8b7b64d3-6019-4dac-b2cf-b78e78172724
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: fs-davids-c2-n1:/gluster/brick3/glusterbrick
Brick2: fs-davids-c2-n2:/gluster/brick3/glusterbrick
Brick3: fs-davids-c2-n3:/gluster/arbiter3/glusterbrick (arbiter)
Options Reconfigured:
changelog.changelog: on
changelog.rollover-time: 36000
features.scrub-freq: daily
features.scrub: Active
features.bitrot: on
cluster.quorum-type: auto
features.default-retention-period: 120
storage.ctime: on
features.utime: on
storage.build-pgfid: on
performance.write-behind: off
performance.write-behind-window-size: 4MB
performance.read-ahead: off
performance.cache-refresh-timeout: 10
performance.cache-size: 512MB
cluster.use-compound-fops: on
performance.io-thread-count: 64
performance.cache-ima-xattrs: on
performance.cache-samba-metadata: on
performance.md-cache-timeout: 600
performance.cache-invalidation: on
performance.stat-prefetch: on
cluster.lookup-optimize: on
server.event-threads: 32
client.event-threads: 32
performance.nl-cache-timeout: 600
performance.nl-cache: on
features.cache-invalidation-timeout: 600
features.cache-invalidation: on
network.ping-timeout: 10
features.retention-mode: enterprise
features.worm-file-level: on
features.worm: off
features.read-only: off
user.smb: disable
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off
changelog.capture-del-path: on
changelog.encoding: ascii
Changelog settings:
fs-davids-c2-n1:~ # gluster vo get repo2 all | grep changelog
changelog.changelog on
changelog.changelog-dir {{ brick.path
}}/.glusterfs/changelogs
changelog.encoding ascii
changelog.rollover-time 36000
changelog.fsync-interval5
changelog.changelog-barrier-timeout 120
changelog.capture-del-path on
Community Meeting Calendar:
Schedule -
Every Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users
