glusterfs.git/doc, branch v4.1.0rc0

doc: GD2 release notes for 4.1.0

2018-05-31T16:10:13+00:00

Change-Id: Iaa32b252b84ccd95e78360130da3e8f6cbc2e7fb
updates: bz#1575386
Signed-off-by: Kaushal M

doc: Updated 4.1.0 release notes for smb.conf changes

2018-05-29T14:38:34+00:00

Updates: bz#1575386
Change-Id: I7a60b06bb57efdecbb5209ab4f98e858c8c39c77
Signed-off-by: ShyamsundarR

doc: Initial release notes for 4.1.0

2018-05-09T17:33:16+00:00

Change-Id: I934d05ff32431787086d4ec4ddb45abb131d44f6
Updates: bz#1575386
Signed-off-by: ShyamsundarR

posix: APIs in posix to get and set time attributes

2018-05-06T01:32:30+00:00

This is part of the effort to provide consistent time
across distribute and replica set for time attributes
(ctime, atime, mtime) of the object. This patch contains
the APIs to set and get the attributes from on disk
and in inode context.

Credits: Rafi KC 
Updates: #208
Change-Id: I5d3cba53eef90ac252cb8299c0da42ebab3bde9f
Signed-off-by: Kotresh HR

mount,fuse: make fuse dumping available as mount option

2018-05-04T17:42:12+00:00

Updates: bz#1193929
Change-Id: I4dd4d0e607f89650ebb74b893b911b554472826d
Signed-off-by: Csaba Henk

fuse: add support for kernel writeback cache

2018-05-04T17:42:12+00:00

- Added kernel-writeback-cache command line and xlator
  option for requesting utilisation of the writeback
  cache of the kernel in FUSE_INIT (see [1]).
- Added attr-times-granularity command line and xlator
  option via which granularity of the {a,m,c}time in
  stat (attr) data that we support can be indicated to
  kernel. This is a means to avoid divergence of the
  attr times between kernel and userspace that could
  occur with writeback-cache, while still maintaining
  maximum time precision the FUSE server is capable of
  (see [2]).
- Handling FATTR_CTIME flag in FUSE_SETATTR that
  indicates presence of ctime in setattr payload.
  Currently we cannot associate arbitrary ctimes to
  files on backend, so we just touch them to update
  their ctimes to current time. Having ctimes in setattr
  payload is also a side effect of writeback cache
  (see [3] and [4]).

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4d99ff8,
     "fuse: Turn writeback cache on"
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e27c9d3,
     "fuse: fuse: add time_gran to INIT_OUT"
[3]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1e18bda,
     "fuse: add .write_inode"
[4]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab9e13f,
     "fuse: allow ctime flushing to userspace"

Updates: #435
Change-Id: Id174c8e0c815c4456c35f8c53e41a6a507d91855
Signed-off-by: Csaba Henk

doc: updates Language Bindings for libgfapi-perl and gogfapi

2018-05-03T15:28:15+00:00

The libgfapi-perl provides declarations and linkage for the Gluster
gfapi C library with FFI for many Perl mongers

In addition, gogfapi URI link is replaced with GitHub because Forge is
dead.

Change-Id: I773e78beb201b48ca3fde0dc72d04b64dc9697d6
Signed-off-by: Ji-Hyeon Gim 
Updates: #447

doc: Update the admin guide link

2018-04-06T10:13:35+00:00

Update the existing admin guide link as it is incorrect.

Change-Id: I05669192623aeac287dfa9002caa0f390ea79499
Updates: bz#1193929
Signed-off-by: Varsha Rao

Fix gluster(8) formatting

2018-03-28T08:57:56+00:00

Looking at the man page show that "Snapshot command" wasn't aligned
with the other section titles.

Change-Id: I24bdb2e3728e03862fee57710cfe34b0607fe09a
BUG: 1507230
Signed-off-by: Michael Scherer

client: make fuse direct I/O strategies explicit

2018-03-22T04:27:11+00:00

So far the --direct-io-mode option has been presented
as of being Boolean valued. That is however not exact,
as a third behavior is chosen if the option is not
specified.

We accept now the "auto" value as an explicit choice
for the default heuristics, and indicate in the
descriptions of the option (which occur in commandline
help and in the gluterfs / mount.glusterfs man pages)
that auto is the default.

The default heuristics was briefly described in the
commandline help. We are getting rid of that, because:
- it's not the right place to provide such details;
- there is no guarantee of keeping the current heuristics
  so it might go out of sync with reality;
- that is already the case to some degree, because the
  description did not take into account that the default
  heuristics varies between platforms (on Mac, it's just
  "off"), and that xlators can also prescribe direct I/O
  for the file of their choice (see change
  I3fe3312cd96baa4eecfe1247ab7255b4f455f049).

Change-Id: Ia83479c0c67fe66b7fc2e0e8db5b7792d9f44b28
Signed-off-by: Csaba Henk