minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-28 19:42:10 +03:00
Code Activity

Updating fstab and minio.service path (#936)

Browse Source 
Updates fstab to add `nofail`.
Modifies path for `minio.service` to be in `/lib/` instead of `/etc/`.

Closes #874 .

Staged [here](
http://192.241.195.202:9000/staging/fstab874/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html#local-jbod-storage-with-sequential-mounts).

---------

Co-authored-by: Ravind Kumar <ravind@min.io>
This commit is contained in:
Daryl White
2023-08-14 14:10:26 -05:00
committed by GitHub
parent 6a3a85bc84
commit 79751411a4
4 changed files with 40 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
source/includes/common-installation.rst
View File

@ -195,6 +195,15 @@ For example:
LABEL=DISK3 /mnt/disk3 xfs defaults,noatime 0 2
LABEL=DISK4 /mnt/disk4 xfs defaults,noatime 0 2
.. note::
Cloud environment instances which depend on mounted external storage may encounter boot failure if one or more of the remote file mounts return errors or failure.
For example, an AWS ECS instances with mounted persistent EBS volumes may fail to boot with the standard ``/etc/fstab`` configuration if one or more EBS volumes fail to mount.
You can set the ``nofail`` option to silence error reporting at boot and allow the instance to boot with one or more mount issues.
You should not use this option on systems which have locally attached disks, as silencing drive errors prevents both MinIO and the OS from responding to those errors in a normal fashion.
You can then specify the entire range of drives using the expansion notation ``/mnt/disk{1...4}``.
If you want to use a specific subfolder on each drive, specify it as ``/mnt/disk{1...4}/minio``.
@ -256,6 +265,16 @@ MinIO **does not** support arbitrary migration of a drive with existing MinIO
data to a new mount position, whether intentional or as the result of OS-level
behavior.
.. note::
Cloud environment instances which depend on mounted external storage may encounter boot failure if one or more of the remote file mounts return errors or failure.
For example, an AWS ECS instances with mounted persistent EBS volumes may fail to boot with the standard ``/etc/fstab`` configuration if one or more EBS volumes fail to mount.
You can set the ``nofail`` option to silence error reporting at boot and allow the instance to boot with one or more mount issues.
You should not use this option on systems which have locally attached disks, as silencing drive errors prevents both MinIO and the OS from responding to those errors in a normal fashion.
.. end-local-jbod-desc
.. start-nondisruptive-upgrade-desc

13
source/includes/linux/common-installation.rst
View File

@ -207,11 +207,16 @@ operating systems using RPM, DEB, or binary:
.. start-install-minio-systemd-desc
The ``.deb`` or ``.rpm`` packages install the following
`systemd <https://www.freedesktop.org/wiki/Software/systemd/>`__ service file to
``/etc/systemd/system/minio.service``. For binary installations, create this
file manually on all MinIO hosts:
The ``.deb`` or ``.rpm`` packages install the following `systemd <https://www.freedesktop.org/wiki/Software/systemd/>`__ service file to ``/usr/lib/systemd/system/minio.service``.
For binary installations, create this file manually on all MinIO hosts.
.. note::
``systemd`` checks the ``/etc/systemd/...`` path before checking the ``/usr/lib/systemd/...`` path and uses the first file it finds.
To avoid conflicting or unexpected configuration options, check that the file only exists at the ``/usr/lib/systemd/system/minio.service`` path.
Refer to the `man page for systemd.unit <https://www.man7.org/linux/man-pages/man5/systemd.unit.5.html>`__ for details on the file path search order.
.. code-block:: shell
:class: copyable

11
source/operations/data-recovery/recover-after-drive-failure.rst
View File

@ -83,11 +83,20 @@ For example, consider
LABEL=DRIVE3 /mnt/drive3 xfs defaults,noatime 0 2
LABEL=DRIVE4 /mnt/drive4 xfs defaults,noatime 0 2
.. note::
Cloud environment instances which depend on mounted external storage may encounter boot failure if one or more of the remote file mounts return errors or failure.
For example, an AWS ECS instances with mounted persistent EBS volumes may fail to boot with the standard ``/etc/fstab`` configuration if one or more EBS volumes fail to mount.
You can set the ``nofail`` option to silence error reporting at boot and allow the instance to boot with one or more mount issues.
You should not use this option on systems which have locally attached disks, as silencing drive errors prevents both MinIO and the OS from responding to those errors in a normal fashion.
Given the previous example command, no changes are required to
``fstab`` since the replacement drive at ``/mnt/drive1`` uses the same
label ``DRIVE1`` as the failed drive.
4) Remount the Replaced Drive(s)
1) Remount the Replaced Drive(s)
--------------------------------
Use ``mount -a`` to remount the drives unmounted at the beginning of this

4
source/operations/install-deploy-manage/decommission-server-pool.rst
View File

@ -331,7 +331,7 @@ server in the deployment and remove the decommissioned pool.
The ``.deb`` or ``.rpm`` packages install a
`systemd <https://www.freedesktop.org/wiki/Software/systemd/>`__ service file to
``/etc/systemd/system/minio.service``. For binary installations, this
``/lib/systemd/system/minio.service``. For binary installations, this
procedure assumes the file was created manually as per the
:ref:`deploy-minio-distributed` procedure.
@ -521,7 +521,7 @@ For persistent failures, use :mc:`mc admin console` or review the ``systemd`` lo
Once decommissioning completes, you can safely remove the pools from the deployment configuration.
Modify the startup command for each remaining MinIO server in the deployment and remove the decommissioned pool.
The ``.deb`` or ``.rpm`` packages install a `systemd <https://www.freedesktop.org/wiki/Software/systemd/>`__ service file to ``/etc/systemd/system/minio.service``.
The ``.deb`` or ``.rpm`` packages install a `systemd <https://www.freedesktop.org/wiki/Software/systemd/>`__ service file to ``/lib/systemd/system/minio.service``.
For binary installations, this procedure assumes the file was created manually as per the :ref:`deploy-minio-distributed` procedure.
The ``minio.service`` file uses an environment file located at ``/etc/default/minio`` for sourcing configuration settings, including the startup.