public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Stephen Ecker <stephenecker240@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: expand-on-first-boot broken with btrfs subvolume
Date: Wed, 22 Jan 2025 18:21:36 -0800 (PST)	[thread overview]
Message-ID: <3652dfef-495c-431c-b91b-9ff1e6735157n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1577 bytes --]

I have an initramfs script that moves the root filesystem to btrfs 
subvolume on first boot.  This breaks the expand-last-partition.sh script 
for the oddest reason:

line 4:  *findmnt / -o source -n*

normally this line outputs something like: */dev/name*,
but when on a btrfs subvolume, it outputs: */dev/name[@subvol] *

This leads to the error: "*Boot device equals root device - no partitioning 
found"*
not exactly sure why, as I didn't dissect every line. I found that changing 
the command in line 4 to: *findmnt / -o sources -n* 
fixed the problem... I tried this after I noticed running *findmnt / 
--output-all*, the device name alone was listed under SOURCES, where SOURCE 
had the subvol appended.

I don't really *like* this solution, partly because 1) an ubuntu 
installation I have doesn't even have the *sources* output (though it was 
added 3 years ago, 
see: https://github.com/util-linux/util-linux/blame/master/misc-utils/findmnt.c#L135 
)... but mainly because I don't know exactly what this will look like for 
other device / filesystem types.

maybe we could add a sed expression to trim past the device name?  i.e.  

*findmnt / -o source -n | sed 's, [\[.*]*,,' *

thoughts?

thanks,
   Stephen

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/3652dfef-495c-431c-b91b-9ff1e6735157n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2178 bytes --]

             reply	other threads:[~2025-01-23  2:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23  2:21 Stephen Ecker [this message]
2025-01-23  7:38 ` Uladzimir Bely
2025-01-23  7:50   ` Stephen Ecker

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=3652dfef-495c-431c-b91b-9ff1e6735157n@googlegroups.com \
    --to=stephenecker240@gmail.com \
    --cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox