All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Apostolos B." <barz621@gmail.com>
To: Boris Burkov <boris@bur.io>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: No space left errors on shutdown with systemd-homed /home dir
Date: Thu, 27 Jan 2022 01:29:27 +0200	[thread overview]
Message-ID: <75011941-2b38-f148-be37-a0ce8f1490fc@gmail.com> (raw)
In-Reply-To: <YfHXFfHMeqx4MowJ@zen>

I don't have a bpftrace setup and sadly i cant do much debugging on this 
machine.

However i am sure its systemd that is involved in it. The few lines 
before the crash read:

Ιαν 26 22:45:06 mainland systemd[1]: Stopped WPA supplicant.
Ιαν 26 22:45:06 mainland systemd-homework[14696]: Discovered used LUKS 
device /dev/mapper/home-toliz, and validated password.
Ιαν 26 22:45:07 mainland systemd-homework[14696]: Successfully 
re-activated LUKS device.
Ιαν 26 22:45:07 mainland systemd-homework[14696]: Discovered used 
loopback device /dev/loop0.
Ιαν 26 22:45:07 mainland systemd-homework[14696]: offset = 1048576, size 
= 137436856320, image = 137438953472
Ιαν 26 22:45:07 mainland systemd-homework[14696]: Ready to resize image 
size 128.0G → 1.8G, partition size 127.9G → 1.8G, file system size 
127.9G → 1.7G.
Ιαν 26 22:45:07 mainland systemd-homework[14696]: Allocated additional 
124.8G.
Ιαν 26 22:45:07 mainland kernel: BTRFS info (device dm-0): relocating 
block group 2177892352 flags data
Ιαν 26 22:45:07 mainland kernel: BTRFS info (device dm-0): relocating 
block group 1104150528 flags data
Ιαν 26 22:45:08 mainland systemd-homework[14696]: Failed to resize file 
system: Read-only file system
Ιαν 26 22:45:08 mainland kernel: BTRFS info (device dm-0): relocating 
block group 30408704 flags metadata|dup

On 27/1/22 01:19, Boris Burkov wrote:
> On Thu, Jan 27, 2022 at 12:07:53AM +0200, Apostolos B. wrote:
>>   This is what homectl inspect user reports:
>>
>>    Disk Size: 128.0G
>>    Disk Usage: 3.8G (= 3.1%)
>>    Disk Free: 124.0G (= 96.9%)
>>
>> and this is what btrfs usage reports:
>>
>> sudo btrfs filesystem usage /home/toliz
>>
>> Overall:
>>      Device size:             127.98GiB
>>      Device allocated:               4.02GiB
>>      Device unallocated:     123.96GiB
>>      Device missing:                 0.00B
>>      Used:                           1.89GiB
>>      Free (estimated):             124.10GiB    (min: 62.12GiB)
>>      Free (statfs, df):             124.10GiB
>>      Data ratio:                  1.00
>>      Metadata ratio:                  2.00
>>      Global reserve:               5.14MiB    (used: 0.00B)
>>      Multiple profiles:                    no
>>
>> Data,single: Size:2.01GiB, Used:1.86GiB (92.73%)
>>     /dev/mapper/home-toliz       2.01GiB
>>
>> Metadata,DUP: Size:1.00GiB, Used:12.47MiB (1.22%)
>>     /dev/mapper/home-toliz       2.00GiB
>>
>> System,DUP: Size:8.00MiB, Used:16.00KiB (0.20%)
>>     /dev/mapper/home-toliz      16.00MiB
>>
>> Unallocated:
>>     /dev/mapper/home-toliz     123.96GiB
>>
> OK, there is plenty of unallocated space, thanks for confirming.
>
> Looking at the stack trace a bit more, the only thing that really sticks
> out as suspicious to me is btrfs_shrink_device, I'm not sure who would
> want to do that or why.
>
> It might be interesting to trace it and see if we can catch the
> parameters/caller in the act. If you have bpftrace setup on your system,
> could you try to setup something like:
>
> bpftrace -e 'kprobe:btrfs_shrink_device { printf("%s %llu %s\n", comm, arg1, kstack); }'
>
> to write to a file during shutdown?
>
>> On 26/1/22 23:50, Boris Burkov wrote:
>>> On Tue, Jan 25, 2022 at 07:46:51PM +0200, Apostolos B. wrote:
>>>> Hello.
>>>>
>>>> When i shut down my pc i get No space left errors -even though i have plenty
>>>> of space in both / and home dirs- and this message on the journal:
>>> How did you conclude you have plenty of space? df can be misleading with
>>> btrfs, for example. Can you please post the output of
>>> 'btrfs filesystem usage /home'
>>>
>>> Thanks,
>>> Boris
>>>
>>>> Ιαν 25 14:34:31 mainland kernel: BTRFS info (device dm-0): relocating block
>>>> group 2177892352 flags data
>>>> Ιαν 25 14:34:31 mainland kernel: BTRFS info (device dm-0): relocating block
>>>> group 1104150528 flags data
>>>> Ιαν 25 14:34:32 mainland kernel: BTRFS info (device dm-0): relocating block
>>>> group 30408704 flags metadata|dup
>>>> Ιαν 25 14:34:32 mainland kernel: ------------[ cut here ]------------
>>>> Ιαν 25 14:34:32 mainland kernel: BTRFS: Transaction aborted (error -28)
>>>> Ιαν 25 14:34:32 mainland kernel: WARNING: CPU: 4 PID: 18307 at
>>>> fs/btrfs/extent-tree.c:3066 __btrfs_free_extent+0x59c/0x950 [btrfs]
>>>> Ιαν 25 14:34:32 mainland kernel: Modules linked in: uhid rfcomm
>>>> snd_seq_dummy snd_hrtimer snd_seq snd_seq_device i2c_dev dm_crypt cbc
>>>> encrypted_keys trusted asn1_e>
>>>> Ιαν 25 14:34:32 mainland kernel:  snd_pcm_dmaengine kvm snd_hda_intel
>>>> iTCO_wdt irqbypass snd_intel_dspcfg intel_pmc_bxt crct10dif_pclmul
>>>> snd_intel_sdw_acpi hid_mul>
>>>> Ιαν 25 14:34:32 mainland kernel:  int340x_thermal_zone tpm_tis tpm_tis_core
>>>> wmi int3400_thermal tpm mac_hid rng_core acpi_thermal_rel acpi_tad acpi_pad
>>>> ipmi_devint>
>>>> Ιαν 25 14:34:32 mainland kernel: CPU: 4 PID: 18307 Comm: systemd-homewor
>>>> Tainted: G        W         5.16.2-arch1-1 #1
>>>> 86fbf2c313cc37a553d65deb81d98e9dcc2a3659
>>>> Ιαν 25 14:34:32 mainland kernel: Hardware name: SAMSUNG ELECTRONICS CO.,
>>>> LTD. 930XDB/931XDB/930XDY/NP930XDB-KF1IT, BIOS P03RFX.055.210415.SP
>>>> 04/15/2021
>>>> Ιαν 25 14:34:32 mainland kernel: RIP: 0010:__btrfs_free_extent+0x59c/0x950
>>>> [btrfs]
>>>> Ιαν 25 14:34:32 mainland kernel: Code: 24 14 ba 7e 0c 00 00 48 c7 c6 40 d4
>>>> bc c0 4c 89 ef e8 44 25 0c 00 e9 99 fe ff ff 44 89 e6 48 c7 c7 a0 95 bd c0
>>>> e8 24 6c 28 e>
>>>> Ιαν 25 14:34:32 mainland kernel: RSP: 0018:ffffb1ab80f837a0 EFLAGS: 00010246
>>>> Ιαν 25 14:34:32 mainland kernel: RAX: 0000000000000000 RBX: 0000000000000000
>>>> RCX: 0000000000000000
>>>> Ιαν 25 14:34:32 mainland kernel: RDX: 0000000000000000 RSI: 0000000000000000
>>>> RDI: 0000000000000000
>>>> Ιαν 25 14:34:32 mainland kernel: RBP: 0000000000d07000 R08: 0000000000000000
>>>> R09: 0000000000000000
>>>> Ιαν 25 14:34:32 mainland kernel: R10: 0000000000000000 R11: 0000000000000000
>>>> R12: 00000000ffffffe4
>>>> Ιαν 25 14:34:32 mainland kernel: R13: ffff982240648888 R14: ffff9823b62514d0
>>>> R15: fffffffffffffff7
>>>> Ιαν 25 14:34:32 mainland kernel: FS:  00007f336b49ea80(0000)
>>>> GS:ffff9823c3700000(0000) knlGS:0000000000000000
>>>> Ιαν 25 14:34:32 mainland kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
>>>> 0000000080050033
>>>> Ιαν 25 14:34:32 mainland kernel: CR2: 00007fa3c5637050 CR3: 000000010cfd0002
>>>> CR4: 0000000000770ee0
>>>> Ιαν 25 14:34:32 mainland kernel: PKRU: 55555554
>>>> Ιαν 25 14:34:32 mainland kernel: Call Trace:
>>>> Ιαν 25 14:34:32 mainland kernel:  <TASK>
>>>> Ιαν 25 14:34:32 mainland kernel: __btrfs_run_delayed_refs+0x25c/0x10d0
>>>> [btrfs c10068e329b0dae5c9bb0cca4f6f33712f172b3b]
>>>> Ιαν 25 14:34:32 mainland kernel: btrfs_run_delayed_refs+0x73/0x200 [btrfs
>>>> c10068e329b0dae5c9bb0cca4f6f33712f172b3b]
>>>> Ιαν 25 14:34:32 mainland kernel:  ? __reserve_bytes+0x164/0x7d0 [btrfs
>>>> c10068e329b0dae5c9bb0cca4f6f33712f172b3b]
>>>> Ιαν 25 14:34:32 mainland kernel: btrfs_commit_transaction+0xf6/0xb20 [btrfs
>>>> c10068e329b0dae5c9bb0cca4f6f33712f172b3b]
>>>> Ιαν 25 14:34:32 mainland kernel:  relocate_block_group+0x6e/0x5a0 [btrfs
>>>> c10068e329b0dae5c9bb0cca4f6f33712f172b3b]
>>>> Ιαν 25 14:34:32 mainland kernel: btrfs_relocate_block_group+0x18b/0x340
>>>> [btrfs c10068e329b0dae5c9bb0cca4f6f33712f172b3b]
>>>> Ιαν 25 14:34:32 mainland kernel:  btrfs_relocate_chunk+0x27/0x100 [btrfs
>>>> c10068e329b0dae5c9bb0cca4f6f33712f172b3b]
>>>> Ιαν 25 14:34:32 mainland kernel:  btrfs_shrink_device+0x277/0x5a0 [btrfs
>>>> c10068e329b0dae5c9bb0cca4f6f33712f172b3b]
>>>> Ιαν 25 14:34:32 mainland kernel:  btrfs_ioctl_resize+0x449/0x470 [btrfs
>>>> c10068e329b0dae5c9bb0cca4f6f33712f172b3b]
>>>> Ιαν 25 14:34:32 mainland kernel:  btrfs_ioctl+0x1fa8/0x2fc0 [btrfs
>>>> c10068e329b0dae5c9bb0cca4f6f33712f172b3b]
>>>> Ιαν 25 14:34:32 mainland kernel:  ? btrfs_statfs+0x418/0x570 [btrfs
>>>> c10068e329b0dae5c9bb0cca4f6f33712f172b3b]
>>>> Ιαν 25 14:34:32 mainland kernel:  ? _copy_to_user+0x1c/0x50
>>>> Ιαν 25 14:34:32 mainland kernel:  ? do_statfs_native+0xaf/0xe0
>>>> Ιαν 25 14:34:32 mainland kernel:  ? __seccomp_filter+0x39e/0x570
>>>> Ιαν 25 14:34:32 mainland kernel:  ? __x64_sys_ioctl+0x8b/0xd0
>>>> Ιαν 25 14:34:32 mainland kernel:  __x64_sys_ioctl+0x8b/0xd0
>>>> Ιαν 25 14:34:32 mainland kernel:  do_syscall_64+0x59/0x90
>>>> Ιαν 25 14:34:32 mainland kernel:  ? do_syscall_64+0x69/0x90
>>>> Ιαν 25 14:34:32 mainland kernel:  ? syscall_exit_to_user_mode+0x23/0x50
>>>> Ιαν 25 14:34:32 mainland kernel:  ? do_syscall_64+0x69/0x90
>>>> Ιαν 25 14:34:32 mainland kernel:  ? syscall_exit_to_user_mode+0x23/0x50
>>>> Ιαν 25 14:34:32 mainland kernel:  ? do_syscall_64+0x69/0x90
>>>> Ιαν 25 14:34:32 mainland kernel:  ? exc_page_fault+0x72/0x180
>>>> Ιαν 25 14:34:32 mainland kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae
>>>> Ιαν 25 14:34:32 mainland kernel: RIP: 0033:0x7f336baa359b
>>>> Ιαν 25 14:34:32 mainland kernel: Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff
>>>> ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10
>>>> 00 00 00 0f 0>
>>>> Ιαν 25 14:34:32 mainland kernel: RSP: 002b:00007ffc945a04d8 EFLAGS: 00000246
>>>> ORIG_RAX: 0000000000000010
>>>> Ιαν 25 14:34:32 mainland kernel: RAX: ffffffffffffffda RBX: 0000000072184000
>>>> RCX: 00007f336baa359b
>>>> Ιαν 25 14:34:32 mainland kernel: RDX: 00007ffc945a0570 RSI: 0000000050009403
>>>> RDI: 0000000000000004
>>>> Ιαν 25 14:34:32 mainland kernel: RBP: 0000000000000004 R08: 0000000000000000
>>>> R09: 00007ffc945a0370
>>>> Ιαν 25 14:34:32 mainland kernel: R10: 0000000072184000 R11: 0000000000000246
>>>> R12: 00007ffc945a0570
>>>> Ιαν 25 14:34:32 mainland kernel: R13: 0000000000000000 R14: 000055c0fade8cc0
>>>> R15: 00007ffc945a1920
>>>> Ιαν 25 14:34:32 mainland kernel:  </TASK>
>>>> Ιαν 25 14:34:32 mainland kernel: ---[ end trace 81d5963d986040ee ]---
>>>> Ιαν 25 14:34:32 mainland kernel: BTRFS: error (device dm-0) in
>>>> __btrfs_free_extent:3066: errno=-28 No space left
>>>> Ιαν 25 14:34:32 mainland kernel: BTRFS info (device dm-0): forced readonly
>>>> Ιαν 25 14:34:32 mainland kernel: BTRFS: error (device dm-0) in
>>>> btrfs_run_delayed_refs:2149: errno=-28 No space left
>>>>
>>>> The dm-0 device is my /home directory and is set up using systemd-homed
>>>>
>>>> Kernel version: 5.16.2
>>>>
>>>> Systemd version: 250.3
>>>>
>>>> btrfs-progs version: 5.16
>>>>
>>>> It seems to cause no issues thus far but a solution would be good to have.
>>>>
>>>> Thanks in advance.
>>>>

  reply	other threads:[~2022-01-26 23:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 17:46 No space left errors on shutdown with systemd-homed /home dir Apostolos B.
2022-01-26 21:50 ` Boris Burkov
2022-01-26 22:07   ` Apostolos B.
2022-01-26 23:19     ` Boris Burkov
2022-01-26 23:29       ` Apostolos B. [this message]
2022-01-27  7:59         ` Wang Yugui
2022-01-27  8:51           ` Wang Yugui
2022-01-27 19:13         ` Goffredo Baroncelli
2022-01-27 20:48       ` Chris Murphy
2022-01-29  9:53         ` Goffredo Baroncelli
2022-01-29 18:01           ` Chris Murphy
2022-01-30  9:27             ` Goffredo Baroncelli
2022-01-31  9:41               ` Colin Guthrie
2022-02-01 19:55                 ` Neal Gompa
2022-05-31 12:44                   ` Colin Guthrie
2022-05-31 18:12                     ` Goffredo Baroncelli
2022-06-01  9:36                       ` Colin Guthrie
2022-07-23 19:09                         ` Chris Murphy
2022-02-01  4:26           ` Zygo Blaxell
2022-07-23 19:26             ` Chris Murphy

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=75011941-2b38-f148-be37-a0ce8f1490fc@gmail.com \
    --to=barz621@gmail.com \
    --cc=boris@bur.io \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.