[opensuse-factory] Device already mounted or mountpoint busy error after some beta2 update, I guess
Hi, On a 10.3beta2 couple days ago my /dev/sdb1 was perfectly mountable. It was not in in fstab on purpose, mind you. Then something got updated by opensuse updater and sdb1 was not mountable anymore. mount /dev/sdb1 /mnt said "already mounted or /mnt busy" which was so not true. Errk. Googling I found people almost back in the last century debating this. The good advice pointed towards device-mapper. Turned out that device-mapper had grabbed sdb. So can _I_ do something with it too? Like use my hard disk? Not that I ever configured, invoked, worshipped device-mapper at all. dmsetup ls gave me 2 strings garbled together from device-mapper lingo and the name and serial number of my disk. Like linear-scsi-SATA_ST3500630A_serial_number (253, 0) and linear-scsi-SATA_ST3500630A_serial_number_part1 (253, 1) dmsetup remove linear-scsi-SATA_ST3500630A_serial_number_part1 and dmsetup remove linear-scsi-SATA_ST3500630A_serial_number and mount /dev/sdb1 /mnt and things are back the way they were. Am I missing something deep? Plus: Apart from police people who in this whole wide world thinks having serial numbers of your disks all over the system was cool? Could that be, like, an _option_ please? My face turns all yellow when I look at /etc/fstab these days. Can someone tell me the advantages of this? Thanks, and thank you for a pretty amazing beta2. Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Saturday 01 September 2007 18:30, Wolfgang Woehl wrote:
Hi,
On a 10.3beta2 couple days ago my /dev/sdb1 was perfectly mountable. It was not in in fstab on purpose, mind you. Then something got updated by opensuse updater and sdb1 was not mountable anymore.
mount /dev/sdb1 /mnt said "already mounted or /mnt busy" which was so not true. Errk.
Googling I found people almost back in the last century debating this. The good advice pointed towards device-mapper.
Turned out that device-mapper had grabbed sdb. So can _I_ do something with it too? Like use my hard disk? Not that I ever configured, invoked, worshipped device-mapper at all.
dmsetup ls gave me 2 strings garbled together from device-mapper lingo and the name and serial number of my disk. Like linear-scsi-SATA_ST3500630A_serial_number (253, 0) and linear-scsi-SATA_ST3500630A_serial_number_part1 (253, 1)
dmsetup remove linear-scsi-SATA_ST3500630A_serial_number_part1 and dmsetup remove linear-scsi-SATA_ST3500630A_serial_number and mount /dev/sdb1 /mnt and things are back the way they were.
Am I missing something deep? Plus: Apart from police people who in this whole wide world thinks having serial numbers of your disks all over the system was cool? Could that be, like, an _option_ please? My face turns all yellow when I look at /etc/fstab these days. Can someone tell me the advantages of this?
Thanks, and thank you for a pretty amazing beta2. Wolfgang
It seems to be the same as this: https://bugzilla.novell.com/show_bug.cgi?id=307044 but looking another similar bug, leads to: https://bugzilla.novell.com/show_bug.cgi?id=302422 origin. -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Sonntag, 2. September 2007 Rajko M.:
On Saturday 01 September 2007 18:30, Wolfgang Woehl wrote:
Hi,
On a 10.3beta2 couple days ago my /dev/sdb1 was perfectly mountable. It was not in in fstab on purpose, mind you. Then something got updated by opensuse updater and sdb1 was not mountable anymore.
mount /dev/sdb1 /mnt said "already mounted or /mnt busy" which was so not true. Errk.
Googling I found people almost back in the last century debating this. The good advice pointed towards device-mapper.
Turned out that device-mapper had grabbed sdb. So can _I_ do something with it too? Like use my hard disk? Not that I ever configured, invoked, worshipped device-mapper at all.
dmsetup ls gave me 2 strings garbled together from device-mapper lingo and the name and serial number of my disk. Like linear-scsi-SATA_ST3500630A_serial_number (253, 0) and linear-scsi-SATA_ST3500630A_serial_number_part1 (253, 1)
dmsetup remove linear-scsi-SATA_ST3500630A_serial_number_part1 and dmsetup remove linear-scsi-SATA_ST3500630A_serial_number and mount /dev/sdb1 /mnt and things are back the way they were.
Am I missing something deep? Plus: Apart from police people who in this whole wide world thinks having serial numbers of your disks all over the system was cool? Could that be, like, an _option_ please? My face turns all yellow when I look at /etc/fstab these days. Can someone tell me the advantages of this?
Thanks, and thank you for a pretty amazing beta2. Wolfgang
It seems to be the same as this: https://bugzilla.novell.com/show_bug.cgi?id=307044 but looking another similar bug, leads to: https://bugzilla.novell.com/show_bug.cgi?id=302422 origin.
Ok, https://bugzilla.novell.com/show_bug.cgi?id=302422 has " Comment #6 From Hannes Reinecke 2007-08-29 05:12:02 MST ------- That's the dm-linear feature interfering. Please remove /etc/udev/rules.d/62-dm_linear.rules, and run dmsetup remove_all " I wonder why did the device-mapper start to grab (in my case) sdb in the first place? What would the "feature" be? I've looked at /etc/udev/rules.d/60-persistent-storage.rules and I wonder: Is that the only/the right spot to get rid of serial numbers? Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 02 September 2007 07:42, Wolfgang Woehl wrote:
I've looked at /etc/udev/rules.d/60-persistent-storage.rules and I wonder: Is that the only/the right spot to get rid of serial numbers?
I guess it is, but you can also use YaST Partitioner (command 'yast2 disk'). Select partition that you want to change, click on Edit button. In window that pops up click on 'Fstab Options' and in new window you can tell system to mount volume in different way. Be aware that abandoning mount by device path was forced by increasing number of devices that can be mounted in different order on each boot which results in different path. All SATA and USB devices are prone to that. In order to access them you have to know where they are located, with different path each time you have to find something that doesn't change. Serial numbers are safe bet, they will be the same even across multiple installations, or large systems with whole a lot of hard disks. Lables would be too, but than you risk to create system that is today fine, but with increase in number of devices can run out of available labels in the future. The present system will hardly hit the limit any soon. -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Sonntag, 2. September 2007 Rajko M.:
On Sunday 02 September 2007 07:42, Wolfgang Woehl wrote:
I've looked at /etc/udev/rules.d/60-persistent-storage.rules and I wonder: Is that the only/the right spot to get rid of serial numbers?
I guess it is, but you can also use YaST Partitioner (command 'yast2 disk'). Select partition that you want to change, click on Edit button. In window that pops up click on 'Fstab Options' and in new window you can tell system to mount volume in different way.
Rajko, thanks for the hint.
Be aware that abandoning mount by device path was forced by increasing number of devices that can be mounted in different order on each boot which results in different path. All SATA and USB devices are prone to that.
Internal sata devices could be mounted in different order each boot?
In order to access them you have to know where they are located, with different path each time you have to find something that doesn't change. Serial numbers are safe bet, they will be the same even across multiple installations, or large systems with whole a lot of hard disks. Lables would be too, but than you risk to create system that is today fine, but with increase in number of devices can run out of available labels in the future. The present system will hardly hit the limit any soon.
Ok, I've read up a bit on udev and am aware now of the possibilities. But I'm not running a serverfarm here. I change disks once in 2 years maybe. Anyway, if all this worked I couldn't care less, except for the serial number notion (which i realize is not trivial to get rid of if you want the above safety net). But my initial posting was about an internal device disappearing from the usual mount infrastructure. Thank you again for your advice, Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 02 September 2007 16:15, Wolfgang Woehl wrote: ...
Be aware that abandoning mount by device path was forced by increasing number of devices that can be mounted in different order on each boot which results in different path. All SATA and USB devices are prone to that.
Internal sata devices could be mounted in different order each boot?
My bad :-( SATA is not in the same bag as USB. SATA device placement can be changed on hardware changes. Adding or removing PATA drive will automatically change SATA placement reported by BIOS and goof mounting if it is defined by device path. This is not a big problem if you know that it exists, but there is no problem if you use present schema or mounting by label (haven't checked the rest).
In order to access them you have to know where they are located, with different path each time you have to find something that doesn't change. Serial numbers are safe bet, they will be the same even across multiple installations, or large systems with whole a lot of hard disks. Lables would be too, but than you risk to create system that is today fine, but with increase in number of devices can run out of available labels in the future. The present system will hardly hit the limit any soon.
Ok, I've read up a bit on udev and am aware now of the possibilities. But I'm not running a serverfarm here.
The openSUSE is created for many different users, and present schema works for all of them. Besides if you replace disk with present schema mount will report error even if disk is formatted ie. mountable, but content doesn't fit in your system. This will prompt you to update configuration. Mount by path on the other hand can happily accept that disk which can lead to problems later. The label system can do the same if label is the same.
I change disks once in 2 years maybe.
For most desktop users this is not an issue, except the case with SATA drives that happen not so often.
Anyway, if all this worked I couldn't care less, except for the serial number notion (which i realize is not trivial to get rid of if you want the above safety net).
If disk serial number is problem as privacy concern, than forget it. The Ethernet card has unique number, motherboard, if computer is brand name, has another one, than IP address, and more can be used to identify person. Of course not by everyone, but privacy in the Internet is illusion. Those that sell privacy services with very broad claims of protection count on peoples lack of knowledge. "Browse Internet anonymously" is one of slogans I can recall. They protect to some extent, but far from total.
But my initial posting was about an internal device disappearing from the usual mount infrastructure.
It is solved.
Thank you again for your advice, Wolfgang
Have fun! -- Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Montag, 3. September 2007 Rajko M.:
On Sunday 02 September 2007 16:15, Wolfgang Woehl wrote:
But my initial posting was about an internal device disappearing from the usual mount infrastructure.
It is solved.
I still don't know why the internal device got grabbed by device-mapper. I suspect not having it in fstab (which was on purpose) led to it. Although I never conciously configured or invoked dm-mechanisms.
Have fun!
I'm having more fun than I expected really :} Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dienstag, 4. September 2007 Wolfgang Woehl:
Montag, 3. September 2007 Rajko M.:
On Sunday 02 September 2007 16:15, Wolfgang Woehl wrote:
But my initial posting was about an internal device disappearing from the usual mount infrastructure.
It is solved.
I still don't know why the internal device got grabbed by device-mapper. I suspect not having it in fstab (which was on purpose) led to it. Although I never conciously configured or invoked dm-mechanisms.
Plus, I realize this just now, plugging in a usb mass-storage device makes kde pop up "open in window?" which it tries but fails to show the content of because device-mapper grabbed it. Is this the default behaviour? It can't be. Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 04 September 2007 15:50, Wolfgang Woehl wrote:
Dienstag, 4. September 2007 Wolfgang Woehl:
Montag, 3. September 2007 Rajko M.:
On Sunday 02 September 2007 16:15, Wolfgang Woehl wrote:
But my initial posting was about an internal device disappearing from the usual mount infrastructure.
It is solved.
I still don't know why the internal device got grabbed by device-mapper. I suspect not having it in fstab (which was on purpose) led to it. Although I never conciously configured or invoked dm-mechanisms.
Plus, I realize this just now, plugging in a usb mass-storage device makes kde pop up "open in window?" which it tries but fails to show the content of because device-mapper grabbed it. Is this the default behaviour? It can't be.
I'm pretty sure it is not. Is this happening after deleting /etc/udev/rules.d/62-dm_linear.rules and dmsetup remove_all -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Mittwoch, 5. September 2007 Rajko M.:
On Tuesday 04 September 2007 15:50, Wolfgang Woehl wrote:
Plus, I realize this just now, plugging in a usb mass-storage device makes kde pop up "open in window?" which it tries but fails to show the content of because device-mapper grabbed it. Is this the default behaviour? It can't be.
I'm pretty sure it is not. Is this happening after deleting /etc/udev/rules.d/62-dm_linear.rules and dmsetup remove_all
No. And again: I did not configure or invoke device-mapper explivitly. This is a non-tweaked 10.3beta2 install and the mount behaviour changed a day after the install with -- i guess -- an automatic update. Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday, 5. September 2007, Wolfgang Woehl wrote:
No. And again: I did not configure or invoke device-mapper explivitly. This is a non-tweaked 10.3beta2 install and the mount behaviour changed a day after the install with -- i guess -- an automatic update.
The bug is tracked in #302422 and its marked as fixed for Beta3. please try there again. Thanks, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Mittwoch, 5. September 2007 Dirk Mueller:
On Wednesday, 5. September 2007, Wolfgang Woehl wrote:
No. And again: I did not configure or invoke device-mapper explivitly. This is a non-tweaked 10.3beta2 install and the mount behaviour changed a day after the install with -- i guess -- an automatic update.
The bug is tracked in #302422 and its marked as fixed for Beta3. please try there again.
Thank you. Sorry for not reading through 302422 up to the multipath-tools and kpartx change comment. How can i "upgrade" to beta3? Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday 05 September 2007 09:25:10 am Wolfgang Woehl wrote:
Mittwoch, 5. September 2007 Dirk Mueller:
On Wednesday, 5. September 2007, Wolfgang Woehl wrote:
No. And again: I did not configure or invoke device-mapper explivitly. This is a non-tweaked 10.3beta2 install and the mount behaviour changed a day after the install with -- i guess -- an automatic update.
The bug is tracked in #302422 and its marked as fixed for Beta3. please try there again.
Thank you. Sorry for not reading through 302422 up to the multipath-tools and kpartx change comment.
How can i "upgrade" to beta3? Wolfgang
1) Download Beta 3 CD/DVD and update. 2) Using YaST module Update to Factory. I guess it is already frozen in Beta3 Status. This is how I'm going to update. -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Donnerstag, 6. September 2007 Rajko M.:
On Wednesday 05 September 2007 09:25:10 am Wolfgang Woehl wrote:
How can i "upgrade" to beta3? Wolfgang
1) Download Beta 3 CD/DVD and update. 2) Using YaST module Update to Factory. I guess it is already frozen in Beta3 Status. This is how I'm going to update.
Raiko, thanks for your patience, Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Dirk Mueller -
Rajko M. -
Wolfgang Woehl