← Back to team overview

ubuntu-phone team mailing list archive

Re: SDK kit issues with 15.04

 

Hi Mitchell again,

It seems Christian found a workaround I just tested it to be working.
So, adding the following line:

none /home none rslave 0 0

to /etc/schroot/click/fstab seems to work. While doing it, I removed
my previous /home/timo line so that wasn't needed after all.

-Timo


On Wed, May 6, 2015 at 9:10 AM, Timo Jyrinki <timo.jyrinki@xxxxxxxxxxxxx> wrote:
> Hi Mitchell,
>
> This is the unfortunate bug #1427264 [1] that I'm also hitting and
> filed a duplicate bug some time ago.
>
> [1] https://bugs.launchpad.net/ubuntu/+source/click/+bug/1427264
>
> I didn't get the workaround working though, if I understood it
> correctly. I added the following line to the file
> /etc/schroot/click/fstab:
>
> /home/timo      /home/timo      none    rw,rbind        0       0
>
> But got the same error still. I did restart schroot after the change.
> CC:ing Sebastien who has written the bug description.
>
> -Timo
>
> On Wed, May 6, 2015 at 2:06 AM, Mitchell Reese
> <dev@xxxxxxxxxxxxxxxxxxxxx> wrote:
>> Hi folks, i've got a problem installing an armhf kit with the Ubuntu-sdk on
>> 15.04. I'm on a fresh install of 15.04, and installed the ubuntu-sdk
>> package. Have also added the ppa in case, but no change.
>>
>> Everything runs fine with installing the kit for my Nexus 7 (2013) tablet,
>> until it crashes at the end. Seems to be something to do with the encrypted
>> home partition I have... the sdk finishes setting up the kit with errors
>> (creates the chroot, but then removes it, uninstalling all the packages it
>> downloaded). Then my laptop behaves like I've unmounted my ecryptfs file
>> system... i.e., if I browse to /home/user., I get the default files in an
>> ecryptfs setup that haven't been mounted, nothing else is there until I
>> reboot. I'm using the default ecryptfs setup by checking the 'encrypt home
>> directory' on the initial install. This was not an issue with 14.10 (same
>> setup)
>>
>> Any ideas what's going wrong here? I had expected an easier setup...
>>
>> Below is the last bit of output from creating the kit:
>>
>> E: 10mount: umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home/mitchell:
>> target is busy E: 10mount: (In some cases useful info about processes that
>> E: 10mount: use the device is found by lsof(8) or fuser(1).) E:
>> click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2: Chroot
>> setup failed: stage=setup-stop
>> umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home/mitchell:
>> target is busy (In some cases useful info about processes that use the
>> device is found by lsof(8) or fuser(1).)
>> umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home:
>> target is busy (In some cases useful info about processes that use the
>> device is found by lsof(8) or fuser(1).)
>> umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2:
>> target is busy (In some cases useful info about processes that use the
>> device is found by lsof(8) or fuser(1).)
>> Command returned 1: schroot u root -c source:click-ubuntu-sdk-15.04-armhf -
>> /finish.sh
>> Traceback (most recent call last): File "/usr/bin/click", line 86, in
>> sys.exit(main()) File "/usr/bin/click", line 82, in main return
>> mod.run(args) File
>> "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 266, in run
>> return args.func(parser, args) File
>> "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 68, in
>> create return chroot.create(args.keep_broken_chroot) File
>> "/usr/lib/python3/dist-packages/click/chroot.py", line 551, in create
>> self.destroy() File "/usr/lib/python3/dist-packages/click/chroot.py", line
>> 649, in destroy shutil.rmtree(chroot_dir) File
>> "/usr/lib/python3.4/shutil.py", line 464, in rmtree _rmtree_safe_fd(fd,
>> path, onerror) File "/usr/lib/python3.4/shutil.py", line 406, in
>> _rmtree_safe_fd onerror(os.rmdir, fullname, sys.exc_info()) File
>> "/usr/lib/python3.4/shutil.py", line 404, in _rmtree_safe_fd os.rmdir(name,
>> dir_fd=topfd) OSError: [Errno 16] Device or resource busy: 'home'
>> There was an error creating the click target, cleaning up
>> umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home/mitchell:
>> target is busy (In some cases useful info about processes that use the
>> device is found by lsof(8) or fuser(1).) umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home:
>> target is busy (In some cases useful info about processes that use the
>> device is found by lsof(8) or fuser(1).)
>> umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2:
>> target is busy (In some cases useful info about processes that use the
>> device is found by lsof(8) or fuser(1).)
>> Traceback (most recent call last): File "/usr/bin/click", line 86, in
>> sys.exit(main()) File "/usr/bin/click", line 82, in main return
>> mod.run(args) File
>> "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 266, in run
>> return args.func(parser, args) File
>> "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 91, in
>> destroy return chroot.destroy() File
>> "/usr/lib/python3/dist-packages/click/chroot.py", line 649, in destroy
>> shutil.rmtree(chroot_dir) File "/usr/lib/python3.4/shutil.py", line 464, in
>> rmtree _rmtree_safe_fd(fd, path, onerror) File
>> "/usr/lib/python3.4/shutil.py", line 406, in _rmtree_safe_fd
>> onerror(os.rmdir, fullname, sys.exc_info()) File
>> "/usr/lib/python3.4/shutil.py", line 404, in _rmtree_safe_fd os.rmdir(name,
>> dir_fd=topfd) OSError: [Errno 16] Device or resource busy: 'home'
>> Unmounting
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2
>> Unmount failed... trying to force
>> umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2:
>> target is busy (In some cases useful info about processes that use the
>> device is found by lsof(8) or fuser(1).)
>> Unmounting
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home
>> Unmount failed... trying to force Unmounting
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home
>> failed Unmounting
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home/mitchell
>> Unmount failed... trying to force Unmounting
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home/mitchell
>> failed Deleting /etc/schroot/chroot.d/click-ubuntu-sdk-15.04-armhf Deleting
>> /var/lib/schroot/chroots/click-ubuntu-sdk-15.04-armhf
>> umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home:
>> mountpoint not found umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home:
>> mountpoint not found umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home/mitchell:
>> mountpoint not found umount:
>> /var/lib/schroot/mount/click-ubuntu-sdk-15.04-armhf-04fb8d7e-df93-48cb-b9f5-3fe7013914d2/home/mitchell:
>> mountpoint not found
>> click target was removed successfully
>> ---Click exited with errors, please check the output---
>>
>> --
>> Mailing list: https://launchpad.net/~ubuntu-phone
>> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>> More help   : https://help.launchpad.net/ListHelp


Follow ups

References