New answers tagged

1

Intro First of all for anyone who is having the same issue on Ubuntu 16.04, it is currently an ongoing bug and as of now, to my knowledge, has not been fixed. You can visit the github conversation here to see the bug I am referencing. Secondly I am writing this post as an enthusiast and intermediate linux user, I am not a developer or currently work on ...


0

A quick search yields the following: On [Open]Solaris, this is handled by an event daemon. Autoreplace on/off just tells the daemon whether or not to do the replacement. On FreeBSD, the autoreplace setting doesn't do anything by default - you need to write a devd rule to handle triggering the actual replacement. I'm not sure what Linux does, but I'm sure ...


0

It is the same as with other vdev types. The FreeNAS documentation explains how it is done, see figure and table 8.1a for details. Note that only available disks will be shown and they limit the possible configurations, so make sure that all your disks are properly recognized. If it does not work this way, you could also create a striped pool out of two ...


1

Unfortunately, at this point you basically have two good options: Destroy and recreate the pool with the intended configuration, then restore your data from a restoration copy Get two more drives (minimum same size as each respective one you already have) and expand your pool to two mirrored pairs instead of two single disks The latter can be performed ...


6

Yes, this is possible. If you read a little on ZFS, you’ll find that it’s basically a pool of so-called “vdev”s. The simplest vdev would be a plain physical drive. It could also be a mirror consisting of two or more physical drives. This is what you want. You’d go for this structure: d1 d2 d3 d4 \ / \ / mirror mirror \ / ...


0

Unfortunately, destroying and recreating the pool would be your only option. If you just want to extract this specific single drive (for other reasons, like if it has lower performance than all other drives), you can attach a mirror drive to the vdev and then detach the old drive from the vdev, thereby "extracting" the drive while leaving the pool intact (...


1

I could then manually replace it with a copy from the 2,5" backup drive before the backup is polluted with the corrupted version. Unfortunately I have read that ZFS doesn't appear to notify the user when it detects corrupted files during an automatic checksum calculation/comparison. So my idea isn't possible. Actually, ZFS does (in a way) notify the user ...


1

I have a similar workflow. You should periodically scrub the external disk: zpool scrub poolname This will take several hours, depending on your pool size. You can check on status: zpool status poolname In your case where the pool has no redundancy, the scrubbing process will not be able to correct any bit errors but it will tell you which files are ...



Top 50 recent answers are included