You are not logged in.
Pages: 1
When I shutdown my laptop today, the log said failed to umount /var/cache. It worked fine yesterday, is it because systemd updated?
I have reboot the system 3 times, and the error always show up.
the disk format is btrfs, and /var/cache is on the subvolume named @cache.
/var/cache btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvol=/@cache 0 0
/var/log btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvol=/@log 0 0systemd[1]: Failed unmounting /var/cache.Last edited by smartyin (2025-12-20 03:17:30)
Offline
is it because systemd updated?
Most likely, same as https://bbs.archlinux.org/viewtopic.php … 4#p2278914 ?
Offline
I add the workaround line in sd-shutdown, but still have the problem.
systemd[1]: Unmounting /.snapshots...
systemd[1]: Unmounting /boot...
systemd[1]: Unmounting /home...
systemd[1]: Unmounting Temporary Directory /tmp...
systemd[1]: Unmounting /var/cache...
systemd[1]: Unmounting /var/tmp...
systemd[1]: Stopping Flush Journal to Persistent Storage...
systemd[1]: systemd-backlight@backlight:intel_backlight.service: Deactivated su>
systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:intel_ba>
systemd[1]: Finished Virtual Console Setup.
umount[1866]: umount: /var/cache: target is busy.
systemd[1]: \x2esnapshots.mount: Deactivated successfully.
systemd[1]: Unmounted /.snapshots.
systemd[1]: boot.mount: Deactivated successfully.
systemd[1]: Unmounted /boot.
systemd[1]: home.mount: Deactivated successfully.
systemd[1]: Unmounted /home.
systemd[1]: tmp.mount: Deactivated successfully.Offline
umount[1866]: umount: /var/cache: target is busy.What does the rest of the journal look like? Apparently some process (refused to die?) is still using the cache.
Offline
umount[1866]: umount: /var/cache: target is busy.What does the rest of the journal look like? Apparently some process (refused to die?) is still using the cache.
I don't know how to find out the process, can you tell me?
Offline
https://man.archlinux.org/man/ps.1
But /that/ process is by now gone - you'll have to wait until this happens again.
Offline
I cannot find any clue about this problem. It is so weird.
Offline
Oh, sorry - I confused this w/ another thread in my last post.
Please post your complete system journal for the last boot where this happened, eg.
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.stfor the previous one.
Offline
Oh, sorry - I confused this w/ another thread in my last post.
Please post your complete system journal for the last boot where this happened, eg.sudo journalctl -b -1 | curl -F 'file=@-' 0x0.stfor the previous one.
thanks.
I reinstall the system and packages and config everything step by step, want to find out what's wrong.
Till now, everything works fine only without the splash plymouth. But I donnot now why.
Offline
Since you destroyed all evidence, you'll have to wait and see whether this re-emerges, then update the thread w/ the journal.
Offline
I have just comfirmed the problem reason is installing the package named plymouth.
When I install the package, and use it in mkinitcpio.conf like this:
HOOKS=(base udev plymouth autodetect microcode modconf kms keyboard keymap consolefont block filesystems resume fsck)with the theme like this:
[Daemon]
Theme=scriptthen the /var/cache will be busy when shutdown and cannot be unmounted. After uninstall that package, everything works fine.
Offline
Do you have the problem w/ any other plymouth theme?
https://wiki.archlinux.org/title/Plymou … _the_theme
Offline
Do you have the problem w/ any other plymouth theme?
https://wiki.archlinux.org/title/Plymou … _the_theme
Yes, even using the default theme.
Offline
https://gitlab.freedesktop.org/plymouth … h/-/issues
Is this a regression w/ systemd 259 or has it always been like that?
Offline
I am not sure. Plymouth works fine, only find the failure when press esc key to show the log.
Offline
It might be an artifact of the cache not being on the root partition - if it doesn't cause notable delays or other issues you could report it to the plymouth developers but otherwise just ignore it.
Offline
Pages: 1