Unable to remove loop: loop0 is still in use #519

Although tomb is a ZSH shell script you don't have zsh installed?

Not sure why tomb --version cannot find zsh as it works as expected otherwise (minus my trouble with loop0).
Even though I don't have zsh installed directly, the tomb package provides zsh as dependency so it should be available.

Did you check the loop device with lsof?

Yes, this was one of my first steps. It doesn't return anything, hence my confusion. I should have probably mentioned this.

I originally thought it may be related to my bind-hooks, but they are all removed properly when I do tomb close.

$ tomb list
.tomb-real . [.d-crate] open on /media/.d-crate using (rw,nodev,noatime)
.tomb-real . [.d-crate] open since Sat 06 Jul 2024 06:48:01 PM WEST
.tomb-real . [.d-crate] open by franz from /dev/pts/0 on panther
.tomb-real . [.d-crate] size 270M of which 48M (19%) is used: 203M free
.tomb-real . [.d-crate] hooks /home/franz/.ssh
.tomb-real . [.d-crate] hooks /home/franz/.aws

I read somewhere that the kernel itself may be keeping the loop busy, but I'm not too familiar with this.

Odd with zsh. No real magic involved. The script only invokes zsh --version. Is it available in $PATH?
After closing the tomb, does losetup -d <loopdevice> or losetup -D remove the loop device?
And can you maybe post a full open and close cycle of tomb with the debug output option -D? Do you have after a reboot automatically a loop device? It's odd if tomb can setup a loop device but doesn't get around to remove it in the endgame.

Oh, and what distribution is at work? I noticed that the found programs are relatively old. Maybe tomb has something in place which isn't available for you. Something we may need to consider.

Odd with zsh. No real magic involved. The script only invokes zsh --version. Is it available in $PATH?

This is how tomb runs:

which tomb
/home/franz/.guix-home/profile/bin/tomb
#!/gnu/store/v9p25q9l5nnaixkhpap5rnymmwbhf9rp-bash-minimal-5.1.16/bin/bash
export PATH="/gnu/store/hp1wfjq5vpnyhc23fgnqzl1kvjhpixw5-mlocate-0.26/bin:/gnu/store/9v9xjn6lvmavsqbsfr0s22ydmzldzq85-coreutils-9.1/bin:/gnu/store/3r5a91mwgvg7np8773z2brgjv604skd8-e2fsprogs-1.47.0/sbin:/gnu/store/8bcrzzbl8c1wdr8awkd7mirm949227lp-pinentry-1.2.1/bin:/gnu/store/llpxyyym3nvp2d8iny34m7z1b7dqgwpk-gnupg-2.2.39/bin:/gnu/store/zfymrgmxa7r3g59s8gisjzy3zr0fz342-cryptsetup-2.3.7/sbin:/gnu/store/amhk3vjn6npgb5qh6xb2g2nqb4fzyqar-gettext-minimal-0.21/bin:/gnu/store/6nyp9cvksvyfww5d7j7rvm43jb46p521-lsof-4.94.0/bin:/gnu/store/0csa6dgrn9sb62pxs21yn5a9nq16017q-qrencode-4.1.1/bin:/gnu/store/jg90sh9cy35va656x2773kkl0rqfi9sb-steghide-0.5.1/bin:/gnu/store/wgfvgbd0yayl77zpkc10ibc5g78accgm-util-linux-2.37.4/bin:/gnu/store/ln6hxqjvz6m9gdd9s97pivlqck7hzs99-glibc-2.35/bin${PATH:+:}$PATH"
exec -a "0ドル" "/gnu/store/vzpnv8v7y24wlwixbzakwb0dyx18c917-tomb-2.9/bin/.tomb-real" "$@"

I guess the problem with zsh --version comes from how dependencies are handled; Currently zsh is included as package input, whereas it should probably be a propagated-inputs, so that it's included in the path.

propagated-inputs is similar to inputs, but the specified packages will be automatically installed to profiles alongside the package they belong to

Not sure I understand why it works regardless - except for this detail.

After closing the tomb, does losetup -d or losetup -D remove the loop device?

I'll have to come back to you on this again later.
As of right now, I can cleanly open / close the mentioned tomb, without any issue.

The only changes are:

• Newer Linux kernel (6.9.8 vs 6.9.6)

Oh, and what distribution is at work?

I'm on guix.

$ guix --version
guix (GNU Guix) c1d367f57e89c3f2efd964e6d638bd89b0b1df97

I do appreciate your input on this, thank you!