In our case we are talking about the C drive specifically which as to be bound at boot, but we have experimented with local ISCSI alternates which did not work all the time due to a number of windows related issues. We have not looked in alternate methods, since we thought that directly using the kvm way should provide the most stable and reliable boot procedure.
From: Gjermund ॐ Gusland Thorsen Sent: Wednesday, January 18, 2017 09:19 To: [email protected] Subject: Re: [smartos-discuss] 'Defrag' a KVM disk Did you consider to make the file pool of the KVM a native ZFS file pool? CIFS or other Sent from my iPhone On 18 Jan 2017, at 08:31, Matthias Goetzke <[email protected]> wrote: We have a machine which temporarily got 98% full and the boot time of a KVM windows server has gotten quite extreme (minutes on the black part of the boot alone). Apart from over-allocating, we guess it might have to do with fragmentation of the underlying C drive (just a hunch due to the number of writes on C and the fact that overall fragmentation was temporarily >78%) since another win machine still booted up quite quickly. If a kvm disk were just a file then I could just make a copy of the C drive (I have enough space now) into a new file which should (in theory) just create new aligned blocks and once I delete the old file it should be defragmented mostly. Is this correct ? And if so, kvm disks are mounted as raw devices, so I guess my idea wont work anyway. Is there an alternative or is this a fools errant ? Cheers, matthias smartos-discuss | Archives | Modify Your Subscription ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
