Tag Info

New answers tagged

1

It's always better to use redundant pools instead of non-redundant pools (though not always possible). The issue above is not likely to happen on a redundant pool. And it's faster to clone a snapshot (to get a file from it) than to recreate it somewhere (if you, of course, have no complaints about faulty hardware).


0

Here's my slightly generalized solution: sudo cp /tank2/test-text-file /tank1/test-text-file sudo zfs snapshot tank1@snapshot3 sudo sh -c 'zfs send -i tank1@snapshot2 tank1@snapshot3 | zfs receive -F tank2' sudo zfs rollback -r tank1@snapshot1 sudo sh -c 'zfs send -i tank2@snapshot1 tank2@snapshot3 | zfs receive -F tank1' sudo zpool scrub tank1; sudo zpool ...


0

After searching the internet and server fault and stack overflow for over a day, not finding anything. I ask this question, and the answer shows up in the related questions on the right side. So I found the answer to this on this question : Upgraded Ubuntu, all drives in one zpool marked unavailable For some reason, madam runs in the start, and starts ...


1

Just run a zpool clear solaris then post the result of zpool status -v. It would be nice to know the hardware involved and what controller you're using. edit Looking at your blkid output, you have remnants of a previous Linux software RAID. You'll need to mdadm --zero-superblock /dev/sdb1 to clear that.



Top 50 recent answers are included