Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am finding quite hard times in understanding ZFS. I was trying to learn it from Sun's documentation. But I am finding quite difficult from understanding it as it jumps directly from one place to other.
Do you have any other better sites in understanding ZFS ??
To be honest, I've learned ZFS as I've gone along. What is it that you're having difficulty understanding? The thing that gave me most trouble at first was the concept that it is both a filesystem, and a logical volume manager.
To be honest, I've learned ZFS as I've gone along. What is it that you're having difficulty understanding? The thing that gave me most trouble at first was the concept that it is both a filesystem, and diska logical volume manager.
Yes, the "mirror" in the zpool status output shows that the two disks are in a mirrored array, so the same data will be duplicated on each device. You can detach one side of the mirror, and continue to use volumes in the pool.
If you re-attach the device to the pool, it will re-silver automatically (re-mirror in ZFS speak). However, if you add it to the pool, the devices will be striped together, rather than mirrored.*
I found a reasonable looking tutorial, which may be of help. I also found a good article on the principles behind ZFS on Snoracle's BigAdmin site, though unfortunately it's quite out-of-date (pre-ZFS being bootable, for one thng).
* I made this mistake once, and In current versions of ZFS, you can't shrink a pool. The only solution was to send the data out to a file, then destroy and re-create the pool :-/.
No, you shouldn't need any command to force re-mirroring.
Code:
zpool attach [-f] pool device new_device
Attaches new_device to an existing zpool device. The existing device cannot be part of a raidz
configuration. If device is not currently part of a mirrored configuration, device automatically
transforms into a two-way mirror of device and new_device. If device is part of a two-way
mirror, attaching new_device creates a three-way mirror, and so on. In either case, new_device
begins to resilver immediately.
Did you try running zpool status after re-attaching the drive, and then again before detaching the other half? If you did, you should have seen a message informing you that the drive was being resilvered in the status line immediately after re-attaching. It would be wise to check before running zpool detach, though I'd be surprised if the utilities would allow you to detach a drive from a pool with inconsistencies.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.