michalczyk.pro/blog
1
0
Fork 0
Code Issues 3 Pull Requests Projects Releases Activity

Update RAID recovery instructions

Browse Source
This commit is contained in:
cryptogopher 2025-05-10 01:07:17 +02:00
parent 961b2205ac
commit 695a3ef687
1 changed files with 17 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
_posts/sysadm/2023-09-15-lvm-cheat-sheet.tl
View File

@ -34,7 +34,7 @@ If problems are found, this is denoted by @m@ on 9th bit of attributes displayed
by @lvs@: by @lvs@:
{% highlight bash %} {% highlight bash %}
$ cat /tmp/lvs # lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
backup vgdev rwi-aor-m- 4.00g 100.00 backup vgdev rwi-aor-m- 4.00g 100.00
{% endhighlight %} {% endhighlight %}
@ -58,7 +58,8 @@ bq. Integrity limitations
pvmove, snapshots, splitmirror, raid syncaction commands, raid rebuild. pvmove, snapshots, splitmirror, raid syncaction commands, raid rebuild.
That means commands like @lvchange --syncaction repair@ or @lvchange --rebuild@ That means commands like @lvchange --syncaction repair@ or @lvchange --rebuild@
won't work as expected. *should not be run* on RAID with integrity. They can give misleading results,
e.g. signal mismatch when there is none.
If RAID1 with integrity LV requires refresh (partial synchronization) due to If RAID1 with integrity LV requires refresh (partial synchronization) due to
e.g. device write errors, but both PVs are otherwise available, take the e.g. device write errors, but both PVs are otherwise available, take the
@ -82,7 +83,8 @@ so the process must be performed manually:
{% endhighlight %} {% endhighlight %}
* check integrity of both RAID1 parts: * check integrity of both RAID1 parts:
** whether they differ at all: ** whether they differ at all (this may be time consuming and it may be more
appropriate to proceed directly to file content comparison instead):
{% highlight bash %} {% highlight bash %}
# sha512sum /dev/vgdev/backup /dev/vgdev/backup_split # sha512sum /dev/vgdev/backup /dev/vgdev/backup_split
{% endhighlight %} {% endhighlight %}
@ -92,11 +94,19 @@ so the process must be performed manually:
# fsck.ext4 -n -f /dev/vgdev/backup_split # fsck.ext4 -n -f /dev/vgdev/backup_split
{% endhighlight %} {% endhighlight %}
** once filesystems are fixed and can be mounted, compare file content to ** once filesystems are fixed and can be mounted, compare file content to
determine which mirror is valid: determine which mirror is valid (no output from @rsync@ means no differences):
{% highlight bash %} {% highlight bash %}
# mount /dev/vgdev/backup /mnt/mirror1 # mount /dev/vgdev/backup /mnt/mirror1
# mount /dev/vgdev/backup_split /mnt/mirror1 # mount /dev/vgdev/backup_split /mnt/mirror2
# rsync -d /mnt/mirror1 /mnt/mirror2 # rsync -n -c -a --delete --progress /mnt/mirror1 /mnt/mirror2
{% endhighlight %} {% endhighlight %}
* finally remove invalid mirror, recreate RAID1 and re-add integrity layer * finally remove invalid mirror, recreate RAID1, re-add integrity layer and
discard unused space if necessary
h2. SSD related maintenance
h3. Discard unused space
* OWC does not support TRIM