summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKai Lüke <kailueke@riseup.net>2017-08-17 23:31:32 +0200
committerPetr Kovar <pkovar@redhat.com>2017-09-12 09:40:10 +0200
commit70e287118048538537d77c26c6ae472dab8f2b1b (patch)
tree82d0dd2d17e9ac4fb1fc4ab2f038513dd52984ca
parent7d388801bbd6e0533149f78fa494b3269f5a41f2 (diff)
downloadgnome-user-docs-70e287118048538537d77c26c6ae472dab8f2b1b.tar.gz
Bug 786446 - Document filesystem resize and repair
-rw-r--r--gnome-help/C/disk-repair.page109
-rw-r--r--gnome-help/C/disk-resize.page73
-rw-r--r--gnome-help/Makefile.am2
3 files changed, 184 insertions, 0 deletions
diff --git a/gnome-help/C/disk-repair.page b/gnome-help/C/disk-repair.page
new file mode 100644
index 00000000..f84392a9
--- /dev/null
+++ b/gnome-help/C/disk-repair.page
@@ -0,0 +1,109 @@
+<page xmlns="http://projectmallard.org/1.0/"
+ type="topic" style="task"
+ id="disk-repair">
+ <info>
+ <link type="guide" xref="disk"/>
+
+
+ <credit type="author">
+ <name>GNOME Documentation Project</name>
+ <email>gnome-doc-list@gnome.org</email>
+ </credit>
+
+ <revision pkgversion="3.25.90" date="2017-08-17" status="review"/>
+
+ <desc>Check if a filesystem is damaged and bring it back into a usable
+ state.</desc>
+ <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
+ </info>
+
+<title>Repair a damaged filesystem</title>
+
+ <p>Filesystems can be corrupted due to unexpected power loss, system crashes
+ and unsafe removal of the drive.
+ After such an incident it is recommended to <em>repair</em> or at least
+ <em>check</em> the filesystem to prevent future data loss.</p>
+ <p>Sometimes a repair is required in order to mount or modify a filesystem.
+ Even if a <em>check</em> does not report any damage the filesystem might
+ still be marked as 'dirty' internally and require a repair.</p>
+
+<steps>
+ <title>Check if a filesystem is damaged</title>
+ <item>
+ <p>Open <app>Disks</app> from the <gui>Activities</gui> overview.</p>
+ </item>
+ <item>
+ <p>Select the disk containing the filesystem in question from the list of
+ storage devices on the left. If there is more than one volume on the
+ disk, select the volume which contains the filesystem.</p>
+ </item>
+ <item>
+ <p>In the toolbar underneath the <gui>Volumes</gui> section, click the
+ menu button. Then click <gui>Check Filesystem…</gui>.</p>
+ </item>
+ <item>
+ <p>Depending on how much data is stored in the filesystem a check may take
+ longer time. Confirm to start the action in the dialog that pops up.</p>
+ <p>The action will not modify the filesystem but will unmount it if needed.
+ Be patient while the filesystem is checked.</p>
+ </item>
+ <item>
+ <p>After completion you will be notified whether the filesystem is damaged.
+ Note that in some cases even if the filesystem is undamaged it still
+ may need to be repaired to reset an internal 'dirty' marker.</p>
+ </item>
+</steps>
+
+<note style="warning">
+ <title>Possible data loss when repairing</title>
+ <p>If the filesystem structure is damaged it can affect the files stored
+ in it. In some cases these files can not be brought into a valid form
+ again and will be deleted or moved to a special directory. It is normally
+ the <em>lost+found</em> folder in the top level directoy of the filesystem
+ where these recovered file parts can be found.</p>
+ <p>If the data is too valuable to be lost during this process, you are
+ advised to back it up by saving an image of the volume before
+ repairing.</p>
+ <p>This image can be then processed with forensic analysis tools like
+ <app>sleuthkit</app> to further recover missing files and data parts
+ which were not restored during the repair, and also previously removed
+ files.</p>
+</note>
+
+<steps>
+ <title>Repair a filesystem</title>
+ <item>
+ <p>Open <app>Disks</app> from the <gui>Activities</gui> overview.</p>
+ </item>
+ <item>
+ <p>Select the disk containing the filesystem in question from the list
+ of storage devices on the left. If there is more than one volume on
+ the disk, select the volume which contains the filesystem.</p>
+ </item>
+ <item>
+ <p>In the toolbar underneath the <gui>Volumes</gui> section, click the
+ menu button. Then click <gui>Repair Filesystem…</gui>.</p>
+ </item>
+ <item>
+ <p>Depending on how much data is stored in the filesystem a repair may take
+ longer time. Confirm to start the action in the dialog that pops up.</p>
+ <p>The action will unmount the filesystem if needed. The repair action tries
+ to bring the filesystem into a consistent state and moves files which were
+ damaged in a special folder. Be patient while the filesystem is
+ repaired.</p>
+ </item>
+ <item>
+ <p>After completion you will be notified whether the filesystem could be
+ successfully repaired. In case of success it can be used again in the
+ normal way.</p>
+ <p>If the filesystem could not be repaired, back it up by saving an image
+ of the volume to be able to retrieve important files later. This can
+ be done by mounting the image read-only or using forensic analysis tools
+ like <app>sleuthkit</app>.</p>
+ <p>To make use of the volume again it has to be
+ <link xref="disk-format">formatted</link> with a new filesystem. All
+ data will be discarded.</p>
+ </item>
+</steps>
+
+</page>
diff --git a/gnome-help/C/disk-resize.page b/gnome-help/C/disk-resize.page
new file mode 100644
index 00000000..225fe1cd
--- /dev/null
+++ b/gnome-help/C/disk-resize.page
@@ -0,0 +1,73 @@
+<page xmlns="http://projectmallard.org/1.0/"
+ type="topic" style="task"
+ id="disk-resize">
+ <info>
+ <link type="guide" xref="disk"/>
+
+
+ <credit type="author">
+ <name>GNOME Documentation Project</name>
+ <email>gnome-doc-list@gnome.org</email>
+ </credit>
+
+ <revision pkgversion="3.25.90" date="2017-08-17" status="review"/>
+
+ <desc>Shrink or grow a filesystem and its partition.</desc>
+ <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
+ </info>
+
+<title>Adjust the size of a filesystem</title>
+
+ <p>A filesystem can be grown to make use of the free space after its
+ partition. Often this is even possible while the filesystem is
+ mounted.</p>
+ <p>To make space for another partition after the filesystem, it can be
+ shrunk according to the free space within it.</p>
+ <p>Not all filesystems have resize support.</p>
+ <p>The partition size will be changed together with the filesystem size.
+ It is also possible to resize a partition without a filesystem in the
+ same way.</p>
+
+<steps>
+ <title>Resize a filesystem/partition</title>
+ <item>
+ <p>Open <app>Disks</app> from the <gui>Activities</gui> overview.</p>
+ </item>
+ <item>
+ <p>Select the disk containing the filesystem in question from the list
+ of storage devices on the left. If there is more than one volume on
+ the disk, select the volume which contains the filesystem.</p>
+ </item>
+ <item>
+ <p>In the toolbar underneath the <gui>Volumes</gui> section, click the
+ menu button. Then click <gui>Resize Filesystem…</gui> or
+ <gui>Resize…</gui> if there is no filesystem.</p>
+ </item>
+ <item>
+ <p>A dialog will open where the new size can be chosen. The filesystem will
+ be mounted to calculate the minimum size by the amount of current
+ content. If shrinking is not supported the minimum size is the current
+ size. Leave enough space within the filesystem when shrinking to ensure
+ that it can work fast and reliably.</p>
+ <p>Depending on how much data has to be moved from the shrunk part, the
+ filesystem resize may take longer time.</p>
+ <note style="warning">
+ <p>The filesystem resize automatically involves
+ <link xref="disk-repair">repairing</link> of the filesystem. Therefore
+ it is advised to back up important data before starting. The action
+ must not be stopped or it will result in a damaged filesystem.</p>
+ </note>
+ </item>
+ <item>
+ <p>Confirm to start the action by clicking
+ <gui style="button">Resize</gui>.</p>
+ <p>The action will unmount the filesystem if resizing a mounted filesystem
+ is not supported. Be patient while the filesystem is resized.</p>
+ </item>
+ <item>
+ <p>After completion of the needed resize and repair actions the filesystem
+ is ready to be used again.</p>
+ </item>
+</steps>
+
+</page>
diff --git a/gnome-help/Makefile.am b/gnome-help/Makefile.am
index f4a7b691..fbd03fc7 100644
--- a/gnome-help/Makefile.am
+++ b/gnome-help/Makefile.am
@@ -191,6 +191,8 @@ HELP_FILES = \
disk-check.page \
disk-format.page \
disk-partitions.page \
+ disk-repair.page \
+ disk-resize.page \
disk.page \
display-blank.page \
display-brightness.page \