From: Arsalan Awan <Arsalan_Awan@mentor.com>
To: <poky@yoctoproject.org>
Subject: [PATCH 0/1] fixing initrd mounts w/ spaces fail to move to real rootfs
Date: Thu, 28 Jun 2018 14:25:32 +0500 [thread overview]
Message-ID: <cover.1530176497.git.Arsalan_Awan@mentor.com> (raw)
From: "Arsalan H. Awan" <Arsalan_Awan@mentor.com>
When there are spaces in the mount points of devices e.g.:
a partition mounted at "/run/media/My Root Partition-sda1",
the initrd fails to move such mount points over to the
corresponding directories at /media under the real root filesystem,
and the mount points would appear at the same location as they were
mounted on when detected by initrd, for example:
here: "/run/media/My Root Partition-sda1"
instead of here: "/media/My Root Partition-sda1"
This causes issues such as:
* The disks/partitions cannot be formated with any filesystem
using e.g. mkfs.ext4 or mke2fs in general. When tried to do so
by making sure the device is not mounted, it failed with
errors such as:
> /dev/sda1 is apparently in use by the system; will not make a
filesystem here!
> /dev/sda1: Device or resource busy while setting up superblock
* The read/write operations become extremely slow. e.g. Under testing,
it took approx. 2 hours just to copy 700 MB of data to the partition,
and it took more than 40 minutes to delete that data from it.
Same operations took under 5 minutes on a partition that had no
spaces in its mount point (or that was successfully moved to real
root by initrd and appeared under /media instead of /run/media).
This commit fixes such issues by quoting the arguments of failing mount
move commands and by parsing OCT or HEX encoded special characters
such as spaces to ASCII charecters in the mount points as kernel
populates the procfs like so.
The following changes since commit 13c465663d0d1835773fb30baba345396cf0906e:
documentation: Updated manual revision tables with 2.2.4 release date (2018-05-24 17:23:02 +0100)
are available in the git repository at:
git://push.yoctoproject.org/poky-contrib ArsalanHAwan/initrdscripts-init-live
Arsalan H. Awan (1):
initrdscripts/init-live.sh: fix mounts w/ spaces fail to move to real
rootfs
meta/recipes-core/initrdscripts/files/init-live.sh | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2018-06-28 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 9:25 Arsalan Awan [this message]
2018-06-28 9:26 ` [PATCH 1/1] initrdscripts/init-live.sh: fix mounts w/ spaces fail to move to real rootfs Arsalan Awan
2018-06-28 11:23 ` Alexander Kanavin
2018-06-28 14:18 ` Awan, Arsalan
-- strict thread matches above, loose matches on Subject: below --
2018-06-28 14:16 [PATCH 0/1] fixing initrd " Arsalan Awan
2018-07-13 11:07 ` Awan, Arsalan
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=cover.1530176497.git.Arsalan_Awan@mentor.com \
--to=arsalan_awan@mentor.com \
--cc=poky@yoctoproject.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.