RE: how to change hotplug mount point?
Hi experts, Could anyone suggest how to change 9.1 hotplug mount point for memory stick from /media/usb-storage-3563BF09143714061204:0:0:0p1 to something like /media/usbflash? I was trying to use symbolic link but that did breaks automount as once the memory stick was removed, symlink stayed active and next time memory stick was plugged in it did not get mounted at all. Thx, Martin __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail
Martin, On Friday 07 January 2005 20:23, Martin wrote:
Hi experts,
Could anyone suggest how to change 9.1 hotplug mount point for memory stick from /media/usb-storage-3563BF09143714061204:0:0:0p1 to something like /media/usbflash?
I was trying to use symbolic link but that did breaks automount as once the memory stick was removed, symlink stayed active and next time memory stick was plugged in it did not get mounted at all.
That's odd. I keep symlinks in / for each of the removable media devices in my system, which include one flash RAM stick. It's /media mount point is similar to the one you report and is the same every time the device is mounted, naturally, since otherwise the technique would not really work. What you say really doesn't make sense to me, since a symbolic link has no effect on its target. Are you sure you got the link pointed in the right direction? The "ln" command would be "ln -s /media/... shortName", not the reverse.
Thx, Martin
Randall Schulz
--- Randall R Schulz
Martin,
That's odd. I keep symlinks in / for each of the removable media devices in my system, which include one flash RAM stick. It's /media mount point is similar to the one you report and is the same every time the device is mounted, naturally, since otherwise the technique would not really work.
What you say really doesn't make sense to me, since a symbolic link has no effect on its target. Are you sure you got the link pointed in the right direction? The "ln" command would be "ln -s /media/... shortName", not the reverse.
Randall, this is what I did: 1. insert memory stick 2. cd /home/user/Documents 3. created sym link ln -s /media/usb-storage<bla bla> ./usbflash 4. opened up konqueror in /home/user/Documents/usbflash 5. closed konqueror 6. removed memory stick 7. got the error in /var/log/messages Jan 7 21:53:58 tp600e /etc/hotplug/block.agent[4779]: umount: /media/usb-storage-3563BF09143714061204:0:0:0p1: device is busy Jan 7 21:53:58 tp600e /etc/hotplug/block.agent[4779]: umount: /media/usb-storage-3563BF09143714061204:0:0:0p1: device is busy 8. inserted memory stick back 9. got the following msgs after opening konqueror as above Jan 7 21:58:33 tp600e /etc/hotplug/block.agent[5219]: new block device /block/sdb/sdb1 Jan 7 21:58:42 tp600e /etc/hotplug/block.agent[5219]: mount by-path/usb-storage-3563BF09143714061204:0:0:0p1 Jan 7 21:59:00 tp600e /USR/SBIN/CRON[5499]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 7 21:59:03 tp600e kernel: scsi0 (0:0): rejecting I/O to dead device Jan 7 21:59:03 tp600e kernel: FAT: Directory bread(block 497) failed Jan 7 21:59:03 tp600e kernel: scsi0 (0:0): rejecting I/O to dead device Jan 7 21:59:03 tp600e kernel: FAT: Directory bread(block 498) failed Jan 7 21:59:03 tp600e kernel: scsi0 (0:0): rejecting I/O to dead device Jan 7 21:59:03 tp600e kernel: FAT: Directory bread(block 499) failed Any idea why this is happening? Thx, Martin __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail
Martin, On Friday 07 January 2005 22:05, Martin wrote:
--- Randall R Schulz
wrote: Martin,
...
Randall,
this is what I did:
For starters, the symptoms you see have nothing to do with the use of symbolic links. I believe the real problem is that closing the Konqueror window does not actually terminate the Konqueror process. It has a feature designed to make its windows open faster. It keeps one or more instances of the Konqueror code running so that when the user asks to open Konqueror, all (or most of) the initializations it must perform are already complete. This has a side-effect that various file system resources can remain "in use" (in this case, it probably means that the Konqueror process has a directory on that device as a current directory or has one of those directories open for reading in order to display a directory listing). To confirm that this is what's happening and to prevent it from happening in the future, you can configure Konqueror not to perform this optimization: Konqueror -> Settings (Menu) -> Configure Konqueror -> Performance (last category in the list on the left) In the "Preloading" section set the "Maximum number of instances kept preloaded" to zero. Let me know if doing this solves the problem. Randall Schulz
1. insert memory stick 2. cd /home/user/Documents 3. created sym link
ln -s /media/usb-storage<bla bla> ./usbflash
4. opened up konqueror in /home/user/Documents/usbflash 5. closed konqueror 6. removed memory stick 7. got the error in /var/log/messages
Jan 7 21:53:58 tp600e /etc/hotplug/block.agent[4779]: umount: /media/usb-storage-3563BF09143714061204:0:0:0p1: device is busy Jan 7 21:53:58 tp600e /etc/hotplug/block.agent[4779]: umount: /media/usb-storage-3563BF09143714061204:0:0:0p1: device is busy
8. inserted memory stick back 9. got the following msgs after opening konqueror as above
Jan 7 21:58:33 tp600e /etc/hotplug/block.agent[5219]: new block device /block/sdb/sdb1 Jan 7 21:58:42 tp600e /etc/hotplug/block.agent[5219]: mount by-path/usb-storage-3563BF09143714061204:0:0:0p1 Jan 7 21:59:00 tp600e /USR/SBIN/CRON[5499]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Jan 7 21:59:03 tp600e kernel: scsi0 (0:0): rejecting I/O to dead device Jan 7 21:59:03 tp600e kernel: FAT: Directory bread(block 497) failed Jan 7 21:59:03 tp600e kernel: scsi0 (0:0): rejecting I/O to dead device Jan 7 21:59:03 tp600e kernel: FAT: Directory bread(block 498) failed Jan 7 21:59:03 tp600e kernel: scsi0 (0:0): rejecting I/O to dead device Jan 7 21:59:03 tp600e kernel: FAT: Directory bread(block 499) failed
Any idea why this is happening?
Thx, Martin
To confirm that this is what's happening and to prevent it from happening in the future, you can configure Konqueror not to perform this optimization:
Konqueror -> Settings (Menu) -> Configure Konqueror -> Performance (last category in the list on the left)
In the "Preloading" section set the "Maximum number of instances kept preloaded" to zero.
Let me know if doing this solves the problem.
Randall, I was hopefull this would be it but unfortunatelly it didn't help at all. Repeating the same steps as before I end up getting the same error messages in /var/log/messages. I could not find any 'safe' method to get a rid of it but reloading the laptop. If this was for me I would not care but it is for my mother and she wanted to have memory stick mounted (she does not know anything about mounting ;) as a folder in her home directory. The only way for her to transfer files back and forth is to use konqueror. I was also thinking to upgrade to 9.2 but not sure this would be safe and helped at all. Martin __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail
On Saturday 08 Jan 2005 06:05 am, Martin wrote: <SNIP>
this is what I did:
1. insert memory stick 2. cd /home/user/Documents 3. created sym link
ln -s /media/usb-storage<bla bla> ./usbflash
4. opened up konqueror in /home/user/Documents/usbflash 5. closed konqueror 6. removed memory stick
How long did you leave between closing Konq and removing the stick? You need to leave enough time for it to auto-unmount. I've dealt with this problem by disabling subfs and putting a device icon on the desktop for people who can't cope with mounting things. Dylan -- "I see your Schwartz is as big as mine" -Dark Helmet
participants (3)
-
Dylan
-
Martin
-
Randall R Schulz