From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B87D9C43381 for ; Tue, 19 Mar 2019 06:03:56 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6C00C20989 for ; Tue, 19 Mar 2019 06:03:56 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6C00C20989 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=vt.edu Authentication-Results: mail.kernel.org; spf=fail smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.91) (envelope-from ) id 1h67qJ-0002TS-AD; Tue, 19 Mar 2019 02:03:19 -0400 Received: from omr2.cc.ipv6.vt.edu ([2607:b400:92:8400:0:33:fb76:806e] helo=omr2.cc.vt.edu) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1h67qH-0002TL-5a for kernelnewbies@kernelnewbies.org; Tue, 19 Mar 2019 02:03:17 -0400 Received: from mr5.cc.vt.edu (inbound.smtp.ipv6.vt.edu [IPv6:2607:b400:92:9:0:9d:8fcb:4116]) by omr2.cc.vt.edu (8.14.4/8.14.4) with ESMTP id x2J5WuGe013810 for ; Tue, 19 Mar 2019 01:32:56 -0400 Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) by mr5.cc.vt.edu (8.14.7/8.14.7) with ESMTP id x2J5WoOA028656 for ; Tue, 19 Mar 2019 01:32:55 -0400 Received: by mail-qk1-f197.google.com with SMTP id k21so16786192qkg.19 for ; Mon, 18 Mar 2019 22:32:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:date:message-id; bh=GbhecxK2h03DIrpPV0MrY1aTXa4e6SWQQ7/Ue4DCWEA=; b=B2/Zu/Fu/IXoiTSFbJxfVxdzTbEicU9X0qCoX0pkU9xRyw5DcVp6jzlsh+k3/wv2EH hDDxImlaI1uWwfrem3q3AcdIHfxfn3D+5OHy9N7XxAZ0jucJZUmvKPRYMD9dLEBsqFKC Ry8uh35ajjMU1dz/OBcMYNlWd10K5i7QeA3PtPcxim2z6r51oaKidSASk6/GsGl/Szob D9Bq0JPa5H2XlLhvq1PlK4skgd74EgGuyyVAMTS8wSsfI2lVTgiVXMHPQWcpjU7VwL23 6kZ7hReuJMHQy+F8otNCaVuRXAkZfGcv3AraTbFZGbiPMlzK6eRiDjI9KbHAQ5l4hJgO mvCg== X-Gm-Message-State: APjAAAW2Byfm6UiQv+X7deR05F+5WA4QzmstZ4um2ULj2pGKs2fyweoL iLRBPDDxj/WUmMe0PKduIOQeLfrvT6JTbR9AnSRbnK7Y93WNkksvb3WIIPoPnvGzfRE9Rrk73Ul +e5mEfJHfXC04le7it0pHTWA7lNmw+GzNufc6z3g= X-Received: by 2002:a37:5f85:: with SMTP id t127mr429164qkb.268.1552973570788; Mon, 18 Mar 2019 22:32:50 -0700 (PDT) X-Google-Smtp-Source: APXvYqxe9WAyF8HuvtGpEkE3Oh5WW9JeH/7mBOHJ+ik0n/8bRSB/FI2vjUwkve2qEA9bCp19oIkgqw== X-Received: by 2002:a37:5f85:: with SMTP id t127mr429153qkb.268.1552973570504; Mon, 18 Mar 2019 22:32:50 -0700 (PDT) Received: from turing-police ([2601:5c0:c001:4341::936]) by smtp.gmail.com with ESMTPSA id h196sm532965qke.32.2019.03.18.22.32.49 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 18 Mar 2019 22:32:49 -0700 (PDT) From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Google-Original-From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7+dev To: Jeno P Subject: Re: fsync slowness + XFS -- Regd. In-reply-to: References: Mime-Version: 1.0 Date: Tue, 19 Mar 2019 01:32:48 -0400 Message-ID: <17020.1552973568@turing-police> Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Tue, 19 Mar 2019 07:40:29 +0530, Jeno P said: > One of my module *(C/C++)* is writing to log files and periodically flushes > it using *fsync()*. Even for small amount of data, *fsync* is taking more > time *(>15 seconds)* than expected. Is it possible that some other process is applying a file lock to the log file? Any signs of I/O errors? 15 seconds is the sort of delay you might see on a RAID controller with one dead or partially dead disk throwing timeouts... _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies