On Wed, May 20, 2009 at 12:06:49AM +0300, Ahmed Kamal wrote: > Is anyone even using ZFS under Xen in production in some form. If so, > what's > your impression of reliability ?
Hmm, somebody needs to out itself. Short answer: yes. Details: Well, i've installed an IntelServer (2x QuadCore E5440, 2.8 GHz) with 4x 300GB-SATA (2x 2-way mirrors) in a small company (one of the ebay rated Top10 sellers in germany) in October 2008 running snv_b98 as dom0 ;-) domU1 is a win2003 32bit small business server running a MS SQL server, domU2 is a win2008 32bit standard server, which is used as terminal server (<=10 users) basically to run several Sage[.de] products. Both domUs are using the latest PV driver, which - depending on the recordsize to write - reaches about the same xfer rates as in dom0. (see http://iws.cs.uni-magdeburg.de/~elkner/xVM/ for more info: the "benchmarks" were made on a X4600M, however the IntelServer produces about the same numbers). pool1/win2003sbs.dsk volsize 48G - pool1/win2003sbs.dsk volblocksize 8K - pool1/win2008ss.dsk volsize 24G - pool1/win2008ss.dsk volblocksize 8K - It is in production since ~ february 2009 and stable as expected: Sometimes, when the win2003 domU is too long idle, it doesn't wake up anymore. No problem, wrote a simple CGI-script, so that the users have a simple UI to check the state of the domUs (basically a ping), to pull the cable (virsh destroy) as well as start/suspend/resume them. Usually they use this bookmark ~ 2-3/week when they start working. Users are quite happy with it, since clicking on a link is not much more work than switching on their own PC - so not annoying/painful at all. Initially I gave win2003 2x16 GB partitions (C:, D: for SQL Data), winn2008 a single 16 GB partition. When the sage products were installed, it turned out, that the 16GB was almost filled, so the volsize of pool1/win2008ss.dsk was increased to 24GB and the C: partition dynam. extendend in Win2008 - no problem. Last month the SQL Server has filled up its D: partition (16GB). So it started to 'reboot' several times a day. However, rising the pool1/win2003sbs.dsk volsize to 48 GB (i.e. D: to 32GB) solved that problem. The only little hurdle here was, that on could not extend the partition per win partitionmanager's context menu: one had to use the command line tool ... Things, which are a little bit annoying is the ZFS send command. Takes pretty long, but since it is usually running at night, it is not a real problem. BTW: The server was installed from remote "misusing" a company internal linux server (jumpstart of course). Since seriell port was not connected, I had to ask an on-site user to initiate the PXE boot, but this was not a problem, too. So the summary: all people (incl. admins) are happy. However, if you need to decide, whether to use Xen, test your setup before going into production and ask your boss, whether he can live with innovative ... solutions ;-) Regards, jel. -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768 _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
