| 1 |
On Wed, Jun 25, 2014 at 2:44 PM, Douglas J Hunley <doug.hunley@×××××.com> wrote: |
| 2 |
> |
| 3 |
> You're going to want to cron a 'scrub' and have it email you. There's no |
| 4 |
> background daemon that I'm aware of to handle this. ZFS just introduced |
| 5 |
> 'zed' and it would be nice if BTRFS would do the same |
| 6 |
|
| 7 |
Actually, I think that for serious failures smartd will take care of it. |
| 8 |
|
| 9 |
I was reading the btrfs list archives and apparently btrfs doesn't |
| 10 |
make as much as a whisper when a drive fails. It just keeps on going. |
| 11 |
|
| 12 |
Now, the keeps on going part I'm fine with, but you'd think that |
| 13 |
operating in a degraded mode would trigger some kind of message. |
| 14 |
|
| 15 |
Granted, it isn't 100% done yet, either. In fact, if your replace the |
| 16 |
failed drive you have to manually force a re-balance or it will just |
| 17 |
continue to operate degraded. |
| 18 |
|
| 19 |
Rich |
Archives