Hi, I''m running snv_134 on 64-bit x86 motherboard, with 2 SATA drives. The zpool "rpool" uses whole disk of each drive. I''ve installed grub on both discs, and mirroring seems to be working great. I just started testing what happens when a drive fails. I kicked off some activities and unplugged one of the drives while it was running, the system kept running, and zpool status indicated that one drive was removed. Awesome. I plugged it back in, and it recovered perfectly. But with one of the drives unplugged, the system hangs at boot. On both drives (with the other unplugged) grub loads, and the system starts to boot. However, it gets stuck at the "Hostname: Vault" line and never gets to "reading ZFS config" like it would on a normal boot. If I reconnect both drives then booting continues correctly. If I detach a drive from the pool, then the system also correctly boots off a single connected drive. However, reattaching the 2nd drive causes a whole resilver to occur. Is this a bug? Or is there some other thing you need to do to mark the drive as offline or something. Shame that you have to do that before rebooting! Would make it very hard to recover if the drive was physically dead.... Thanks, Matt -- This message posted from opensolaris.org
On Sat, May 29, 2010 at 12:54 AM, Matt Connolly <matt.connolly.au at gmail.com> wrote:> But with one of the drives unplugged, the system hangs at boot. On both drives (with the other unplugged) grub loads, and the system starts to boot. However, it gets stuck at the "Hostname: Vault" line and never gets to "reading ZFS config" like it would on a normal boot.It''s a known bug in b134. -B -- Brandon High : bhigh at freaks.com
On 5/29/10 12:54 AM -0700 Matt Connolly wrote:> I''m running snv_134 on 64-bit x86 motherboard, with 2 SATA drives. The > zpool "rpool" uses whole disk of each drive.Can''t be. zfs can''t boot from a whole disk pool on x86 (maybe sparc too). You have a single solaris partition with the root pool on it. I am only being pedantic because "whole disk" has a special meaning to zfs, distinct from "a single partition using the entire disk". ...> If I detach a drive from the pool, then the system also correctly boots > off a single connected drive. However, reattaching the 2nd drive causes a > whole resilver to occur.By "detach" do you mean running "zpool detach", or simply removing the drive physically without running any command? I suppose the former because if you just remove it I''d think you''d have the same non-booting problem. If that''s right, then that is the expected behavior. "zpool detach" causes zfs to forget everything it knows about the device being detached. -frank