erik.ableson wrote:
On 7 août 09, at 02:03, Stephen Green wrote:
Man, that looks so nice I think I'll change my mail client to do dates
in French :-)
Now my only question is: what do I do when it's done? If I reboot
and the ram disk disappears, will my tank be dead? Or will it just
continue without the slog? I realize that I'm probably totally boned
if the system crashes, so I'm copying off the stuff that I really care
about to another pool (the Mac's already been backed up to a USB drive.)
You have a number of options to preserve the current state of affairs
and be able to reboot the OpenSolaris server if required.
The absolute safest bet would be the following, but the resilvering will
take a while before you'll be able to shutdown:
create a file of the same size of the ramdisk on the rpool volume
replace the ramdisk slog with the 2G file (zpool replace <poolname>
/dev/ramdisk/slog /root/slogtemp)
wait for the resilver/replacement operation to run its course
reboot
create a new ramdisk (same size, as always)
replace the file slog with the newly created ramdisk
Would having an slog as a file on a different pool provide anywhere near
the same improvement that I saw by adding a ram disk? Would it affect
the typical performance (i.e., reading and writing files in my editor)
adversely?
That is, could I move the slog to a file and then just leave it there so
that I don't have trouble across reboots? I could then just use the
ramdisk when big things happened on the MacBook.
If your machine reboots unexpectedly things are a little dicier, but you
should still be able to get things back online. If you did a dump of
the ramdisk via dd to a file it should contain the correct signature and
be recognized by ZFS. Now there will be no guarantees to the state of
the data since if there was anything actively used on the ramdisk when
it stopped you'll lose data and I'm not sure how the pool will deal with
this. But in a pinch, you should be able to either replace the missing
ramdisk device with the dd file copy of the ramdisk (make a copy first,
just in case) or mount a new ramdisk, and dd the contents of the file
back to the device and then import the pool.
So, I take it if I just do a shutdown, the slog will be emptied
appropriately to the pool, but then at startup the slog device will be
missing and the system won't be able to import that pool.
If I dd the ramdisk to a file, I suppose that I should use a file on my
rpool, right?
Thanks for the advice, I think it might be time to convince the wife
that I need to buy an SSD. Anyone have recommendations for a reasonably
priced SSD for a home box?
Steve
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
