On 11/15/13, 12:24 AM, Paul B. Henson wrote: >> From: Saso Kiselkov [mailto:[email protected]] >> Sent: Wednesday, November 13, 2013 4:01 PM >> >> Has anybody had time to look over this webrev yet? I'm getting requests >> from people to get this upstreamed. > > Unfortunately reviewing this code is out of my depth :(, but you can count > me among the people that would love to see it upstream ;). I do finally have > my storage box running though, so if you happen to have a binary compatible > with the latest omnios stable and are still interested in people pounding on > it, I could do that.
Appreciate your offering to test the code out - here's the latest copy of both 32 and 64-bit zfs modules: http://37.153.99.61/zfs_l2arc_persist.tar.bz2 It should run fine on bloody (and perhaps even on stable, but I'm not super-confident in that). As per usual, test in a separate boot environment to make sure you won't hose your main install: # beadm create l2arc_persist # zfs set mountpoint=/tmp/l2arc_persist rpool/ROOT/l2arc_persist # zfs mount rpool/ROOT/l2arc_persist # wget -O - http://37.153.99.61/zfs_l2arc_persist.tar.bz2 | tar xjf - # cp zfs_l2arc_persist/obj32/zfs /tmp/l2arc_persist/kernel/fs/zfs # cp zfs_l2arc_persist/obj64/zfs /tmp/l2arc_persist/kernel/fs/amd64/zfs # bootadm update-archive -R /tmp/l2arc_persist # umount /tmp/l2arc_persist # reboot -fe l2arc_persist If you plan on capturing crash dumps with this new change running (and I'd appreciate it if you can), make sure your dump device is set to a physical partition or device, NOT a zvol, since a crash in the ZFS module precludes any dump to a zvol. That having been said, I don't expect any crashes (haven't had any myself). Cheers, -- Saso _______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
