Difference between revisions of "User talk:Andybill"
From Linux-VServer
(Site-to-site failover of VServers, and experiments with the ZFS filesystem.) |
|||
| Line 1: | Line 1: | ||
| − | + | Transfer of vservers over L2TP: effects of latency in transferring a vserver from one host to another, with block-replicated storage used for the /vservers area .... anyone tried this? Update: tested and working fine across a Fast Ethernet connection between two data centres. | |
| − | + | ZFS for storage of vservers is working up to a point; using zfs-fuse is fine for the /var/lib/vservers and /etc/vservers data, but any attempt to use apt fails. Seems to be due to a problem with apt mmap usage on FUSE, not ZFS specific. Horrible workaround is move vserver data back to the spare ext3, do the install/upgrade, then move it back to ZFS. Reason for having vservers on ZFS is that they are now snapshotted by ZFS each time they start successfully, so when experimenting with new builds / software, I don't have to do backups :-) | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 15:33, 1 August 2007
Transfer of vservers over L2TP: effects of latency in transferring a vserver from one host to another, with block-replicated storage used for the /vservers area .... anyone tried this? Update: tested and working fine across a Fast Ethernet connection between two data centres.
ZFS for storage of vservers is working up to a point; using zfs-fuse is fine for the /var/lib/vservers and /etc/vservers data, but any attempt to use apt fails. Seems to be due to a problem with apt mmap usage on FUSE, not ZFS specific. Horrible workaround is move vserver data back to the spare ext3, do the install/upgrade, then move it back to ZFS. Reason for having vservers on ZFS is that they are now snapshotted by ZFS each time they start successfully, so when experimenting with new builds / software, I don't have to do backups :-)
