f5bb0a3163
On kernel 5.10.178, when a squashfs file is stored on an EXT4 filesystem backed by a dm-crypt volume, dissecting fails: $ SYSTEMD_LOG_LEVEL=debug systemd-dissect /var/foo/bar.raw Opened '/var/foo/bar.raw' in O_RDONLY access mode, with O_DIRECT enabled. Couldn't find any partition table to derive sector size of. loop2: Acquired exclusive lock. Could not enable direct IO mode, proceeding in buffered IO mode. Successfully acquired /dev/loop2, devno=7:2, nr=2, diskseq=87 Opened /dev/loop2 (fd=3, whole_block_devnum=7:2, diskseq=87). Name: bar.raw Size: 67.2M Sec. Size: 512 Arch.: n/a Successfully forked off '(sd-dissect)' as PID 4110. Mounting /proc/self/fd/3 (squashfs) on /tmp/dissect-Zk3K5F (MS_RDONLY|MS_NODEV "")... Failed to mount /proc/self/fd/3 (type squashfs) on /tmp/dissect-Zk3K5F (MS_RDONLY|MS_NODEV ""): Input/output error Failed to mount dissected image: Input/output error Failed to read /etc/hostname of image: No such file or directory /etc/machine-id file of image is empty. Failed to read has-init-system boolean: Input/output error (sd-dissect) failed with exit status 1. Failed to acquire image metadata: Input/output error The kernel shows I/O errors: kernel: blk_update_request: I/O error, dev loop2, sector 0 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 0 kernel: SQUASHFS error: Failed to read block 0x0: -5 kernel: unable to read squashfs_super_block This is independent of a particular filesystem and can be reproduced reliably in my setup, starting from freshly formatted disks. Instead of continuing when O_DIRECT fails, start over the setup process without the flag, including opening a new FD, to make the kernel happy. |
||
---|---|---|
.clusterfuzzlite | ||
.github | ||
.semaphore | ||
catalog | ||
coccinelle | ||
docs | ||
factory | ||
hwdb.d | ||
LICENSES | ||
man | ||
mkosi.conf.d | ||
mkosi.presets | ||
modprobe.d | ||
network | ||
po | ||
presets | ||
rules.d | ||
shell-completion | ||
src | ||
sysctl.d | ||
sysusers.d | ||
test | ||
tmpfiles.d | ||
tools | ||
units | ||
xorg | ||
.clang-format | ||
.ctags | ||
.dir-locals.el | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.packit.yml | ||
.pylintrc | ||
.vimrc | ||
.ycm_extra_conf.py | ||
configure | ||
LICENSE.GPL2 | ||
LICENSE.LGPL2.1 | ||
Makefile | ||
meson_options.txt | ||
meson.build | ||
mkosi.kernel.config | ||
NEWS | ||
README | ||
README.md | ||
TODO |
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.