GNU bug report logs - #39712
Partitions produced by the installer not properly unmounted?

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#39712: closed (Partitions produced by the installer not
 properly unmounted?)
Date: Fri, 13 Mar 2020 15:53:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 13 Mar 2020 16:52:41 +0100
with message-id <87pndgz1yu.fsf <at> gmail.com>
and subject line Re: bug#39712: Partitions produced by the installer not properly unmounted?
has caused the debbugs.gnu.org bug report #39712,
regarding Partitions produced by the installer not properly unmounted?
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
39712: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=39712
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: bug-guix <at> gnu.org
Subject: Partitions produced by the installer not properly unmounted?
Date: Fri, 21 Feb 2020 12:13:22 +0100

Hi Mathieu,

I noticed that partitions created by the installer appear to not be
properly unmounted, at least when running in the context of (gnu tests
install):

--8<---------------cut here---------------start------------->8---
ludo <at> ribbon ~$ qemu-img convert -O raw /gnu/store/2d3s2nbb3j2c1hmkz52xds9rfbk4q3x3-installation /tmp/broken.raw
ludo <at> ribbon ~$ sudo losetup -P /dev/loop0 /tmp/broken.raw 
ludo <at> ribbon ~$ sudo dmesg |tail -3
[10703.869334] kvm [8936]: vcpu0, guest rIP: 0xffffffffac073dad disabled perfctr wrmsr: 0xc2 data 0xffff
[10742.475623] kvm [8957]: vcpu0, guest rIP: 0xffffffffaf073dad disabled perfctr wrmsr: 0xc2 data 0xffff
[11774.318468]  loop0: p1 p2 p3
ludo <at> ribbon ~$ sudo fdisk -l /dev/loop0
Disk /dev/loop0: 2.15 GiB, 2306867200 bytes, 4505600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 213AE251-0E91-499E-9184-0CCEC6DA64C7

Dispositiu    Start   Final Sectors  Size Tipus
/dev/loop0p1   2048    6143    4096    2M BIOS boot
/dev/loop0p2   6144  231423  225280  110M Intercanvi Linux
/dev/loop0p3 231424 4503551 4272128    2G Linux filesystem
ludo <at> ribbon ~$ sudo mount /dev/loop0p3 /mnt/usb
ludo <at> ribbon ~$ sudo dmesg |tail -3
[11774.318468]  loop0: p1 p2 p3
[11803.975300] EXT4-fs (loop0p3): recovery complete
[11803.977277] EXT4-fs (loop0p3): mounted filesystem with ordered data mode. Opts: (null)
--8<---------------cut here---------------end--------------->8---

However, I’ve added logging in ‘umount-user-partitions’ in (gnu
installer parted), and the installer does seem to unmount partitions
correctly.

Could it be a side effect of the MS_MOVE dance in
1d02052067e04d7dd8fd1ec17557ca02a30b9bcf?

(I’m observing this on ‘wip-installer-tests’, roughly based on
117d8467be232bcc1b0136d04f362d95d975ca95.)

Thanks,
Ludo’.

[Message part 3 (message/rfc822, inline)]

From: Mathieu Othacehe <m.othacehe <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 39712-done <at> debbugs.gnu.org
Subject: Re: bug#39712: Partitions produced by the installer not properly
 unmounted?
Date: Fri, 13 Mar 2020 16:52:41 +0100

This is fixed by 64704be417ab6f2788e8e3bc36fede1db35470e7.

Thanks,

Mathieu

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.