[Parted-maintainers] Bug#662084: libparted0debian1: False busy/mounted detection of some sdaX, X > 16, partitions
Linus Lüssing
linus.luessing at web.de
Sun Mar 4 00:16:32 UTC 2012
Package: libparted0debian1
Version: 2.3-8
Severity: normal
Hi,
Today I tried to create quite a few logical partitions and ended up
having 23 partitions in (g)parted in total.
Some of these, i.e. /dev/sda17 and /dev/sda19, were detected as mounted
and had the lock symbol next to it in gparted. I however could not
unmount and therefore could not delete this partition both within parted
or gparted.
Also a `ls /dev/sda*` or a `cat /proc/partitions` only showed a
/dev/sda1 to /dev/sda16:
---
$ cat /proc/partitions
major minor #blocks name
8 0 625131864 sda
8 1 81892356 sda1
8 2 4914251 sda2
8 3 1 sda3
8 4 430013440 sda4
8 5 16384 sda5
8 6 16384 sda6
8 7 16384 sda7
8 8 16384 sda8
8 9 16384 sda9
8 10 16384 sda10
8 11 16384 sda11
8 12 16384 sda12
8 13 16384 sda13
8 14 16384 sda14
8 15 16384 sda15
259 0 16384 sda16
---
parted 3.1 seems to work fine though. I could delete sda19 to sda23 with
it. And after having deleted those partitions funnilly sda17 to sda18
reappear within /dev and /proc/partitions:
---
$ cat /proc/partitions | grep sda
8 0 625131864 sda
8 1 81892356 sda1
8 2 4914251 sda2
8 3 1 sda3
8 4 430013440 sda4
8 5 16384 sda5
8 6 16384 sda6
8 7 16384 sda7
8 8 16384 sda8
8 9 16384 sda9
8 10 16384 sda10
8 11 16384 sda11
8 12 16384 sda12
8 13 16384 sda13
8 14 16384 sda14
8 15 16384 sda15
259 0 16384 sda16
259 1 16384 sda17
259 2 16384 sda18
---
After having used parted 3.1 and having those partitions reappear in the
kernel's partition table (Linux 3.2.4), parted 2.3.8 still does not work
though:
---
(parted) print
Model: ATA SAMSUNG HM640JJ (scsi)
Disk /dev/sda: 640GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 83.9GB 83.9GB primary
2 83.9GB 88.9GB 5032MB primary
3 88.9GB 200GB 111GB extended
5 88.9GB 88.9GB 16.8MB logical
6 88.9GB 88.9GB 16.8MB logical
7 88.9GB 88.9GB 16.8MB logical
8 88.9GB 89.0GB 16.8MB logical
9 89.0GB 89.0GB 16.8MB logical
10 89.0GB 89.0GB 16.8MB logical
11 89.0GB 89.0GB 16.8MB logical
12 89.0GB 89.0GB 16.8MB logical
13 89.0GB 89.1GB 16.8MB logical
14 89.1GB 89.1GB 16.8MB logical
15 89.1GB 89.1GB 16.8MB logical
16 89.1GB 89.1GB 16.8MB logical
17 89.1GB 89.1GB 16.8MB logical
4 200GB 640GB 440GB primary
(parted) rm 17
Error: Partition /dev/sda17 is being used. You must unmount it before you modify it with Parted.
---
Although it is definitely not mounted:
---
$ sudo mount
udev on /dev type devtmpfs (rw,relatime,size=892316k,nr_inodes=223079,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=179796k,mode=755)
/dev/mapper/sda1_crypt on / type ext4 (rw,noatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,size=359592k)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
/dev/sdb1 on /boot type ext3 (ro,noexec,noatime,nodiratime,errors=continue,barrier=1,data=ordered)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,relatime,size=359592k)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 77G 59G 18G 78% /
udev 872M 0 872M 0% /dev
tmpfs 176M 612K 175M 1% /run
/dev/mapper/sda1_crypt 77G 59G 18G 78% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 352M 132K 352M 1% /tmp
/dev/sdb1 358M 304M 35M 90% /boot
tmpfs 352M 132K 352M 1% /run/shm
---
And the only swap partition is from /dev/sda2:
---
$ sudo dmsetup ls
sda1_crypt (254, 1)
sda2_crypt (254, 2)
$ cat /proc/swaps
Filename Type Size Used Priority
/dev/dm-2
---
So the busy detection seems to be wrong if I am not missing anything.
I am going to use the 3.1 parted build from now on and try to get my
initially planned setup working, I therefore might not be able to
reproduce this issue with other builds soonish if asked to do so.
I also found #619330 which sounds similar to my issue, but I'm not sure
whether my one is a duplicate. Could be interesting to check whether
#619330 also has been fixed with parted 3.1.
I'm also not sure about the severity level. It pretty much locked me out
from deleting partitions and doing anything useful, but didn't seem to
cause any harm to any of the other, old partitions. And maybe my 23
partitions setup is just weird anyway :P.
Cheers, Linus
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (x86_64)
Kernel: Linux 3.2.4 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libparted0debian1 depends on:
ii libblkid1 2.20.1-3
ii libc6 2.13-27
ii libdevmapper1.02.1 2:1.02.67-2
ii libuuid1 2.20.1-3
ii multiarch-support 2.13-27
libparted0debian1 recommends no packages.
Versions of packages libparted0debian1 suggests:
ii libparted0-dev <none>
ii libparted0-i18n <none>
ii parted 2.3-8
-- no debconf information
More information about the Parted-maintainers
mailing list