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=-3.6 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 E2593C433E3 for ; Tue, 25 Aug 2020 07:22:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2F38120578 for ; Tue, 25 Aug 2020 07:22:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=protonmail.com header.i=@protonmail.com header.b="DHrqb3UO" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729396AbgHYHWM (ORCPT ); Tue, 25 Aug 2020 03:22:12 -0400 Received: from mail-40140.protonmail.ch ([185.70.40.140]:21129 "EHLO mail-40140.protonmail.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729374AbgHYHWK (ORCPT ); Tue, 25 Aug 2020 03:22:10 -0400 X-Greylist: delayed 90607 seconds by postgrey-1.27 at vger.kernel.org; Tue, 25 Aug 2020 03:22:09 EDT Date: Tue, 25 Aug 2020 07:22:03 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1598340127; bh=Ry0/F9XzTVOXkghEYpiUW2Q+X5IckgjPzonjL/Lu2JU=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=DHrqb3UOkdxtHtN6t8QHUIi3+NZtIeV3H6ooJL+7Tw3QNlACJsFSlLKPMurYCgHFW 2lpatF4kNx1Ouj23UKh/fZvR0dg1v1Q/gbg0JeHE7gzHqTkBPwPH7jkG07I7CP49ob SLAZfOEE+qIAon95iGqMy0c3V4fiLD7epGEZpd6o= To: Chris Murphy From: Andrii Zymohliad Cc: "linux-btrfs@vger.kernel.org" , Andrei Borzenkov Reply-To: Andrii Zymohliad Subject: Re: [Help] Can't login to my systemd-homed user account due to fallocate failure Message-ID: <8oT9s0Jlzpgp2ctPAXOixSR03oOiPXaitR0AiOkNdBsYHwjPMfjK7CoVAPXuvj71hiUTH-fKoSevAM-To8iSPPBvGRvZeBkU0Nd1_NPonyU=@protonmail.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org > Seems like bool should take either yes, true, on, or 1. But I'm an odd > duck. Anyway! Glad it works. Ah, sorry, I didn't notice I changed true to on. It doesn't matter. The thi= ng is, it should be "homectl update", and not during activation/authorizati= on itself. > Next question is to find out why you have shared extents. # filefrag -v /home/azymohliad.home | grep -m 10 shared 55082: 52756487..52756516: 291198215.. 291198244: 30: 291722503: = shared 55083: 52756518..52756522: 291198246.. 291198250: 5: = shared 55084: 52756524..52756528: 291198252.. 291198256: 5: = shared 55085: 52756530..52756530: 291198258.. 291198258: 1: = shared 55086: 52756532..52756534: 291198260.. 291198262: 3: = shared 55087: 52756536..52756546: 291198264.. 291198274: 11: = shared 55088: 52756548..52756553: 291198276.. 291198281: 6: = shared 55089: 52756555..52756557: 291198283.. 291198285: 3: = shared 55090: 52756559..52756578: 291198287.. 291198306: 20: = shared 55091: 52756582..52756595: 291198310.. 291198323: 14: = shared And for all of these extents the output of "btrfs inspect-internal" is: //home/azymohliad.home I call it on root / filesystem, e.g.: # btrfs inspect-internal logical-resolve $[291198246 * 4096] /