Bart Smaalders wrote:
Torrey McMahon wrote:
eric kustarz wrote:
I want per pool, per dataset, and per file - where all are done by
the filesystem (ZFS), not the application. I was talking about a
further enhancement to "copies" than what Matt is currently
proposing - per file "copies", but its more work (one thing being we
don't have administrative control over files per se).
Now if you could do that and make it something that can be set at
install time it would get a lot more interesting. When you install
Solaris to that single laptop drive you can select files or even
directories that have more then one copy in case of a problem down
the road.
Actually, this is a perfect use case for setting the copies=2
property after installation. The original binaries are
quite replaceable; the customizations and personal files
created later on are not.
We've been talking about user data but the chance of corrupting
something on disk and then detecting a bad checksum on something in
/kernel is also possible. (Disk drives do weird things from time to
time.) If I was sufficiently paranoid I would want everything required
to get into single-user mode, some other stuff, and then my user data,
duplicated to avoid any issues.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
