Giovanni Tirloni wrote:
On Thu, Sep 2, 2010 at 10:18 AM, Jeff Bacon <ba...@walleyesoftware.com <mailto:ba...@walleyesoftware.com>> wrote:So, when you add a log device to a pool, it initiates a resilver. What is it actually doing, though? Isn't the slog a copy of the in-memory intent log? Wouldn't it just simply replicate the data that's in the other log, checked against what's in RAM? And presumably there isn't that much data in the slog so there isn't that much to check? Or is it just doing a generic resilver for the sake of argument because you changed something?Good question. Here it takes little over 1 hour to resilver a 32GB SSD in a mirror. I've always wondered what exactly it was doing since it was supposed to be 30 seconds worth of data. It also generates lots of checksum errors.
Here it takes more than 2 days to resilver a failed slog-SSD. I'd also expect it to finish in a few seconds... It seems it resilvers the whole pool, 35T worth of data on 22 spindels (RAID-Z2). We don't get any errors during resilver. -- Arne _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
