From: Andrii Zymohliad <azymohliad@protonmail.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: [Help] Can't login to my systemd-homed user account due to fallocate failure
Date: Sun, 23 Aug 2020 15:31:47 +0000 [thread overview]
Message-ID: <bdJVxLiFr_PyQSXRUbZJfFW_jAjsGgoMetqPHJMbg-hdy54Xt_ZHhRetmnJ6cJ99eBlcX76wy-AvWwV715c3YndkxneSlod11P1hlaADx0s=@protonmail.com> (raw)
Hello! I've lost the ability to log in to my systemd-homed user account, and after some investigation on Systemd mailing list I was directed here. I would be very grateful for any help!
My root partition is ~475GiB with BTRFS, my home partition is a ~400GiB LUKS-encrypted partition on a loopback file (also BTRFS) created by systemd-homed (residing at /home/azymohliad.home). Which leaves ~75GiB for the rest of the root FS.
Recently I've lost the ability to log in to that user account, because during authentication systemd does fallocate call for the image. CLI alternative for my case (suggested on systemd mailing list, I don't really know what is it) is:
fallocate -l 403G -n /home/azymohliad.home
Which fails:
fallocate: fallocate failed: No space left on device
My first idea was that I occupied all those ~75GiB on a root partition, but cleaning didn't help (I definitely released more space than I could occupy during the last working session).
Here are some details about my system:
uname -a
Linux az-wolf-pc 5.8.3-arch1-1 #1 SMP PREEMPT Fri, 21 Aug 2020 16:54:16 +0000 x86_64 GNU/Linux
btrfs --version
btrfs-progs v5.7
I can mount my home manually like this:
losetup -fP /home/azymohliad.home
cryptsetup open /dev/loop0p1
mount /dev/mapper/home /mnt
and then,
btrfs fi show
Label: none uuid: b68411ce-702a-4259-9121-ac21c9119ddf
Total devices 1 FS bytes used 299.71GiB
devid 1 size 476.44GiB used 476.44GiB path /dev/nvme0n1p2
Label: 'azymohliad' uuid: 4ffae38b-42c9-4e53-89a1-3d21cd862938
Total devices 1 FS bytes used 221.92GiB
devid 1 size 402.72GiB used 258.02GiB path /dev/mapper/home
btrfs fi df /
Data, single: total=475.43GiB, used=299.28GiB
System, single: total=4.00MiB, used=80.00KiB
Metadata, single: total=1.01GiB, used=437.05MiB
GlobalReserve, single: total=61.03MiB, used=0.00B
btrfs fi df /mnt
Data, single: total=256.01GiB, used=221.18GiB
System, single: total=4.00MiB, used=48.00KiB
Metadata, single: total=2.01GiB, used=749.92MiB
GlobalReserve, single: total=297.11MiB, used=0.00B
dmesg.log: https://gitlab.com/-/snippets/2007155
What's interesting to me from above, the partition size on /home/azymohliad.home is 402.72GiB, but the file system size is 256.01GiB, and the image file size is 256.64GiB (from btrfs fi du /home, although ls -lh reports 403GiB). I'm not really sure, but iirc the fs and image sizes were around 403GiB too earlier. Could it be that it somehow got automatically reduced?
Could I do anything to make that fallocate call (with -l 403G) working? It will allow me to authenticate to homectl and resize the home partition from there.
If not, what is the safe way to shrink that LUKS-partition size? Maybe then systemd-homed would do fallocate for less space and it would work.
If from my assumptions you could tell that I'm looking in the wrong direction, please give me a hint. Thanks for taking time to read it!
next reply other threads:[~2020-08-23 15:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 15:31 Andrii Zymohliad [this message]
2020-08-23 15:37 ` [Help] Can't login to my systemd-homed user account due to fallocate failure Hugo Mills
2020-08-23 16:21 ` Andrei Borzenkov
2020-08-23 16:55 ` Andrii Zymohliad
2020-08-23 18:16 ` Andrei Borzenkov
2020-08-23 18:49 ` Andrii Zymohliad
2020-08-24 3:01 ` Chris Murphy
2020-08-24 2:23 ` Chris Murphy
2020-08-24 2:50 ` Chris Murphy
2020-08-24 6:11 ` Andrii Zymohliad
2020-08-24 7:13 ` Chris Murphy
2020-08-24 7:25 ` Andrii Zymohliad
2020-08-24 8:28 ` Andrii Zymohliad
2020-08-24 8:32 ` Andrii Zymohliad
2020-08-24 18:51 ` Chris Murphy
2020-08-25 7:22 ` Andrii Zymohliad
2020-08-25 19:05 ` Chris Murphy
2020-08-25 20:47 ` Andrii Zymohliad
2020-08-25 22:34 ` Chris Murphy
2020-08-26 13:37 ` Andrii Zymohliad
2020-08-26 13:40 ` Andrii Zymohliad
2020-08-26 19:06 ` Chris Murphy
[not found] ` <dHPyoaNUuxoqxJjpSUjcxZvk21ew2ObKWFFhX0efJKBqjG8m27px3mPupviQuM3HYQDEcYQGFQ9jOprBuAX4x1Em3oVOyDl6EhKwEJSiuXs=@protonmail.com>
2020-08-26 19:15 ` Chris Murphy
2020-08-26 19:57 ` Andrii Zymohliad
2020-08-26 21:06 ` Chris Murphy
2020-08-26 21:08 ` Chris Murphy
2020-08-26 21:14 ` Chris Murphy
2020-08-27 6:48 ` Andrii Zymohliad
2020-09-01 15:01 ` Chris Murphy
2020-09-01 17:06 ` Andrii Zymohliad
2020-09-01 17:22 ` Chris Murphy
2020-09-01 17:27 ` Andrii Zymohliad
2020-09-01 17:31 ` Andrii Zymohliad
2020-09-01 20:45 ` Chris Murphy
2020-09-02 16:35 ` Chris Murphy
2020-08-27 5:39 ` Andrei Borzenkov
2020-08-24 15:23 ` Andrei Borzenkov
2020-08-24 17:42 ` Goffredo Baroncelli
[not found] <bdJVxLiFr=5FPyQSXRUbZJfFW=5FjAjsGgoMetqPHJMbg-hdy54Xt=5FZHhRetmnJ6cJ99eBlcX76wy-AvWwV715c3YndkxneSlod11P1hlaADx0s=3D@protonmail.com>
[not found] ` <CAJCQCtTC2yi4HRqg6fkMrxw33TVSBh=5FyAKtnX-Z1-nXSVjBW7w@mail.gmail.com>
[not found] ` <Yy8-04dbNru1LWPcNZ9UxsagH1b0KNsGn7tDEnxVOqS812IqGiwl37dj4rxAh05gEP8QoNJ5F=5FEa6CZ8iZgvnupuq5Qzc38gl69MceWMc9s=3D@protonmail.com>
[not found] ` <CAJCQCtSqe=5FoqRZWYP7iLJcGQnzZkC4vmoYVTm=5F9RPb8eb0-E6Q@mail.gmail.com>
[not found] ` <BfU9s11rmWxGNQdKqifkB1JKOJcgqAN49OZdV4LAOgo1W2AguRebwCPVosOiMVjMTzuSmsk=5FEfbkl02s31niRqtCS67WJ9S7=5Fs4jiK9afeA=3D@protonmail.com>
[not found] ` <E212ihR5U8HVCyaalepkxQUX3wOj6IXd1yUFHj-PFFtyU7ma-A49vmB8QwfQG5gUVo2nCMbVpPo7C2ccooRO0ExVrIbdLP9sBpnjMOcefHo=3D@protonmail.com>
[not found] ` <lyGE8gPEf9cUEMJceWoJWD=5Fibk4viZXU0yG5VzbNe9yueGbkcnl1FkJrFZZufhWd5y2vNOgAwfYSpJ4Gia5Tow4wdmQXiGuETdyuNmnemJY=3D@protonmail.com>
[not found] ` <CAJCQCtR3gbJxJn24qyDfHWh9kQG7BSC=3DNnoGHmRKPnaQ+P7yyg@mail.gmail.com>
[not found] ` <8oT9s0Jlzpgp2ctPAXOixSR03oOiPXaitR0AiOkNdBsYHwjPMfjK7CoVAPXuvj71hiUTH-fKoSevAM-To8iSPPBvGRvZeBkU0Nd1=5F NPonyU=3D?= =?us-ascii?Q?@protonmail.com>
[not found] ` <CAJCQCtQH3h=3DNNr6PX3HZp7SbkgqZtNNdihi4aBMFvx+DN79XeA@mail.gmail.com>
[not found] ` <6LDov933WqF3kLH8jtkEh-pfK6pRe0o6-Y9l3NcO2mVhswDL7rhbHyda71OnztoJKfgqqQT9jj1Ba52lz=5FugNFmmRtzN33BlSa5pCvds0F8=3D@protonmail.com>
[not found] ` <CAJCQCtQDt=3Dx7WCX7KhWz=5FpPn4yB1YdZm9jN29jRuQ DFy=3DZTO?= =?us-ascii?Q?jA@mail.gmail.com>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='bdJVxLiFr_PyQSXRUbZJfFW_jAjsGgoMetqPHJMbg-hdy54Xt_ZHhRetmnJ6cJ99eBlcX76wy-AvWwV715c3YndkxneSlod11P1hlaADx0s=@protonmail.com' \
--to=azymohliad@protonmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).