I have installed mountall 2.5 from lucid to my karmic and the problem is
still occuring
--
Loops trying to mount NTFS partition after failure
https://bugs.launchpad.net/bugs/480564
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Will a fix be applied to Karmic? Is there some other workaround? I don't
like having to killall mountall on every boot.
--
Loops trying to mount NTFS partition after failure
https://bugs.launchpad.net/bugs/480564
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package mountall - 2.0
---
mountall (2.0) lucid; urgency=low
[ Scott James Remnant ]
* "mount" event changed to "mounting", to make it clear it happens
before the filesystem is mounted. Added "mounted" event which
happens afterwards.
* Dropped
In my case, the failure to mount the ntfs partition was only because the
mount point was missing. `service udev stop; sleep 2; service udev
start` stopped the continuous logging in /var/log/syslog and
/var/log/daemon.log, but I was able to re-trigger it by `mount -a`.
Looking at /etc/fstab and chec
** Changed in: mountall (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
** Changed in: mountall (Ubuntu)
Milestone: None => lucid-alpha-2
--
Loops trying to mount NTFS partition after failure
https:
If you need any more tests performed let me know as I left the machine in
it's current error state and am running LTSP (from another server) on it
until otherwise notified.
2009/12/13 Scott James Remnant
> Yes, the strace shows us getting a uevent, and that triggering the re-
> attempt to mount
Yes, the strace shows us getting a uevent, and that triggering the re-
attempt to mount it. Not sure how to filter these out, we need to react
to change events for software raid
--
Loops trying to mount NTFS partition after failure
https://bugs.launchpad.net/bugs/480564
You received this bug not
There's an strace in bug #479096 showing the continued attempt to mount
the NTFS partition; this strange behaviour seems limited to NTFS,
something is making it try again over and over again.
(Assumedly mount.ntfs opens the block device for writing, which triggers
a udev change event for it)
** S
