Is libvirt capable of doing a live storage migration but keep the VM on the same host?
I have two NFS Network filesystem pools on one host. I would like to live migrate the underlying qcow2 disk files from one pool to the other.
I am unable to find any related documentation regarding live storage migration only. All examples and documentation seem to require a live VM migration at the same time.
When looking at several guides to setup VxLAN networks on Linux there seems to be 2 options:
When using OVS there is an option to use vxlan encap/decap hardware offloading:
$ sudo ovs-vsctl set ... other_config:hw-offload=true
Is there a method to use vxlan encap/decap hardware offloading when using native vxlan devices? If so, how can i enable/disable this hardware offloading and verify this?
Today i was playing around with ethernet adapters and vlans in Alpine Linux. I tried to give the interfaces arbitrary names.
After looking at the source i had the following example working
Ethernet adapter named lan01 configured as DHCP client and a VLAN on this adapter named lan-test on VLAN ID 100
My /etc/network/interfaces:
auto lo
iface lo inet loopback
auto lan01
iface lan01 inet dhcp
hostname alpine
auto lan-test
iface lan-test inet static
vlan-id 100
vlan-raw-device lan01
address 10.10.0.1
netmask 255.255.255.0
ifup and ifdown in Alpine Linux uses busybox.
Nowhere in any documentation i found the option vlan-id. However the vlan-raw-device is found in most documentation/man pages.
So this brings me to the question: Why is this option not documented anywhere?
Some of my guesses:
After i upgraded the firmware of my RAID controller i am experiencing issues with my Exchange server.
The Microsoft Exchange Transport Service stops almost immediatly after starting with the following error:
IP Filtering Database: An operation has encountered a fatal error. The database may be fragmented and manual offline defragmentation using ESEUTIL may be required. The Microsoft Exchange Transport service is shutting down. Exception details:
Microsoft.Exchange.Isam.IsamLogSectorSizeMismatchException: the log file sector size does not match the current volume's sector size (-546) at
Microsoft.Exchange.Isam.JetInterop.MJetInit(MJET_INSTANCE instance) at
Microsoft.Exchange.Isam.Interop.MJetInit(MJET_INSTANCE instance) at
Microsoft.Exchange.Transport.Storage.DataSource.InitInstance()
I tried cleaning all log files and remounting the mailbox database with no success.
We recently increased our user amount on our RDS 2012 R2. We are starting to experience some issues.
We have 4 Windows 2012 R2 RDS Servers and 1 Domain Controller/File server also running Windows Server 2012 R2.
Every RDS server has +- 10 users, At Max 15.
Every now and then when a users logs on the GPO fails to map the network drives. After logging off and login again it might be working again, the user just has to be 'lucky'. The event log shows the following event:
Event ID: 4098
The user 'Y:' preference item in the 'RDS2012 {AAFF7C11-7514-4CC3-BBC6-C00BBE718106}' Group Policy Object did not apply because it failed with error code '0x80070008 Not enough storage is available to process this command.' This error was suppressed.
We try to connect to the shares using the FQDN.
In a very few cases i had users trying to logon onto the RDS and receiving an error:
The remote procedure call failed and did not execute.
Waiting a few minutes and the user is able to logon just fine.
A third issue is when users are working in an Microsoft Office application they suddenly get a messagebox:
Disk is full or too many files are open
It looks like there is a perfomance issue. But after monitoring it, it seems fine.
RDS Servers:
Domain Controller/File server: - CPU usage is around 20-50% - RAM usage is at 70-80% 3.2GB/4GB
I have also checked for the amount of open handles in taskmgr and its a total of +- 150k handles. I think this shouldnt be a problem either?
Does anyone have an idea what might be causing these issues?
Edit:
The drive mappings are partially fixed with running them in the user context (configurable in GPO). Now the network drives are added. Sometimes they still are still marked with a red X in 'This PC' but double clicking it fixes the problem in 99% of the cases.
The Disk is full or too many files are open warning message still pops up in Office applications. This is comming from the Auto-save feature.
I ran a Process Monitor and looked at the moment the errors occurred and noticed 2 (strange?) things.
1. While doing a WriteFile on the pipe services on the domain controller/file server the return value is always INSUFFICIENT RESOURCES.
2. The network directory it's trying to read/write the auto-save file from/to has a double backslash in its name. Opening that exact path in windows explorer gives an error. After changing the double backslash to a single backslash i can open the directory just fine.
I checked the GPO redirections and auto-save location in the Office applications and none of these contain a double backslash.
I have a domain with 4 Remote Desktop Servers running Win2k8 R2.
If i change the GPO on my domain controller for the Remote Desktop Servers i am having some issues.
After running:
gpupdate /force
I get a successful response on all the servers.
On 2 of my Remote Desktop Servers the GPO updates are applied correctly. On 2 other Remote Desktop Servers the GPO updates are not applied correctly. The old settings still apply here.
gpresult /H result.html shows that last update date is from when i ran gpupdate /force and gives the new configures GPO on the last 2 terminals and the old GPO on the first 2 terminals.
I am unable to determine how and why those terminals fail to update to the correct GPO. How can i debug this?
How does zfs handle destroying snapshots during an incremental send?
Example:
2 servers using ZFS:
zfshost1
[root@zfshost1~]# zfs list -t snapshot
NAME
zones/40e66d56-4ea8-11e5-885d-feff819cdc9f@snapshot-1
zones/40e66d56-4ea8-11e5-885d-feff819cdc9f@snapshot-2
zones/40e66d56-4ea8-11e5-885d-feff819cdc9f@snapshot-3
zones/40e66d56-4ea8-11e5-885d-feff819cdc9f@snapshot-4
zfshost2
[root@zfshost2~]# zfs list -t snapshot
NAME
zones/40e66d56-4ea8-11e5-885d-feff819cdc9f@snapshot-1
Now incrementally send snapshot-2 to snapshot-4 to zfshost2
[root@zfshost2~]# nc -w 120 -l -p 1234 | zfs receive -F -d zones/40e66d56-4ea8-11e5-885d-feff819cdc9f
[root@zfshost1~]# zfs send -F -R -I zones/40e66d56-4ea8-11e5-885d-feff819cdc9f@snapshot-1 zones/40e66d56-4ea8-11e5-885d-feff819cdc9f@snapshot-4 | nc -w zfshost2 1234
(How) does ZFS handle if we delete, during the process of sending the snapshots, snapshot-1, snapshot-2, snapshot-3 or snapshot-4
[root@zfshost1~]# zfs destroy zones/40e66d56-4ea8-11e5-885d-feff819cdc9f@snapshot-X
With X = 1, 2, 3, 4
Does ZFS handle this situation? What is the expected result on zfshost2?