Your message dated Tue, 18 Aug 2009 12:02:03 +0000
with message-id <e1mdno7-0006yu...@ries.debian.org>
and subject line Bug#535238: fixed in usbmount 0.0.17.1
has caused the Debian Bug report #535238,
regarding [usbmount] Partitions of USB-disk mounted to same mountpoint
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
535238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: usbmount
Version: 0.0.17
Severity: serious

Hi there,

I didn't use my USB-disk for two or three months now, but I know that I
never had any trouble ... in the meantime usbmount 0.0.17 came out and I
believe there is where the trouble starts. Unfortunately usbmount 0.0.16
isn't available anymore in debian repositories, so I cannot doublecheck
if it works with that.

My USB-disk (not flash) has two partitions: 1. vfat 2. ext3. Both
partitions are recognized and have no errors. When the disk is
connected, it is recognized and usbmount mounts them with correct FS
types, but both partitions on the exact same location (/media/usb0):

-------- excerpt from /var/log/syslog --------
Jul  1 00:55:05 sokrates kernel: [440465.213768]  sdb: sdb1 sdb2
Jul  1 00:55:05 sokrates kernel: [440465.265885] sd 6:0:0:0: [sdb] Attached 
SCSI disk
Jul  1 00:55:05 sokrates kernel: [440465.266074] sd 6:0:0:0: Attached scsi 
generic sg1 type 0
Jul  1 00:55:05 sokrates usbmount[21891]: trying to acquire lock 
/var/run/usbmount/.mount-dev-sdb.lock
Jul  1 00:55:05 sokrates usbmount[21891]: acquired lock 
/var/run/usbmount/.mount-dev-sdb.lock
Jul  1 00:55:05 sokrates usbmount[21891]: testing whether /dev/sdb is readable
Jul  1 00:55:05 sokrates usbmount[21891]: /dev/sdb does not contain a 
filesystem or disklabel
Jul  1 00:55:06 sokrates usbmount[21916]: trying to acquire lock 
/var/run/usbmount/.mount-dev-sdb2.lock
Jul  1 00:55:06 sokrates usbmount[21920]: trying to acquire lock 
/var/run/usbmount/.mount-dev-sdb1.lock
Jul  1 00:55:06 sokrates usbmount[21916]: acquired lock 
/var/run/usbmount/.mount-dev-sdb2.lock
Jul  1 00:55:06 sokrates usbmount[21916]: testing whether /dev/sdb2 is readable
Jul  1 00:55:06 sokrates usbmount[21920]: acquired lock 
/var/run/usbmount/.mount-dev-sdb1.lock
Jul  1 00:55:06 sokrates usbmount[21920]: testing whether /dev/sdb1 is readable
Jul  1 00:55:06 sokrates usbmount[21916]: /dev/sdb2 contains a filesystem or 
disklabel
Jul  1 00:55:06 sokrates usbmount[21920]: /dev/sdb1 contains a filesystem or 
disklabel
Jul  1 00:55:06 sokrates usbmount[21916]: /dev/sdb2 contains filesystem type 
ext3
Jul  1 00:55:06 sokrates usbmount[21916]: mountpoint /media/usb0 is available 
for /dev/sdb2
Jul  1 00:55:06 sokrates usbmount[21916]: executing command: mount -text3 
-onoexec,nodev,noatime /dev/sdb2 /media/usb0
Jul  1 00:55:06 sokrates usbmount[21920]: /dev/sdb1 contains filesystem type 
vfat
Jul  1 00:55:06 sokrates usbmount[21920]: mountpoint /media/usb0 is available 
for /dev/sdb1
Jul  1 00:55:06 sokrates usbmount[21920]: executing command: mount -tvfat 
-onoexec,nodev,noatime /dev/sdb1 /media/usb0
Jul  1 00:55:06 sokrates kernel: [440466.513924] kjournald starting.  Commit 
interval 5 seconds
Jul  1 00:55:06 sokrates kernel: [440466.519001] EXT3 FS on sdb2, internal 
journal
Jul  1 00:55:06 sokrates kernel: [440466.519044] EXT3-fs: recovery complete.
Jul  1 00:55:06 sokrates kernel: [440466.519260] EXT3-fs: mounted filesystem 
with ordered data mode.
Jul  1 00:55:06 sokrates usbmount[21916]: executing command: run-parts 
/etc/usbmount/mount.d
Jul  1 00:55:06 sokrates usbmount[21920]: executing command: run-parts 
/etc/usbmount/mount.d
-------- end excerpt from /var/log/syslog --------

-------- some commands --------
$ mount | grep usb
none on /proc/bus/usb type usbfs
(rw,nosuid,nodev,devgid=1004,devmode=664)
/dev/sdb1 on /media/usb0 type vfat (rw,noexec,nodev,noatime)
/dev/sdb2 on /media/usb0 type ext3 (rw,noexec,nodev,noatime)

# umount /dev/sdb1
umount: cannot umount /dev/sdb1 -- /dev/sdb2 is mounted over it on the
same point.
-------- some commands --------

It seems that usbmount is in a race when checking the available
mountpoint and find it both times available ... it's just a matter of
luck which partition is mounted first. This might lead to data loss,
since a standard user might not recognize that there is such problem.

Regards

Hans-Georg Bork

PS: It might be possible that the bug lies within udev which starts
usbmount simultaneous. If this is true, please forward to them. 

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.26-3-sokrates.home

Debian Release: squeeze/sid
  500 unstable        www.debian-multimedia.org 
  500 unstable        ftp.de.debian.org 
  500 testing         ftp.be.debian.org 

--- Package information. ---
Depends             (Version) | Installed
=============================-+-===========
udev                          | 0.141-1
lockfile-progs                | 0.1.13


Package's Recommends field is empty.

Package's Suggests field is empty.



Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message ---
Source: usbmount
Source-Version: 0.0.17.1

We believe that the bug you reported is fixed in the latest version of
usbmount, which is due to be installed in the Debian FTP archive:

usbmount_0.0.17.1.dsc
  to pool/main/u/usbmount/usbmount_0.0.17.1.dsc
usbmount_0.0.17.1.tar.gz
  to pool/main/u/usbmount/usbmount_0.0.17.1.tar.gz
usbmount_0.0.17.1_all.deb
  to pool/main/u/usbmount/usbmount_0.0.17.1_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 535...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rogério Brito <rbr...@ime.usp.br> (supplier of updated usbmount package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Tue, 18 Aug 2009 08:45:55 -0300
Source: usbmount
Binary: usbmount
Architecture: source all
Version: 0.0.17.1
Distribution: unstable
Urgency: low
Maintainer: Rogério Brito <rbr...@ime.usp.br>
Changed-By: Rogério Brito <rbr...@ime.usp.br>
Description: 
 usbmount   - automatically mount and unmount USB mass storage devices
Closes: 535238 539386
Changes: 
 usbmount (0.0.17.1) unstable; urgency=low
 .
   * usbmount:
     + revert patch from #403209 (seems to introduce race conditions)
       (Closes: #535238)
   * usbmount.conf:
     + include ext4 so that it can be mounted automatically.
     + add MOUNTOPTIONS nodiratime. Closes: #539386. (Tks Jari Aalto)
   * debian/control:
     + include comment (allowed by policy).
     + update standards version to 3.8.2 (no changes necessary).
Checksums-Sha1: 
 cfa25a69cdad9e6ce4724eebc421a9d8d2ded8ef 942 usbmount_0.0.17.1.dsc
 922df5ec8078d57be9db4f24aa9b2f3aa023db0a 11454 usbmount_0.0.17.1.tar.gz
 f409df56e5de8a8b5d38f885130f88c3859d5eb5 13998 usbmount_0.0.17.1_all.deb
Checksums-Sha256: 
 b49d8e6afb5a6a55dfd2476eb6312b5299621e174fded73ace0f31057cc86c37 942 
usbmount_0.0.17.1.dsc
 8183dffad543749e1f1d1c54c9bde7bb8461a497c0240d5fa4489a79d1ef27d9 11454 
usbmount_0.0.17.1.tar.gz
 a620f2f044636a75327c8cca515b536ac9e14065b1fec91f1491b5f6ddbdcd64 13998 
usbmount_0.0.17.1_all.deb
Files: 
 8fe1bf85b88cdde7b4345af740c4a8db 942 admin extra usbmount_0.0.17.1.dsc
 e24f6df4c7cba9358e3b0ab440cb9595 11454 admin extra usbmount_0.0.17.1.tar.gz
 8198f61741419bd184107207e3a85113 13998 admin extra usbmount_0.0.17.1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqKl0kACgkQCFqbMnwsrrjz4ACfbB2Ux2g8pLYBdv+S2V9MVpWt
9ZkAn2g0pNXWze8/FI2XrzgPEi8WItEX
=vdmv
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to