This is a multi-part message in MIME format. ------=_NextPartTM-000-9dce819a-db00-4bb5-9dda-916b9ce8a5d2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Von: Yaniv Kaul [ykaul@redhat.com]=0A= Gesendet: Dienstag, 12. Januar 2016 13:15=0A= An: Markus Stockhausen=0A= Cc: users@ovirt.org; Mike Hildebrandt=0A= Betreff: Re: [ovirt-users] NFS IO timeout configuration=0A= =0A= On Tue, Jan 12, 2016 at 9:32 AM, Markus Stockhausen stockhausen@collogia= .de> wrote:=0A= Hi there,=0A= =0A= we got a nasty situation yesterday in our OVirt 3.5.6 environment.=0A= We ran a LSM that failed during the cleanup operation. To be precise=0A= when the process deleted an image on the source NFS storage.=0A= =0A= Can you share with us your NFS server details? =0A= Is the NFS connection healthy (can be seen with nfsstat)=0A= Generally, delete on NFS should be a pretty quick operation. =0A= Y.=0A= =0A= Hi Yaniv,=0A= =0A= we usually have no problems with our NFS server. From our observations we = =0A= only have issues when deleting files with many extents. This applies to all= =0A= OVirt images files. Several of them have more than 50.000 extents, a few = =0A= even more than 300.000.=0A= =0A= xfs_bmap 1cb5906f-65d8-4174-99b1-74f5b3cbc537=0A= ...=0A= 52976: [629122144..629130335]: 10986198592..10986206783=0A= 52977: [629130336..629130343]: 10986403456..10986403463=0A= 52978: [629130344..629138535]: 10986206792..10986214983=0A= 52979: [629138536..629138543]: 10986411656..10986411663=0A= 52980: [629138544..629145471]: 10986214992..10986221919=0A= 52981: [629145472..629145575]: 10809903560..10809903663=0A= 52982: [629145576..629145599]: 10737615056..10737615079=0A= =0A= Our XFS is mounted with:=0A= =0A= /dev/mapper/vg00-lvdata on /var/nas4 type xfs (rw,noatime,nodiratime,allocs= ize=3D16m)=0A= =0A= Why we use allocsize=3D16M? We once started with allocize=3D512MB. This=0A= led to sparse files that did not save much bytes. Because a single byte wri= tten=0A= resulted in a 512MB allocation. Thin allocation of these files resulted in = long runtimes=0A= for formatting disks inside the VMS. So we reduced to 16MB as a balanced co= nfig=0A= =0A= This works quite well but not for remove operations.=0A= =0A= Better ideas?=0A= =0A= Markus=0A= =0A= =0A= =0A= ------=_NextPartTM-000-9dce819a-db00-4bb5-9dda-916b9ce8a5d2 Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt"
**************************************************************************** Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Über das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 **************************************************************************** ------=_NextPartTM-000-9dce819a-db00-4bb5-9dda-916b9ce8a5d2--