Tag Info

Hot answers tagged

3

This is the problem with raidz1 (and also RAID5). If the data on the disk changes but no drive fault occurs to let ZFS or the RAID controller know which drive caused the error, then it can't know which drive is correct. With raidz2 (and higher) or RAID6, you get a quorum of drives that can decide which drive to ignore for reconstruction. Your only solution ...


3

Filesystems with a % character in them are shares of some sort. You can see the share properties for all shared filesystems with zfs get share.all This is documented in the man page for zfs_share: "A file system's automatic share name displays as filesystem%. For example, tank/home%." That style of documenting something is typical of Sun/Solaris. ...


2

I have a similar configuration with an AD joined server sharing from zfs, and have experienced the 'sleep' issue in FreeBSD 10.1 and 11.0, and several versions of Samba 3 and 4. I began to notice the lockup would occur mainly on changes to existing files, and not creation or deletion. After running very high samba debug levels, and catching a couple of ...


1

I figured it out. Use zdb on the pool to get the GUID of the original disk, then use format to find the name of the replacement disk, then do # zpool replace <pool> <GUID of original disk> <name of replacement disk> It looks like this while resilvering: NAME STATE READ WRITE CKSUM raid ...



Only top voted, non community-wiki answers of a minimum length are eligible