All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
To: "Apostolos B." <barz621@gmail.com>
Cc: Boris Burkov <boris@bur.io>, linux-btrfs@vger.kernel.org
Subject: Re: No space left errors on shutdown with systemd-homed /home dir
Date: Thu, 27 Jan 2022 15:59:19 +0800	[thread overview]
Message-ID: <20220127155918.A4FD.409509F4@e16-tech.com> (raw)
In-Reply-To: <75011941-2b38-f148-be37-a0ce8f1490fc@gmail.com>

Hi,

Why 'resize image size 128.0G → 1.8G'?

This 'No space left errors ' happen when 'resize image size 128.0G → 1.8G'.
and it will not happen when ''resize image size 128.0G → 2.0G'?

Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2022/01/27

> 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%)



  reply	other threads:[~2022-01-27  7:59 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.
2022-01-27  7:59         ` Wang Yugui [this message]
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=20220127155918.A4FD.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --cc=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.