LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 03-29-2013, 01:01 PM   #1
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu, PartedMagic
Posts: 68

Rep: Reputation: 7
mate/caja : mount -oloop / umount problems


Current64 - with and without multilib - up to date.

When I mount a UDF ISO like:
# mount -oloop /E/Lindoc/Rescue/rescue-4.7.3f.iso /cdrom
I get an error popup reading:
> Unable to mount Rescue-4.7.3f
> Device /dev/loop0 is already mounted at '/cdrom'

The ISO however is mounted. There is nothing interesting in the /var/log/messages file other than the usual UDF blurp.
When I then unmount the ISO:
# umount /cdrom
I get an error popup reading:
> Unable to mount Volume
> Operation was cancelled

Strangely enough the messages file now has two squashfs errors ...

When I mount a plain iso9660 ISO I do not get an error popup, nor is there anything in the messages.
Unmounting however gives the same error popup:
> Unable to mount Volume
> Operation was cancelled

In the messages there is now an iso9660 error message.

One or two times I noticed that the ISO was also mounted in /run/media !???!

I see these symptoms with current64 with and without multilib, but not with current32.
I do not know when these symptoms started. It must have been at least a week and possibly even more that I mounted an ISO with my current64's.
Did I pick up something "bad" recently, or are there other users with the same symptoms?

Last edited by burdi01; 04-02-2013 at 03:17 AM.
 
Old 03-29-2013, 06:39 PM   #2
Kustom42
Senior Member
 
Registered: Mar 2012
Distribution: Red Hat
Posts: 1,563

Rep: Reputation: 410Reputation: 410Reputation: 410Reputation: 410Reputation: 410
Incorrect info - Deleted. Didnt realize the distro forum I was in sorry.

Last edited by Kustom42; 03-29-2013 at 06:41 PM.
 
Old 03-29-2013, 06:51 PM   #3
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 145Reputation: 145
man mount and search for "auto type".
 
Old 03-29-2013, 06:57 PM   #4
Kustom42
Senior Member
 
Registered: Mar 2012
Distribution: Red Hat
Posts: 1,563

Rep: Reputation: 410Reputation: 410Reputation: 410Reputation: 410Reputation: 410
Quote:
Originally Posted by guanx View Post
man mount and search for "auto type".
Can you break this down some more? I am curious. I know that /mnt/cdrom is the auto mount location for cdroms in slackware. But I am not a slackware expert.


Try doing an

Code:
losetup /dev/loop0
It should give you some info as to what loop0 is doing.
 
Old 03-29-2013, 09:10 PM   #5
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 145Reputation: 145
Quote:
Originally Posted by Kustom42 View Post
Can you break this down some more? I am curious. I know that /mnt/cdrom is the auto mount location for cdroms in slackware. But I am not a slackware expert.
It has nothing distribution specific. When no fstype is specified, mount tries to guess it (man mount and search for auto type).
The guess may well miss, and one or more failure records will be left in dmesg.
 
Old 03-30-2013, 06:31 AM   #6
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu, PartedMagic
Posts: 68

Original Poster
Rep: Reputation: 7
Things get even weirder: The popup on the mount occurs less consistently than it did yesterday. But the popup on the umount remains as was.

The remarks on type auto are correct, however stating "-tudf" or "-tiso9660" makes no difference at all.
By pure chance I noticed that the "-oloop" is no longer necessary -- I am sure it was necessary in the past.
"Losetup /dev/loop0" or "mount" (without arguments) do not show anything out of the ordinary.

I cannot help feeling that something is interfering with the mount. But I do not have an automounter running -- actually I do not even have autofs installed.
Based on the fact that I do not remember the symptoms from say a week (or two) I would say that something in the recent updates is causing things. Udisk (updated Mar 27) and udisk2 (updated Mar 23) seem good candidates.

Before diving deeper however it might be interesting to know whether or not there are other users seeing the symptoms. Any ISO will do, even the slackware-14.0-install-dvd.iso one.

Last edited by burdi01; 03-30-2013 at 06:43 AM.
 
Old 03-30-2013, 07:23 AM   #7
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 145Reputation: 145
Quote:
Originally Posted by burdi01 View Post
...
I cannot help feeling that something is interfering with the mount. But I do not have an automounter running -- actually I do not even have autofs installed.
...
Are you using any GUI desktop environment or something alike?
 
Old 03-30-2013, 11:06 AM   #8
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu, PartedMagic
Posts: 68

Original Poster
Rep: Reputation: 7
Yes: Xfce 4.10 from Slackware with the "missing" packages added from Salix and Mint. I use Thunar to manage the desktop, Caja ("nautilus") as file manager and Pluma ("gedit") as editor. Both Thunar's and Caja's media handling are disabled.
 
Old 03-31-2013, 10:27 AM   #9
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu, PartedMagic
Posts: 68

Original Poster
Rep: Reputation: 7
Downgrading udisks 1.0.4/2 -> 1.0.4/1 and udisks2 2.1.0/1 -> 1.98.0/1 had no other effect than that the umount message now reads:
> Unable to mount Volume
> The given volume was not found


However, when unmounting the Slackware64 DVD I once got the much more detailed error popup as attached. It (re-)highlights two points:
1) The message when unmounting is about a failed mount;
2) There is the "/run/media" again, and I have idea where it comes from.
The syslog message referred to reads:
Mar 30 17:27:28 riposo kernel: isofs_fill_super: bread failed, dev=loop0, iso_blknum=16, block=32

Actually I noticed that the /var/log/run -> /run symlink that I expected to be there was no longer. Recreating that symlink had no effect on the problem at hand.
Attached Images
File Type: png Screenshot.png (114.3 KB, 8 views)

Last edited by burdi01; 03-31-2013 at 10:30 AM.
 
Old 03-31-2013, 11:36 AM   #10
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 145Reputation: 145
Quote:
Originally Posted by burdi01 View Post
Yes: Xfce 4.10 from Slackware with the "missing" packages added from Salix and Mint. I use Thunar to manage the desktop, Caja ("nautilus") as file manager and Pluma ("gedit") as editor. Both Thunar's and Caja's media handling are disabled.
I bet it takes forever for you to find anyone who happens to mix the same packages from the same distributions :-D
 
Old 03-31-2013, 11:50 AM   #11
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu, PartedMagic
Posts: 68

Original Poster
Rep: Reputation: 7
Exclamation

I revived my Slackware32 installation from a backup of Mar 23 early in the morning and verified that the "mount -oloop / umount" problem was not present.
I then ran "slackpkg update ; slackpkg upgrade-all" (Sat Mar 23 22:49:52 UTC 2013 through Fri Mar 29 00:27:36 UTC 2013 : 80 upgrades, 5 additions) and found that the "mount -oloop / umount" problem *is* present now.

So the likelyhood that other current users have the same symptoms is rather high. Remains the question why I am the only one reporting them - or is no one mounting ISOs?
 
Old 03-31-2013, 05:43 PM   #12
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware-14.0 on a Lenovo T61 6457-4XG
Posts: 3,640

Rep: Reputation: 827Reputation: 827Reputation: 827Reputation: 827Reputation: 827Reputation: 827Reputation: 827
I'd try to do that in fluxbox instead of xfce and see what happens. IIRC xfce sets a /var/run... mount point.

EDIT Better type - o loop than -oloop even if the latter works.

Last edited by Didier Spaier; 04-01-2013 at 01:17 AM.
 
Old 03-31-2013, 07:49 PM   #13
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 145Reputation: 145
Quote:
Originally Posted by burdi01 View Post
I revived my Slackware32 installation from a backup of Mar 23 early in the morning and verified that the "mount -oloop / umount" problem was not present.
I then ran "slackpkg update ; slackpkg upgrade-all" (Sat Mar 23 22:49:52 UTC 2013 through Fri Mar 29 00:27:36 UTC 2013 : 80 upgrades, 5 additions) and found that the "mount -oloop / umount" problem *is* present now.

So the likelyhood that other current users have the same symptoms is rather high. Remains the question why I am the only one reporting them - or is no one mounting ISOs?
So what's meaning of "with the \"missing\" packages added from Salix and Mint"?
 
Old 03-31-2013, 08:44 PM   #14
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.0, 13.1, 13.37, 14.0, 64-14, -current
Posts: 1,507

Rep: Reputation: 499Reputation: 499Reputation: 499Reputation: 499Reputation: 499
Quote:
Originally Posted by burdi01 View Post
So the likelyhood that other current users have the same symptoms is rather high. Remains the question why I am the only one reporting them - or is no one mounting ISOs?
I am running -current (32 bit) and have mounted/umounted ISOs several times today with no problem. I am using Fluxbox.

But like guanx, I am curious what you meant by "missing packages".
 
Old 04-01-2013, 04:18 AM   #15
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu, PartedMagic
Posts: 68

Original Poster
Rep: Reputation: 7
I boot to the console (runlevel 3). From there "startx" brings me to twm, and "xfce" (alias for "xinit /etc/X11/xinit/xinitrc.xfce") to xfce.

The fluxbox tip made me test things on the console and under twm. And lo and behold! the problem did not occur there. I then tested under xfce and the problem was back.

About the missing packages: I found the xfce implementation as provided by the xap disk set rather incomplete - e.g. no editor, no archive manager, no xfburn. Following are the packages and their dependencies from salix (-?gv builds) and mint (-1mint build extracted from a mint live CD):
Code:
asunder-2.2-x86_64-1gv.txz
galculator-1.3.4-x86_64-1gv.txz
gst-plugins-bad-0.10.23-x86_64-1gv.txz
gst-plugins-ugly-0.10.19-x86_64-1gv.txz
gtksourceview-2.10.5-x86_64-1gv.txz
ktsuss-2-x86_64-1gv.txz
leafpad-0.8.18.1-x86_64-1gv.txz
libburn-1.2.4-x86_64-1gv.txz
libevent-2.0.19-x86_64-2gv.txz
libgtop-2.28.4-x86_64-1gv.txz
libisofs-1.2.4-x86_64-1gv.txz
libmatekeyring-1.4.0-x86_64-1gv.txz
libunique-1.1.6-x86_64-2gv.txz
mate-conf-1.4.0-x86_64-1gv.txz
mate-corba-1.4.0-x86_64-1gv.txz
mate-desktop-1.4.2-x86_64-1gv.txz
mate-document-viewer-1.4.0-x86_64-1gv.txz
mate-file-archiver-1.4.1-x86_64-1gv.txz
mate-file-manager-1.4.0-x86_64-1gv.txz
mate-utils-1.4.0-x86_64-1gv.txz
p7zip-9.20.1-x86_64-1gv.txz
parole-0.3.0.3-x86_64-1gv.txz
pluma-1.4.0-x86_64-1mint.txz
salixtools-1.6.1-noarch-1gv.txz
salixtools-gtk-1.3.0-noarch-1gv.txz
simple-scan-2.32.0.2-x86_64-1gv.txz
squashfs-tools-4.2-x86_64-1cp.txz
transmission-2.60-x86_64-2gv.txz
viewnior-1.3-x86_64-1gv.txz
xfburn-0.4.3-x86_64-2gv.txz
Now I will have to figure out whether the problem is caused by xfce packages from Slackware and/or Salix ...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Execute command on mount and integrate with gnome-mount / umount Peter Rhone Linux - Newbie 4 11-18-2008 05:28 AM
util-linux-2.12r error on 'make -C mount mount umount' james penguin Linux From Scratch 2 08-28-2006 11:55 PM
mount / umount problems d1l2w3 Linux - Hardware 6 03-14-2005 04:23 PM
mount/umount devit Linux - General 4 02-19-2004 12:37 PM
Serious mount/umount problems... Veratien Linux - Software 8 03-23-2003 05:05 PM


All times are GMT -5. The time now is 11:23 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration