香港版的 Creative Commons 正式推出,大家可以上去弄新的 HTML code 了:
1. 首先到 https://hk.creativecommons.org ,然後點「授權」
2. 然後選擇條款,可加入附加資料,然後到下一步
One of the attractions of ZFS pools is that they are prettyself-documenting. A ZFS pool automatically captures a great deal of thebasic information that you need to deal with it, such as the filesystemsit contains and NFS export settings. But this isn't quite all of theinformation that you need for long term management and for disasterrecovery, and in our new fileserver environment we've opted to duplicate some of the information outside of ZFS as well.
(Keeping track of filesystems, export permissions,
香港版的 Creative Commons 正式推出,大家可以上去弄新的 HTML code 了:
1. 首先到 https://hk.creativecommons.org ,然後點「授權」
2. 然後選擇條款,可加入附加資料,然後到下一步
Our old SAN was set up in the traditional way: the SAN backend units didRAID-5 interally, and this RAID-5 space was carved up into LUNs and usedby the frontend fileservers. For natural reasons all of our fileservers wound up using LUNs from all of our SAN backends.This setup has low overhead , decent resilience,and decent performance.Our new fileservers are set up inan entirely different way, and among other things they use RAID-1instead of RAID-5. Although we were
Our new fileserver setup requiresthat all of the LUNs exported by the backend SAN be exactly the samesize, down to the block, so that we can always mirror two arbitrary LUNstogether. We wanted our basic LUN size to be around 200 to 250 GB, butthat's a large range of possible sizes, and it still left us to pick asensible exact block size.
Our first approach was to take our 750 GB Seagate SATA disks and dividethem up into three equal