Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unmount failed... but had no reason to do so #53

Open
dmigowski opened this issue Jul 30, 2023 · 0 comments
Open

Unmount failed... but had no reason to do so #53

dmigowski opened this issue Jul 30, 2023 · 0 comments

Comments

@dmigowski
Copy link

dmigowski commented Jul 30, 2023

fstransform version 0.9.3 - conversion of reiserfs to ext3 on Debian 10. Somewhere at the beginning I get:

12:03:32 fsmove: progress: 88.0% done,   2.4 gigabytes still to move, estimated 15 seconds left
12:03:37 fsmove: progress: 90.0% done,   2.0 gigabytes still to move, estimated 20 seconds left
12:03:37 fsmove: job completed.
12:03:37 fstransform: unmounting and running '/sbin/fsck' (disk check) on loop file '/tmp/fstransform.mount.17211/.fstransform.loop.17211'
12:03:46 fsck: fsck from util-linux 2.33.1
12:03:47 fsck: /dev/loop0: 182167/2436448 Dateien (0.3% nicht zusammenhängend), 5160437/9744640 Blöcke
12:03:47 fstransform: disconnected loop device '/dev/loop0' from file '/tmp/fstransform.mount.17211/.fstransform.loop.17211'
12:03:47 fstransform: unmounting device '/dev/sda3' before disk check
12:03:47 umount: /tmp/fstransform.mount.17211: target is busy.

12:03:47 ERROR! fstransform: command '/bin/umount /dev/sda3' failed (exit status 32)
                this is potentially a problem.
                you can either quit now by pressing ENTER or CTRL+C,

                or, if you know what went wrong, you can fix it yourself,
                then manually run the command '/bin/umount /dev/sda3'
                (or something equivalent)
                and finally resume this script by typing CONTINUE and pressing ENTER:

Went into another shell, did the umount manually, and it worked without problems. The target wasn't busy anymore. Maybe one should add a small wait loop here or wait until the previously started processes operating on the filesystem are really stopped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant