All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	David Sterba <dsterba@suse.cz>, Omar Sandoval <osandov@fb.com>
Subject: Re: Hibernation into swap file
Date: Mon, 27 Jan 2020 11:25:48 -0800	[thread overview]
Message-ID: <20200127192548.GA683123@vader> (raw)
In-Reply-To: <CAJCQCtSLYY-AY8b1WZ1D4neTrwMsm_A61-G-8e6-H3Dmfue_vQ@mail.gmail.com>

On Thu, Jan 23, 2020 at 10:20:40AM -0700, Chris Murphy wrote:
> On Mon, May 6, 2019 at 5:31 AM David Sterba <dsterba@suse.cz> wrote:
> > for the reference https://bugzilla.kernel.org/show_bug.cgi?id=202803
> > and https://github.com/systemd/systemd/issues/11939
> 
> I've read these, but can't tell if it's still necessary to manually
> use 'btrfs-map-physical' to find the correct offset, and use it on the
> kernel command line manually?

Yes, it's still necessary, and it's unlikely that systemd will ever go
through the trouble of doing the btrfs-map-physical itself. What we
really want is the interface I described in [1], but I won't be able to
work on that any time soon. It'd be great if someone interested in the
feature would take a stab at it.

1: https://github.com/systemd/systemd/issues/11939#issuecomment-471684411

      parent reply	other threads:[~2020-01-27 19:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-05  7:50 Hibernation into swap file Maksim Fomin
2019-05-05  9:08 ` Andrei Borzenkov
2019-05-06  5:40   ` Chris Murphy
2019-05-06 18:25     ` Maksim Fomin
2019-05-09  6:13       ` Andrei Borzenkov
2019-05-09 17:04         ` Maksim Fomin
2019-05-06 11:32 ` David Sterba
2020-01-23 17:20   ` Chris Murphy
2020-01-24  4:03     ` Andrei Borzenkov
2020-01-27 19:25     ` Omar Sandoval [this message]

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=20200127192548.GA683123@vader \
    --to=osandov@osandov.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=osandov@fb.com \
    /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.