My WD extrnal usb drive automounts fine; however, the disk access is painfully slow... even for read only. Yes, I have read the release notes and I have tried the work-around for slow usb hotplug... it does not work. If I umount the drive and manually mount it with : mount -t reiserfs /def/sda1 /mnt/WD_External -o rw,nodev,nosuid,sync ... then it works wonderfully... nice and fast... What is wrong with automount usbfs, and how do I correct it. At the moment I have placed a 20thirdparty file in /usr/share/hal/fdi/policy/20thirdparty to prevent this volume.uuid from auto-mounting by setting should_mount to false. Then I mount it manually. This machine is my laptop. The usb drive is a 60GB external that I use mainly for read-only reference database. I am running Suse 10 on this machine. What is the solution to this problem? By the way, mounting without sync does not fix the problem. Thanks
On Wednesday 23 August 2006 12:00, Mark Harris wrote:
My WD extrnal usb drive automounts fine; however, the disk access is painfully slow... even for read only.
Yes, I have read the release notes and I have tried the work-around for slow usb hotplug... it does not work.
If I umount the drive and manually mount it with :
mount -t reiserfs /def/sda1 /mnt/WD_External -o rw,nodev,nosuid,sync
... then it works wonderfully... nice and fast...
What is wrong with automount usbfs, and how do I correct it. At the moment I have placed a 20thirdparty file in /usr/share/hal/fdi/policy/20thirdparty to prevent this volume.uuid from auto-mounting by setting should_mount to false. Then I mount it manually.
This machine is my laptop. The usb drive is a 60GB external that I use mainly for read-only reference database. I am running Suse 10 on this machine.
What is the solution to this problem? By the way, mounting without sync does not fix the problem.
Thanks
I do something similar, but since my use dated to the days when auto-mount could not be counted on, I just put an entry in fstab with the mount point and options I wanted, and allowed "user" to mount. Then I can open up KdiskFree and right click to mount/unmount. Mostly I do this on Suse 9.3, but yesterday I plugged that drive into this 10.1 box and it did mount, but it was slow as you saw. Added the line to fstab and it was much better. -- _____________________________________ John Andersen
On Thursday 24 August 2006 03:51, John Andersen wrote:
I just put an entry in fstab with the mount point and options I wanted, and allowed "user" to mount. Then I can open up KdiskFree and right click to mount/unmount. Yeah, this works great. Do you happen to know what is going on with udev so that usb automounts are not working well? Do you know if someone is working on a cure..?
Thanks -- Kind regards, M Harris <><
On Friday 25 August 2006 23:06, M Harris wrote:
On Thursday 24 August 2006 03:51, John Andersen wrote:
I just put an entry in fstab with the mount point and options I wanted, and allowed "user" to mount. Then I can open up KdiskFree and right click to mount/unmount.
Yeah, this works great. Do you happen to know what is going on with udev so that usb automounts are not working well? Do you know if someone is working on a cure..?
Thanks
Have seen some chatter on this list that auto mounting was backed out of the kernel for some reason or other, and left to the distro or desktop providers. Don't know If I got the details right. -- _____________________________________ John Andersen
On Sat, 2006-08-26 at 00:57 -0800, John Andersen wrote:
Have seen some chatter on this list that auto mounting was backed out of the kernel for some reason or other, and left to the distro or desktop providers.
Don't know If I got the details right.
I can't confirm your statement, but I can confirm the result of it! I have wasted tons of hours and the price of the boxed set on 10.1 and am backing out to 9.3 today! Automount will NOT work in twm or fvwm2 by any method I've tried. It works SOMETIMES in kde by clicking on the removable device in "my computer" and then finding it in /media/. It is sad when a reliable old friend turns into a drunken bum! NOVELL should immediately recall 10.1 and pull it from the store shelves. I can only imagine the damage this release is doing to the linux community. I might have to remove the SuSE Penguin Pin from my cowboy hat! Tom (every boxed set since 6.2...yep, I'm on a modem!)
On Saturday 26 August 2006 06:32, Tom Patton wrote:
On Sat, 2006-08-26 at 00:57 -0800, John Andersen wrote:
Have seen some chatter on this list that auto mounting was backed out of the kernel for some reason or other, and left to the distro or desktop providers.
Don't know If I got the details right.
I can't confirm your statement, but I can confirm the result of it! I have wasted tons of hours and the price of the boxed set on 10.1 and am backing out to 9.3 today!
Automount will NOT work in twm or fvwm2 by any method I've tried. It works SOMETIMES in kde by clicking on the removable device in "my computer" and then finding it in /media/.
Well, as I understand it, its not Novells fault. Talk to who ever makes the kernel decisions these days. You ALWAYS have the option of running autofs package which is still available, and still works. man autofs -- _____________________________________ John Andersen
On Sat, 2006-08-26 at 08:32 -0600, Tom Patton wrote:
On Sat, 2006-08-26 at 00:57 -0800, John Andersen wrote:
Automount will NOT work in twm or fvwm2 by any method I've tried. It works SOMETIMES in kde by clicking on the removable device in "my computer" and then finding it in /media/. My apologies to all if warranted, but my reply was the one-and-only one
that has ever been delayed. It arrived here at 1422, shortly after my cynical (and I certainly hope unwarranted) remark to John (over 6 hours late, and following my "test reply", which was immediate). I mis-spoke anyway, giving the impression of automounting, since John's email re the automounter triggered my reply. I have found NO way to mount, manually, user, root, entries in fstab, etc, either usbsticks or cd's. (Other than in KDE, that is.) This was an entirely virgin install out of the box on an athlon-2800 with a gig of ram. It is slow, unable to update, and fighting every step of the way. (I use Cinelerra a lot, which chokes terribly in KDE or Gnome) I'm not new to the list, nor to kernel.org et al. I'm cross-eyed reading and searching for all the needed (correct) answers to jump start this buggy. I don't blame any of you guys at all. But I stand with the concept that Novell is doing a huge dis-service to us all. Tom
On Sat, 2006-08-26 at 00:57 -0800, John Andersen wrote:
Have seen some chatter on this list that auto mounting was backed out of the kernel for some reason or other, and left to the distro or desktop providers.
Don't know If I got the details right.
A test reply...
On Sat, 2006-08-26 at 00:57 -0800, John Andersen wrote:
On Friday 25 August 2006 23:06, M Harris wrote:
On Thursday 24 August 2006 03:51, John Andersen wrote:
I just put an entry in fstab with the mount point and options I wanted, and allowed "user" to mount. Then I can open up KdiskFree and right click to mount/unmount.
Yeah, this works great. Do you happen to know what is going on with udev so that usb automounts are not working well? Do you know if someone is working on a cure..?
Thanks
Have seen some chatter on this list that auto mounting was backed out of the kernel for some reason or other, and left to the distro or desktop providers.
Don't know If I got the details right.
John, sorry for the reply to all...call me paranoid perhaps, but... I replied to the list early this morning to whit: ------------------------ I can't confirm your statement, but I can confirm the result of it! I have wasted tons of hours and the price of the boxed set on 10.1 and am backing out to 9.3 today! Automount will NOT work in twm or fvwm2 by any method I've tried. It works SOMETIMES in kde by clicking on the removable device in "my computer" and then finding it in /media/. It is sad when a reliable old friend turns into a drunken bum! NOVELL should immediately recall 10.1 and pull it from the store shelves. I can only imagine the damage this release is doing to the linux community. I might have to remove the SuSE Penguin Pin from my cowboy hat! Tom (every boxed set since 6.2...yep, I'm on a modem!) --------------------------- I later sent a "test reply" to the list. The test made it on the list, the above topic did not. It would appear that among all the other faults Novell has wrought, they are also filtering the list for the word RECALL... Whatever, Tom ex-10.1 user
On Saturday 26 August 2006 12:22, Tom Patton wrote:
It would appear that among all the other faults Novell has wrought, they are also filtering the list for the word RECALL...
Not! I suspect the problem is somewhere between the chair and the keyboard. ;-) I did get your original and did reply. -- _____________________________________ John Andersen
On Saturday 26 August 2006 16:22, Tom Patton wrote:
On Sat, 2006-08-26 at 00:57 -0800, John Andersen wrote:
On Friday 25 August 2006 23:06, M Harris wrote:
On Thursday 24 August 2006 03:51, John Andersen wrote:
I just put an entry in fstab with the mount point and options I wanted, and allowed "user" to mount. Then I can open up KdiskFree and right click to mount/unmount.
Yeah, this works great. Do you happen to know what is going on with udev so that usb automounts are not working well? Do you know if someone is working on a cure..?
Thanks
Have seen some chatter on this list that auto mounting was backed out of the kernel for some reason or other, and left to the distro or desktop providers.
Don't know If I got the details right.
John, sorry for the reply to all...call me paranoid perhaps, but...
I replied to the list early this morning to whit:
Yes, and I am sure most of us saw both this and your previous email. <yawn> <snip>
--------------------------- I later sent a "test reply" to the list. The test made it on the list, the above topic did not. It would appear that among all the other faults Novell has wrought, they are also filtering the list for the word RECALL...
And you're digging a deeper hole for yourself....
On Saturday 26 August 2006 22:22, Tom Patton wrote:
Automount will NOT work in twm or fvwm2 by any method I've tried. It works SOMETIMES in kde by clicking on the removable device in "my computer" and then finding it in /media/.
The subfs automounting was the source of many problems, and the mailing lists were full of advice to disable it. So it was removed in favour of a user space method, based on the ability of kde and gnome to handle media. It's just not possible to please everyone. But if you run twm or fvwm2, and then complain that you don't get things happening automatically, that's just plain weird. What's next? Booting to runlevel 3 and then complaining that X doesn't start automatically?
I later sent a "test reply" to the list. The test made it on the list, the above topic did not. It would appear that among all the other faults Novell has wrought, they are also filtering the list for the word RECALL...
I received your original copy, as well as John's reply to it. Be sure to adjust that tin foil hat
Whatever,
exactly
participants (6)
-
Anders Johansson -
Bruce Marshall -
John Andersen -
M Harris -
Mark Harris
-
Tom Patton