refactor(admin): refine data directory write-up in troubleshooting chapter #14107
Merged
refactor(admin): refine data directory write-up in troubleshooting chapter #14107
Conversation
joshtrichards
added
3. to review
manual: admin
feature: configuration
Member
Author
|
/backport to stable33 |
joshtrichards
changed the title
This comment was marked as resolved.
This comment was marked as resolved.
joshtrichards
changed the title
…ng chapter Signed-off-by: Josh Richards <josh.t.richards@gmail.com>
Signed-off-by: Josh Richards <josh.t.richards@gmail.com>
skjnldsv
force-pushed
the
jtr/refactor-troubleshooting-datadir-move
branch
from
2ae7b06 to
3acc1bc
Compare
skjnldsv
approved these changes
Apr 26, 2026
miaulalala
reviewed
Apr 26, 2026
|
|
||
| 1. Make sure no cron jobs are running and, if using system cron, that the Nextcloud crontab entry is disabled. | ||
|
|
||
| 2. Stop web/app server(s). |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. Stop web/app server(s). | |
| 2. Stop the web / app server(s). |
|
|
||
| 2. Stop web/app server(s). | ||
|
|
||
| 3. Move ``/data`` to the new location (ensure you also move hidden/dot files such as ``.ncdata``). |
Contributor
There was a problem hiding this comment.
Suggested change
| 3. Move ``/data`` to the new location (ensure you also move hidden/dot files such as ``.ncdata``). | |
| 3. Move the entire ``/data`` firectory to the new location. Ensure you also move hidden/dot files such as ``.ncdata``. |
|
|
||
| 3. Move ``/data`` to the new location (ensure you also move hidden/dot files such as ``.ncdata``). | ||
|
|
||
| 4. Create a symlink from the original location to the new location. |
Contributor
There was a problem hiding this comment.
original location of /data to new location of /data?
|
|
||
| 4. Create a symlink from the original location to the new location. | ||
|
|
||
| 5. Ensure permissions are still correct (including for any parent folders). |
Contributor
There was a problem hiding this comment.
Suggested change
| 5. Ensure permissions are still correct (including for any parent folders). | |
| 5. Ensure the folder permissions are still correct, including parent folders. |
Maybe also mention which permissions or add a link to the relevant section
|
|
||
| 5. Ensure permissions are still correct (including for any parent folders). | ||
|
|
||
| 6. Restart web/app server(s). |
Contributor
There was a problem hiding this comment.
Suggested change
| 6. Restart web/app server(s). | |
| 6. Restart the web / app server(s). |
Comment on lines
+432
to
+434
| This method is not supported and you risk breaking your database. Always make sure you | ||
| have up-to-date backups -- including your database -- and a working (tested) restore | ||
| process **before** attempting this. |
Contributor
There was a problem hiding this comment.
Move this on top so it's before the unsupported datadir migration method instructions?
|
|
||
| .. warning:: | ||
| However this is not supported and you risk breaking your database. | ||
| For safely moving the data directory, the recommended actions are: |
Contributor
There was a problem hiding this comment.
Suggested change
| For safely moving the data directory, the recommended actions are: | |
| For safely moving the data directory, the recommended steps are: |
| However this is not supported and you risk breaking your database. | ||
| For safely moving the data directory, the recommended actions are: | ||
|
|
||
| 1. Make sure no cron jobs are running and, if using system cron, that the Nextcloud crontab entry is disabled. |
Contributor
There was a problem hiding this comment.
Suggested change
| 1. Make sure no cron jobs are running and, if using system cron, that the Nextcloud crontab entry is disabled. | |
| 0. Create a backup of your system - files and database - and test your recovery process. | |
| 1. Make sure no cron jobs are running and, if using system cron, that the Nextcloud crontab entry is disabled. |
Contributor
|
too fast @skjnldsv 🐎 |
Member
Follow-up? |
Contributor
|
@joshtrichards could you check my comments in a follow up if you don't mind? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
☑️ Resolves
🖼️ Screenshots