Rogerio:
Thanks for posting the bug report. Let me know if this should be added to the
bug report.
I have been going back through releases of Voyage to see when they broke
usbmount.
I figured out that mount-usb.rules was a fix for mounting usb drives at boot.
I'm not sure if it could have intercepted the trigger for usbmount. Here is its
content:
## usb disk comes up too late for /etc/init.d/mountall.sh
ENV{ID_FS_LABEL}=="usbrw", ACTION=="add", RUN+="/bin/mount /dev/%k"
ENV{ID_FS_LABEL}=="usbmedia", ACTION=="add", RUN+="/bin/mount /dev/%k"
I'm not sure how to tell if a device is managed by device mapper.
Here is some relevant info from rules.d/55-dm.rules:
KERNEL=="device-mapper", NAME="mapper/control"
SUBSYSTEM!="block", GOTO="dm_end"
KERNEL!="dm-[0-9]*", GOTO="dm_end"
# There is a new change event generated in block layer since kernel
# version 2.6.32. It adds notification for changes in read-only
# attribute. We don't want to misinterpret the regular meaning of change
# events for DM devices and we don't want to apply the rules prematurely,
# therefore we disable them in this situation.
ENV{DISK_RO}=="1", GOTO="dm_disable"
And the following generates an error in udevadm test --action=add
/sys/class/block/sda1
# Normally, we operate on "change" events only. But when
# coldplugging, there's an "add" event present. We have to
# recognize this and do our actions in this particular
# situation, too. Also, we don't want the nodes to be
# created prematurely on "add" events while not coldplugging.
ACTION=="add", ENV{STARTUP}!="1", NAME="", GOTO="dm_end"
The blank name field causes this error:
add_rule: NAME="" is ignored, because udev will not delete any device nodes,
please remove it from /lib/udev/rules.d/55-dm.rules:57
However I don't think that is the culprit.
-Demian
-----Original Message-----
From: Rogério Brito [mailto:rbr...@ime.usp.br]
Sent: Monday, July 12, 2010 4:29 PM
To: Demian Martin
Subject: Re: problem with usbmount
Package: usbmount
Severity: normal
Owner: Demian Martin <demian...@yahoo.com>
Hi, Demian.
I am just sending this message so that it becomes filed in the Bug
tracking system.
By the way, to file any bug report, just send an e-mail to
<sub...@bugs.debian.org> and, in the first lines of the e-mail, put the
information like I did above (the Owner: part is not necessary, in
general).
I am including the submission e-mail to the BTS as a blind-carbon copy.
Regards,
On Jul 12 2010, Demian Martin wrote:
> Rogerio:
> Thanks for the very prompt reply. I was not sure it was a bug or me just not
> having the basics right. The Debian bugtracker system has me a little lost. I
> tried to use reportbug but could not figure out how to send the finished
> report.
> There is nothing sensitive in this info.
> /dev/sda1 is a removable usb disk
> I did confirm I can manually mount and unmount it with no problems.
> I can get you whatever details you want and can even arrange remote access if
> that helps.
> I'll get you the version info on udev, and usbmount is version 0.0.20.
> Anything else you need?
> I'll try to figure out how to file the bug.
> -Demian
>
>
> -----Original Message-----
> From: Rogério Brito [mailto:rbr...@ime.usp.br]
> Sent: Monday, July 12, 2010 2:07 PM
> To: Demian Martin
> Subject: Re: problem with usbmount
>
> Dear Demian,
>
> First, thanks for the report.
>
> I almost filed this bug myself on Debian's Bug Tracking system on your
> behalf, so that it doesn't get missed, but I thought that you, perhaps,
> would like to do it yourself, if you feel that any sensitive information
> is contained here.
>
> If you can, please file the bug there, as it will help me to keep things
> organized.
>
> That being said, let's see the status of this.
>
> On Jul 12 2010, Demian Martin wrote:
> > I had it working fine on an earlier version of this system (Voyage
> > Linux, a debian derivative http://linux.voyage.hk/ ) using kernel
> > 2.6.30.
>
> OK.
>
> > I built a new system using kernel 2.6.32 and it just won't work. I
> > have done a lot of troubleshooting but can't figure out why it doesn't
> > work.
>
> Well, the kernel, by itself, should not be a problem, since I have been
> running every single kernel even before I started maintaining usbmount,
> and, in fact, I have been using some highly experimental kernels from
> Linus Torvald's git tree.
>
> > The issue seems to be one of the dbus not triggering the final mount
>
> I suppose that you meant *udev* here, not *dbus*?
>
> > 1) New system uses /sys/block/sda/sda1
> > 2) Old system uses /sys/class/block/sda1
>
> My system has both, but they should be abstracted away by udev. I am
> running my self-compiled kernel 2.6.34-ish. BTW, the version of udev in
> question is important, as is the version of usbmount, since udev changed
> the infra-structure that usbmount used.
>
> > 3) New system has two new rules that appear
> > a. 55-dm.rules
> > b. mount-usb.rules
>
> I have the first (from dmsetup), but not the second.
>
> > How do I troubleshoot this? I don't know what to do next.
>
> I would need a bit more details on what stage exactly doesn't work.
>
> > udevadm_test: version 158
>
> OK, that's recent enough.
>
> > udev_rules_apply_to_event: IMPORT '/sbin/blkid -o udev -p /dev/sda1'
> > /lib/udev/rules.d/60-persistent-storage.rules:134
>
> Just a question: /dev/sda1 is a partition on a removable device, right?
> Is it managed by device mapper, in any way?
>
> > auraliti-player:~# udevadm test --action=add /sys/class/block/sda1
> > run_command: calling: test
> > udevadm_test: version 146
>
> I don't quite recall the exact version when udev migrated from vol_id to
> blkid, but it is around this version listed above.
>
>
> Regards,
>
> --
> Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 1024D/7C2CAEB8
> http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
> DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
>
>
--
Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 1024D/7C2CAEB8
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
