Hello Al, Thursday, January 25, 2007, 6:52:58 PM, you wrote:
AH> On Thu, 25 Jan 2007, Darren J Moffat wrote: >> Tim Cook wrote: >> > I guess I should clarify what I'm doing. >> > >> > Essentially I'd like to have the / and swap on the first 60GB of the >> > disk. Then use the remaining 100GB as a zfs partition to setup zones >> > on. Obviously the snapshots are extremely useful in such a setup :) >> > >> > Does my plan sound feasible from both a usability and performance >> > standpoint? AH> For a laptop scenario, where you don't have any option to add a 2nd drive, AH> I agree with Darren and others. But in any other usage scenario, I don't AH> think its a good idea. Perhaps you could post some details about your AH> hardware environment and why its limited to a single disk drive? AH> You understand that if ZFS detects any data corruption and you don't have AH> any designed-in data redundancy, ZFS will make the pool unavailable and AH> you are SOL. It's not true. Metadata will still be in 2 and 3 copies (2 for fs metadata and 3 for pool metadata) spread on disks with checksums. So when he will enocunter any problems to only part of a disk he should be ok when it comes to pool/fs consistency and only user data will be affected. However he should be able to determine which files are affected (with zpool status) and just delete them. Few days ago a fix was integrated so zpool status should show actual file names instead of just inode. -- Best regards, Robert mailto:[EMAIL PROTECTED] http://milek.blogspot.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
