User Tools

Site Tools


zfs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
zfs [2015/08/21 13:49]
127.0.0.1 external edit
zfs [2020/02/13 22:55] (current)
Line 1: Line 1:
  
-<h1><var name="TITLE"/></h1><p>Using ZFS on Linux (Ubuntu 14.04 LTS).</p> +====== Using ZFS on Linux (Ubuntu 14.04 LTS) ====== 
-<h1>Zpool Import</h1><p>Because I am using a partition (sdX3) of the disks, and ZFS assumes you are using the whole disk (when it searches /dev by default), it was necessary to symlink the partition names to a new directory and zpool import referencing devices in that new directory.</p>+ 
 +===== Zpool Import ===== 
 + 
 +Because I am using a partition (sdX3) of the disks, and ZFS assumes you are using the whole disk (when it searches /dev by default), it was necessary to symlink the partition names to a new directory and zpool import referencing devices in that new directory. 
 <code> <code>
 # cd /etc/zfs # cd /etc/zfs
Line 7: Line 11:
 # zfs import -d /etc/zfs -a # zfs import -d /etc/zfs -a
 </code> </code>
-<h1>Disk Replacement</h1><p>When using /dev/disk/by-id, I was unable to replace a failed disk with a new working disk when using human readable device paths (by-id).</p><p>I had to grab the numeric disk guid using the zdb command, and then use that ID in the zpool replace command.</p><p>Here disk S/N Z1E2EEN3 died, and was replaced with disk S/N Z1E77EXB.</p>+ 
 +===== Disk Replacement ===== 
 + 
 +When using /dev/disk/by-id, I was unable to replace a failed disk with a new working disk when using human readable device paths (by-id). 
 + 
 +I had to grab the numeric disk guid using the zdb command, and then use that ID in the zpool replace command. 
 + 
 +Here disk S/N Z1E2EEN3 died, and was replaced with disk S/N Z1E77EXB. 
 <code> <code>
 # zdb | grep -B1 Z1E2EEN3 # zdb | grep -B1 Z1E2EEN3
zfs.1440179375.txt.gz · Last modified: 2020/02/13 22:55 (external edit)

free spam filter