From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailgw-02.dd24.net ([193.46.215.43]:47009 "EHLO mailgw-02.dd24.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727386AbeIDQKp (ORCPT ); Tue, 4 Sep 2018 12:10:45 -0400 Message-ID: <6814364da02fd7e71e31c25d7928b2dfab7b133a.camel@scientia.net> Subject: Re: fsck lowmem mode only: ERROR: errors found in fs roots From: Christoph Anton Mitterer To: Qu Wenruo , Su Yue , Btrfs BTRFS Cc: Su Yue Date: Tue, 04 Sep 2018 13:45:56 +0200 In-Reply-To: References: <8d8c90d3edfcc9e73428d3730496d48b1160b39b.camel@scientia.net> <7146cafcc48d46ad123388d492807cbba08e101c.camel@scientia.net> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Tue, 2018-09-04 at 17:14 +0800, Qu Wenruo wrote: > However the backtrace can't tell which process caused such fsync > call. > (Maybe LVM user space code?) Well it was just literally before btrfs-check exited... so I blindly guesses... but arguably it could be just some coincidence. LVM tools are installed, but since I no longer use and PVs/LVs/etc. ... I'd doubt they'd do anything here. Cheers, Chris.