On Tue, Dec 8, 2009 at 6:36 PM, Jack Kielsmeier <jac...@netins.net> wrote: > Ah, good to know! I'm learning all kinds of stuff here :) > > The command (zpool import) is still running and I'm still seeing disk > activity. > > Any rough idea as to how long this command should last? Looks like each disk > is being read at a rate of 1.5-2 megabytes per second. > > Going worst case, assuming each disk is 1572864 megs (the 1.5TB disks are > actually smaller than this due to the 'rounding' drive manufacturers do) and > 2 megs/sec read rate per disk, that means hopefully at most I should have to > wait: > > 1572864(megs) / 2(megs/second) / 60 (seconds / minute) / 60 (minutes / hour) > / 24 (hour / day): > > 9.1 days > > Again, I don't know if the zpool import is looking at the entire contents of > the disks, or what exactly it's doing, but I'm hoping that would be the > 'maximum' I'd have to wait for this command to finish :) > -- > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >
I submitted a bug a while ago about this: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6855208 I'll escalate since I have a support contract. But yes, I see this as a serious bug, I thought my machine had locked up entirely as well, it took about 2 days to finish a destroy on a volume about 12TB in size. -- Brent Jones br...@servuhome.net _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
