Mailinglist Archive: opensuse-factory (824 mails)
| < Previous | Next > |
[opensuse-factory] Device already mounted or mountpoint busy error after some beta2 update, I guess
- From: Wolfgang Woehl <tito@xxxxxxxxxx>
- Date: Sun, 2 Sep 2007 01:30:09 +0200
- Message-id: <200709020130.09902.tito@xxxxxxxxxx>
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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |