TW won't let me mount by device-name
After "fdisk -l" to validate that my booting drive is in fact /dev/sda mount /dev/sda8 /0/sa08 because I want to work in partition 8 What I get in response is ========================================================== # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy. dmesg(1) may have more information after failed mount system call. ========================================================== Why is TW not letting me mount by confirmed device-name? It seem to me that I once removed some package that fixed the issue but I don't remember what that package was, and now it's back to square one. Any other fix? I used disk-labels for a while too but got into trouble with those being used together with uuids :-(
Ben T. Fender composed on 2024-01-24 21:53 (UTC-0500):
After "fdisk -l" to validate that my booting drive is in fact /dev/sda
mount /dev/sda8 /0/sa08
because I want to work in partition 8
What I get in response is ========================================================== # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call. ==========================================================
Why is TW not letting me mount by confirmed device-name?
It seem to me that I once removed some package that fixed the issue but I don't remember what that package was, and now it's back to square one.
Any other fix?
What do mount | egrep 'sda|sa' and df report?
I used disk-labels for a while too but got into trouble with those being used together with uuids :-(
I can only imagine disk labels causing trouble if you choose your disk labels unwisely. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Wed, 24 Jan 2024 22:07:52 -0500 Felix Miata <mrmazda@earthlink.net> :
Ben T. Fender composed on 2024-01-24 21:53 (UTC-0500):
After "fdisk -l" to validate that my booting drive is in fact /dev/sda
mount /dev/sda8 /0/sa08
because I want to work in partition 8
What I get in response is ========================================================== # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call. ==========================================================
Why is TW not letting me mount by confirmed device-name?
It seem to me that I once removed some package that fixed the issue but I don't remember what that package was, and now it's back to square one.
Any other fix?
What do mount | egrep 'sda|sa' and df report?
https://paste.opensuse.org/pastes/10941b7550b2
I used disk-labels for a while too but got into trouble with those being used together with uuids :-(
I can only imagine disk labels causing trouble if you choose your disk labels unwisely.
I hardly ever used labels before, did a few of them but after dd-ing one of those partitions I ended up with two partitions with a different uuid but the same label cause I edited the uuid's only in /etc/stab. It was entirely my fault, 10 fingers up my stack all the way to my armpit again. -- Fender have made the world's greatest electric guitars for 80 years now, but they've not yet managed a Stratovarius.
Ben T. Fender composed on 2024-01-25 00:38 (UTC-0500):
Wed, 24 Jan 2024 22:07:52 -0500 Felix Miata composed :
What do mount | egrep 'sda|sa' and df report?
https://paste.opensuse.org/pastes/10941b7550b2 # mount | egrep 'sda|sa' /0/adat # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 102626592 28836592 68530752 30% / devtmpfs 4096 0 4096 0% /dev tmpfs 8174936 0 8174936 0% /dev/shm tmpfs 3269976 1824 3268152 1% /run tmpfs 8174940 4 8174936 1% /tmp /dev/mapper/WDC_WD20EZBX-00AYRA0_WD-WXH2A31NP1A7-part1 1921724676 1091479568 732553048 60% /0/adat tmpfs 1634984 212 1634772 1% /run/user/1003
Those didn't produce expected output, because your system is employing dev-mapper, which I have no positive experience dealing with. I'd need fdisk -l output to try to make much sense out of that output in terms of why I asked what I asked. Instead of mount | egrep 'sda|sa', do: df --exclude-type=tmpfs --exclude-type=devtmpfs --exclude-type=cgroup --exclude-type=efivarfs Both should be short enough to be able to paste instead of susepaste. Bedtime imminent. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Thu, 25 Jan 2024 01:26:05 -0500 Felix Miata <mrmazda@earthlink.net> :
Ben T. Fender composed on 2024-01-25 00:38 (UTC-0500):
Wed, 24 Jan 2024 22:07:52 -0500 Felix Miata composed :
What do mount | egrep 'sda|sa' and df report?
https://paste.opensuse.org/pastes/10941b7550b2 # mount | egrep 'sda|sa' /0/adat # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 102626592 28836592 68530752 30% / devtmpfs 4096 0 4096 0% /dev tmpfs 8174936 0 8174936 0% /dev/shm tmpfs 3269976 1824 3268152 1% /run tmpfs 8174940 4 8174936 1% /tmp /dev/mapper/WDC_WD20EZBX-00AYRA0_WD-WXH2A31NP1A7-part1 1921724676 1091479568 732553048 60% /0/adat tmpfs 1634984 212 1634772 1% /run/user/1003
Those didn't produce expected output, because your system is employing dev-mapper, which I have no positive experience dealing with. I'd need fdisk -l output to try to make much sense out of that output in terms of why I asked what I asked.
Instead of mount | egrep 'sda|sa', do:
df --exclude-type=tmpfs --exclude-type=devtmpfs --exclude-type=cgroup --exclude-type=efivarfs
Both should be short enough to be able to paste instead of susepaste.
Bedtime imminent.
It's 07:40 here, most of yesterday's issues forgotten because at my age memory is still as sharp as a razor blade but no wider than it's edge. The bonus being 100 new movies every day! Yesterday I pasted not because it was long but because the lines were. # df --exclude-type=tmpfs --exclude-type=devtmpfs --exclude-type=cgroup --exclude-type=efivarfs Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 102626592 28832008 68535336 30% / /dev/mapper/WDC_WD20EZBX-00AYRA0_WD-WXH2A31NP1A7-part1 1921724676 1091363016 732669600 60% /0/adat And dev-mapper, yeah, I think THAT's the one I deleted the other time. -- People used to more polite when dueling was legal.
-- Evolution as taught in public schools is, like religion, based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
On 2024-01-25 03:53, Ben T. Fender wrote:
After "fdisk -l" to validate that my booting drive is in fact /dev/sda
mount /dev/sda8 /0/sa08
because I want to work in partition 8
What I get in response is ========================================================== # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call. ==========================================================
Why is TW not letting me mount by confirmed device-name?
Why do you say it doesn't? What evidence have you shown? You have not shown that you can mount by another method. AND, you have not shown that you read the error message and done what it told you to do. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Thu, 25 Jan 2024 08:53:39 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 03:53, Ben T. Fender wrote:
After "fdisk -l" to validate that my booting drive is in fact /dev/sda
mount /dev/sda8 /0/sa08
because I want to work in partition 8
What I get in response is ========================================================== # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call. ==========================================================
Why is TW not letting me mount by confirmed device-name?
Why do you say it doesn't?
Because dolphin showed nothing under /0/sa07 :-)
What evidence have you shown?
The error message says /dev/sda7 is already mounted OR mountpoint is busy Maybe the error message should say WHERE it is mounted? The already-mounted bit couldn't be the reason because it's a path of my own making. I use canned mountpoints for often used mounts, this way my stuff never gets stepped on @ /mnt nor vice versa (below)
You have not shown that you can mount by another method.
I could mount by using uuid but that wasn't what I commanded
AND, you have not shown that you read the error message and done what it told you to do.
the error message is incomplete and dmesg is in chinese: https://paste.opensuse.org/pastes/92770e62f789 ls /0 adat sa11 sb08 sc05 sd02 sd14 se11 sf08 sg05 odd sa12 sb09 sc06 sd03 sd15 se12 sf09 sg06 sa01 sa13 sb10 sc07 sd04 se01 se13 sf10 sg07 sa02 sa14 sb11 sc08 sd05 se02 se14 sf11 sg08 sa03 sa15 sb12 sc09 sd06 se03 se15 sf12 sg09 sa04 sb01 sb13 sc10 sd07 se04 sf01 sf13 sg10 sa05 sb02 sb14 sc11 sd08 se05 sf02 sf14 sg11 sa06 sb03 sb15 sc12 sd09 se06 sf03 sf15 sg12 sa07 sb04 sc01 sc13 sd10 se07 sf04 sg01 sg13 sa08 sb05 sc02 sc14 sd11 se08 sf05 sg02 sg14 sa09 sb06 sc03 sc15 sd12 se09 sf06 sg03 sg15 sa10 sb07 sc04 sd01 sd13 se10 sf07 sg04
On Thu, Jan 25, 2024 at 5:06 PM Ben T. Fender <slowroller@trixtar.org> wrote:
Thu, 25 Jan 2024 08:53:39 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 03:53, Ben T. Fender wrote:
After "fdisk -l" to validate that my booting drive is in fact /dev/sda
mount /dev/sda8 /0/sa08
because I want to work in partition 8
What I get in response is ========================================================== # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call. ==========================================================
Why is TW not letting me mount by confirmed device-name?
Why do you say it doesn't?
Because dolphin showed nothing under /0/sa07 :-)
What evidence have you shown?
The error message says /dev/sda7 is already mounted OR mountpoint is busy
Maybe the error message should say WHERE it is mounted?
Post output of multipath -l
The already-mounted bit couldn't be the reason because it's a path of my own making. I use canned mountpoints for often used mounts, this way my stuff never gets stepped on @ /mnt nor vice versa (below)
You have not shown that you can mount by another method.
I could mount by using uuid but that wasn't what I commanded
AND, you have not shown that you read the error message and done what it told you to do.
the error message is incomplete and dmesg is in chinese:
https://paste.opensuse.org/pastes/92770e62f789
ls /0 adat sa11 sb08 sc05 sd02 sd14 se11 sf08 sg05 odd sa12 sb09 sc06 sd03 sd15 se12 sf09 sg06 sa01 sa13 sb10 sc07 sd04 se01 se13 sf10 sg07 sa02 sa14 sb11 sc08 sd05 se02 se14 sf11 sg08 sa03 sa15 sb12 sc09 sd06 se03 se15 sf12 sg09 sa04 sb01 sb13 sc10 sd07 se04 sf01 sf13 sg10 sa05 sb02 sb14 sc11 sd08 se05 sf02 sf14 sg11 sa06 sb03 sb15 sc12 sd09 se06 sf03 sf15 sg12 sa07 sb04 sc01 sc13 sd10 se07 sf04 sg01 sg13 sa08 sb05 sc02 sc14 sd11 se08 sf05 sg02 sg14 sa09 sb06 sc03 sc15 sd12 se09 sf06 sg03 sg15 sa10 sb07 sc04 sd01 sd13 se10 sf07 sg04
Thu, 25 Jan 2024 17:15:41 +0300 Andrei Borzenkov <arvidjaar@gmail.com> :
On Thu, Jan 25, 2024 at 5:06 PM Ben T. Fender <slowroller@trixtar.org> wrote:
Thu, 25 Jan 2024 08:53:39 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 03:53, Ben T. Fender wrote:
After "fdisk -l" to validate that my booting drive is in fact /dev/sda
mount /dev/sda8 /0/sa08
because I want to work in partition 8
What I get in response is ========================================================== # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call. ==========================================================
Why is TW not letting me mount by confirmed device-name?
Why do you say it doesn't?
Because dolphin showed nothing under /0/sa07 :-)
What evidence have you shown?
The error message says /dev/sda7 is already mounted OR mountpoint is busy
Maybe the error message should say WHERE it is mounted?
Post output of
multipath -l
# multipath -l Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T dm-0 ATA,Samsung SSD 860 size=932G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=0 status=active `- 2:0:0:0 sda 8:0 active undef running WDC_WD20EZBX-00AYRA0_WD-WXH2A31NP1A7 dm-13 ATA,WDC WD20EZBX-00A size=1.8T features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=0 status=active `- 4:0:0:0 sdb 8:16 active undef running 387.392488 | Warning: multipath devices exist, but multipathd service is not running THIS one might just be saying something Do I need dev-mapper OR multipathd?
The already-mounted bit couldn't be the reason because it's a path of my own making. I use canned mountpoints for often used mounts, this way my stuff never gets stepped on @ /mnt nor vice versa (below)
You have not shown that you can mount by another method.
I could mount by using uuid but that wasn't what I commanded
AND, you have not shown that you read the error message and done what it told you to do.
the error message is incomplete and dmesg is in chinese:
https://paste.opensuse.org/pastes/92770e62f789
ls /0 adat sa11 sb08 sc05 sd02 sd14 se11 sf08 sg05 odd sa12 sb09 sc06 sd03 sd15 se12 sf09 sg06 sa01 sa13 sb10 sc07 sd04 se01 se13 sf10 sg07 sa02 sa14 sb11 sc08 sd05 se02 se14 sf11 sg08 sa03 sa15 sb12 sc09 sd06 se03 se15 sf12 sg09 sa04 sb01 sb13 sc10 sd07 se04 sf01 sf13 sg10 sa05 sb02 sb14 sc11 sd08 se05 sf02 sf14 sg11 sa06 sb03 sb15 sc12 sd09 se06 sf03 sf15 sg12 sa07 sb04 sc01 sc13 sd10 se07 sf04 sg01 sg13 sa08 sb05 sc02 sc14 sd11 se08 sf05 sg02 sg14 sa09 sb06 sc03 sc15 sd12 se09 sf06 sg03 sg15 sa10 sb07 sc04 sd01 sd13 se10 sf07 sg04
On 25.01.2024 22:15, Ben T. Fender wrote:
Thu, 25 Jan 2024 17:15:41 +0300 Andrei Borzenkov <arvidjaar@gmail.com> :
On Thu, Jan 25, 2024 at 5:06 PM Ben T. Fender <slowroller@trixtar.org> wrote:
Thu, 25 Jan 2024 08:53:39 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 03:53, Ben T. Fender wrote:
After "fdisk -l" to validate that my booting drive is in fact /dev/sda
mount /dev/sda8 /0/sa08
because I want to work in partition 8
What I get in response is ========================================================== # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call. ==========================================================
Why is TW not letting me mount by confirmed device-name?
Why do you say it doesn't?
Because dolphin showed nothing under /0/sa07 :-)
What evidence have you shown?
The error message says /dev/sda7 is already mounted OR mountpoint is busy
Maybe the error message should say WHERE it is mounted?
Post output of
multipath -l
# multipath -l Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T dm-0 ATA,Samsung SSD 860 size=932G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=0 status=active `- 2:0:0:0 sda 8:0 active undef running WDC_WD20EZBX-00AYRA0_WD-WXH2A31NP1A7 dm-13 ATA,WDC WD20EZBX-00A size=1.8T features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=0 status=active `- 4:0:0:0 sdb 8:16 active undef running 387.392488 | Warning: multipath devices exist, but multipathd service is not running
So the error message was correct. The full disk is under device-mapper control so it is busy and you cannot directly mount its partition bypassing device-mapper.
THIS one might just be saying something
Do I need dev-mapper OR multipathd?
I do not know whether *you* need it (and it is called device-mapper, not dev-mapper), but using multipath for a device with a single path makes little sense. In any case - to mount partition 7 of sda7 you just need to use /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part7
On 2024-01-25 15:05, Ben T. Fender wrote:
Thu, 25 Jan 2024 08:53:39 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 03:53, Ben T. Fender wrote:
After "fdisk -l" to validate that my booting drive is in fact /dev/sda
mount /dev/sda8 /0/sa08
because I want to work in partition 8
What I get in response is ========================================================== # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call. ==========================================================
Why is TW not letting me mount by confirmed device-name?
Why do you say it doesn't?
Because dolphin showed nothing under /0/sa07 :-)
What evidence have you shown?
The error message says /dev/sda7 is already mounted OR mountpoint is busy
Your original question implies that it does not allow you to mount by device name but allows you to mount by using some other method. You have not shown proof of this, in this message at least.
Maybe the error message should say WHERE it is mounted? The already-mounted bit couldn't be the reason because it's a path of my own making. I use canned mountpoints for often used mounts, this way my stuff never gets stepped on @ /mnt nor vice versa (below)
You have not shown that you can mount by another method.
I could mount by using uuid but that wasn't what I commanded
AND, you have not shown that you read the error message and done what it told you to do.
the error message is incomplete and dmesg is in chinese:
Nonononono. You have to find out what new lines are written there when you issue the command, not the entire thing. That is, the instant you run the command and get the error message, your run dmesg and look at the end. Or, better still, you open a terminal, write "dmesg --follow", hit enter a few times, then on the original terminal issue the command. A few lines should print in the demsg terminal. Just read those lines, and post them here. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Thu, 25 Jan 2024 21:35:27 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 15:05, Ben T. Fender wrote:
Thu, 25 Jan 2024 08:53:39 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 03:53, Ben T. Fender wrote:
After "fdisk -l" to validate that my booting drive is in fact /dev/sda
mount /dev/sda8 /0/sa08
because I want to work in partition 8
What I get in response is ========================================================== # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call. ==========================================================
Why is TW not letting me mount by confirmed device-name?
Why do you say it doesn't?
Because dolphin showed nothing under /0/sa07 :-)
What evidence have you shown?
The error message says /dev/sda7 is already mounted OR mountpoint is busy
Your original question implies that it does not allow you to mount by device name but allows you to mount by using some other method. You have not shown proof of this, in this message at least.
Maybe the error message should say WHERE it is mounted? The already-mounted bit couldn't be the reason because it's a path of my own making. I use canned mountpoints for often used mounts, this way my stuff never gets stepped on @ /mnt nor vice versa (below)
You have not shown that you can mount by another method.
Not sure I understand what more I can do If I do # mount UUID=4960ac17-a377-4007-84fd-45ee43713a57 /0/sa07 then it gets mounted there but tha's NOT what I want (not interested in copy-pasting uuids!) DMESG: [ 1072.223450] EXT4-fs (dm-7): mounted filesystem 4960ac17-a377-4007-84fd-45ee43713a57 r/w with ordered data mode. Quota mode: none. [ 1072.229397] audit: type=1400 audit(1706219199.152:130): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1341 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003
I could mount by using uuid but that wasn't what I commanded
AND, you have not shown that you read the error message and done what it told you to do.
the error message is incomplete and dmesg is in chinese:
Nonononono. ... Or, better still, you open a terminal, write "dmesg --follow", hit enter a few times, then on the original terminal issue the command. A few lines should print in the demsg terminal.
Just read those lines, and post them here.
cool, thanks for reminding me that I look like the lumberjack who struggled with a chainsaw without starting it :-) Ok, so I done that and it ended up looking like this: # mount /dev/sda7 /0/sa07 ERROR MESSAGE: mount: /0/sa07: /dev/sda7 already mounted or mount point busy. dmesg(1) may have more information after failed mount system call. DMESG: [ 434.252860] /dev/sda7: Can't open blockdev # mount /dev/sdc1 /0/sc01 NO ERROR DMESG: [ 457.306647] EXT4-fs (sdc1): warning: mounting fs with errors, running e2fsck is recommended [ 457.348560] EXT4-fs (sdc1): mounted filesystem 21655adc-bb12-4709-aaa7-faf4abdc8618 r/w with ordered data mode. Quota mode: none. [ 457.357989] audit: type=1400 audit(1706218584.296:113): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1341 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003 ...repeats last line a few times, then [ 765.151101] EXT4-fs (sdc1): error count since last fsck: 1166 [ 765.151137] EXT4-fs (sdc1): initial error at time 1681240940: ext4_lookup:1785: inode 231380078 [ 765.151161] EXT4-fs (sdc1): last error at time 1700089692: ext4_mb_generate_buddy:1215 this partition dies get mounted and am already dd-ing a slowroll backup to it # dd if=/dev/sda7 of=/0/sc01/OSes/m7-sR-2024-01-24.dd bs=16M status=progress
On 2024-01-25 22:55, Ben T. Fender wrote:
Thu, 25 Jan 2024 21:35:27 +0100 "Carlos E. R." <> :
On 2024-01-25 15:05, Ben T. Fender wrote:
Thu, 25 Jan 2024 08:53:39 +0100 "Carlos E. R." <> :
On 2024-01-25 03:53, Ben T. Fender wrote:
...
You have not shown that you can mount by another method.
Not sure I understand what more I can do
If I do
# mount UUID=4960ac17-a377-4007-84fd-45ee43713a57 /0/sa07
then it gets mounted there but tha's NOT what I want (not interested in copy-pasting uuids!)
DMESG:
[ 1072.223450] EXT4-fs (dm-7): mounted filesystem 4960ac17-a377-4007-84fd-45ee43713a57 r/w with ordered data mode. Quota mode: none. [ 1072.229397] audit: type=1400 audit(1706219199.152:130): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1341 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003
Notice that the log says it mounted dm-7! That's a device mapper name.
I could mount by using uuid but that wasn't what I commanded
AND, you have not shown that you read the error message and done what it told you to do.
the error message is incomplete and dmesg is in chinese:
Nonononono. ... Or, better still, you open a terminal, write "dmesg --follow", hit enter a few times, then on the original terminal issue the command. A few lines should print in the demsg terminal.
Just read those lines, and post them here.
cool, thanks for reminding me that I look like the lumberjack who struggled with a chainsaw without starting it :-)
Ok, so I done that and it ended up looking like this:
# mount /dev/sda7 /0/sa07
ERROR MESSAGE: mount: /0/sa07: /dev/sda7 already mounted or mount point busy. dmesg(1) may have more information after failed mount system call.
DMESG: [ 434.252860] /dev/sda7: Can't open blockdev
Yeah, it is not there. Andrei said you are using multipath and device mapper, so it is not there. In Linux, in case of error, READ THE LOG. And read what the command error says. If it says "read somewhere", do read somewhere. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Fri, Jan 26, 2024 at 2:15 PM Carlos E. R. <robin.listas@telefonica.net> wrote: ...
Notice that the log says it mounted dm-7! That's a device mapper name.
This name may change next boot. ...
DMESG: [ 434.252860] /dev/sda7: Can't open blockdev
Yeah, it is not there.
It is there, but it is opened exclusively by device-mapper and so cannot be opened by mount.
Fri, 26 Jan 2024 12:15:03 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 22:55, Ben T. Fender wrote:
Thu, 25 Jan 2024 21:35:27 +0100 "Carlos E. R." <> :
On 2024-01-25 15:05, Ben T. Fender wrote:
Thu, 25 Jan 2024 08:53:39 +0100 "Carlos E. R." <> :
On 2024-01-25 03:53, Ben T. Fender wrote:
...
You have not shown that you can mount by another method.
Not sure I understand what more I can do
If I do
# mount UUID=4960ac17-a377-4007-84fd-45ee43713a57 /0/sa07
then it gets mounted there but tha's NOT what I want (not interested in copy-pasting uuids!)
DMESG:
[ 1072.223450] EXT4-fs (dm-7): mounted filesystem 4960ac17-a377-4007-84fd-45ee43713a57 r/w with ordered data mode. Quota mode: none. [ 1072.229397] audit: type=1400 audit(1706219199.152:130): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1341 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003
Notice that the log says it mounted dm-7! That's a device mapper name.
Yes, I've noticed the dozen dm lines in the fdisk output: /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part7 645924864 855640063 209715200 100G Linux filesystem But the thing is this: /dev/sda7 is another linux OS in this case and no-one told the freakin' system to *mount* it ANYWHERE! So why is it being mounted at all? Knowing where something is is one thing, sticking your dick into it without being told to is something else. What kind of confusion can this lead to if I have 10 back-level copies of my OS all with the same uuid there, just to look at one of many possible examples? If some app wants to know what partitions exist let it run "fdisk-l" EACH TIME. I gotta keep device-mapper and multipath packages for vBox to work (from what I see) so that's probably how they got onto my hard-drives in the first place. And I need vBox because it's the only way I can run the microcancer bundleware of my Boss-gx-100 effects board. # umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy. A partition that is totally off-limits unless I say otherwise is being mounted without my knowlege, permission, or directive AND I can't even unmount it? I don't get this, and like it even less. So what does a user have to do, delete the partition from the table before each boot and edit it back in on shutdown?
On 2024-01-26 13:09, Ben T. Fender wrote:
Fri, 26 Jan 2024 12:15:03 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 22:55, Ben T. Fender wrote:
Thu, 25 Jan 2024 21:35:27 +0100 "Carlos E. R." <> :
On 2024-01-25 15:05, Ben T. Fender wrote:
Thu, 25 Jan 2024 08:53:39 +0100 "Carlos E. R." <> :
On 2024-01-25 03:53, Ben T. Fender wrote:
...
You have not shown that you can mount by another method.
Not sure I understand what more I can do
If I do
# mount UUID=4960ac17-a377-4007-84fd-45ee43713a57 /0/sa07
then it gets mounted there but tha's NOT what I want (not interested in copy-pasting uuids!)
DMESG:
[ 1072.223450] EXT4-fs (dm-7): mounted filesystem 4960ac17-a377-4007-84fd-45ee43713a57 r/w with ordered data mode. Quota mode: none. [ 1072.229397] audit: type=1400 audit(1706219199.152:130): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1341 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003
Notice that the log says it mounted dm-7! That's a device mapper name.
Yes, I've noticed the dozen dm lines in the fdisk output:
/dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part7 645924864 855640063 209715200 100G Linux filesystem
But the thing is this: /dev/sda7 is another linux OS in this case and no-one told the freakin' system to *mount* it ANYWHERE! So why is it being mounted at all? Knowing where something is is one thing, sticking your dick into it without being told to is something else. What kind of confusion can this lead to if I have 10 back-level copies of my OS all with the same uuid there, just to look at one of many possible examples? If some app wants to know what partitions exist let it run "fdisk-l" EACH TIME.
I gotta keep device-mapper and multipath packages for vBox to work (from what I see) so that's probably how they got onto my hard-drives in the first place. And I need vBox because it's the only way I can run the microcancer bundleware of my Boss-gx-100 effects board.
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
A partition that is totally off-limits unless I say otherwise is being mounted without my knowlege, permission, or directive AND I can't even unmount it? I don't get this, and like it even less. So what does a user have to do, delete the partition from the table before each boot and edit it back in on shutdown?
Mounted where? Then use lsof to find what is keeping it busy and kill it. Then report in Bugzilla. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Fri, Jan 26, 2024 at 3:10 PM Ben T. Fender <slowroller@trixtar.org> wrote: ...
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
A partition that is totally off-limits unless I say otherwise is being mounted without my knowlege, permission, or directive AND I can't even unmount it?
Of course you cannot unmount your root partition.
On 2024-01-26 13:45, Andrei Borzenkov wrote:
On Fri, Jan 26, 2024 at 3:10 PM Ben T. Fender <slowroller@trixtar.org> wrote: ...
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
A partition that is totally off-limits unless I say otherwise is being mounted without my knowlege, permission, or directive AND I can't even unmount it?
Of course you cannot unmount your root partition.
Wow! I didn't realize this. I should have. He said "But the thing is this: /dev/sda7 is another linux OS in this case" — so I believed this "is another linux". Well, it is not, it is the Linux that is booted. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Fri, 26 Jan 2024 14:20:36 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-26 13:45, Andrei Borzenkov wrote:
On Fri, Jan 26, 2024 at 3:10 PM Ben T. Fender <slowroller@trixtar.org> wrote: ...
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
A partition that is totally off-limits unless I say otherwise is being mounted without my knowlege, permission, or directive AND I can't even unmount it?
Of course you cannot unmount your root partition.
Wow! I didn't realize this. I should have.
He said "But the thing is this: /dev/sda7 is another linux OS in this case" — so I believed this "is another linux". Well, it is not, it is the Linux that is booted.
Very cute, but you're thinking of my old rags, the times they are a changing. I just established a new standard for my drives with the first 3 partitions, so from now on I don't care if its DOS or EFI or my neighbour's pucking fiano all my OS drives will be partitioned the same catering to whatever needs to be catered to. BEFORE 7 used to be TW. # fdisk -l Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 860 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2CB71AC7-D2DB-4B81-A559-02802643D197 Device Start End Sectors Size Type /dev/sda1 2048 2099199 2097152 1G EFI System /dev/sda2 2099200 4196351 2097152 1G BIOS boot /dev/sda3 4196352 16779263 12582912 6G Linux swap /dev/sda4 16779264 226494463 209715200 100G Linux filesystem /dev/sda5 226494464 436209663 209715200 100G Linux filesystem /dev/sda6 436209664 645924863 209715200 100G Linux filesystem /dev/sda7 645924864 855640063 209715200 100G Linux filesystem /dev/sda8 855640064 1065355263 209715200 100G Linux filesystem /dev/sda9 1065355264 1275070463 209715200 100G Linux filesystem /dev/sda10 1275070464 1484785663 209715200 100G Linux filesystem /dev/sda11 1484785664 1694500863 209715200 100G Linux filesystem /dev/sda12 1694500864 1946159103 251658240 120G Linux filesystem 4 - Artix 5 - Devuan 6 - Slack 7 - Slowroll (formerly Leap) 8 - TW 9 - AvLinux 10 - looking for a tenant (was 'buntu-studio, gone!) 11 - unused except testing 12 - leftover for whatever
On 2024-01-26 17:39, Ben T. Fender wrote:
Fri, 26 Jan 2024 14:20:36 +0100 "Carlos E. R." <> :
On 2024-01-26 13:45, Andrei Borzenkov wrote:
On Fri, Jan 26, 2024 at 3:10 PM Ben T. Fender <slowroller@trixtar.org> wrote: ...
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
A partition that is totally off-limits unless I say otherwise is being mounted without my knowlege, permission, or directive AND I can't even unmount it?
Of course you cannot unmount your root partition.
Wow! I didn't realize this. I should have.
He said "But the thing is this: /dev/sda7 is another linux OS in this case" — so I believed this "is another linux". Well, it is not, it is the Linux that is booted.
Very cute, but you're thinking of my old rags, the times they are a changing. I just established a new standard for my drives with the first 3 partitions, so from now on I don't care if its DOS or EFI or my neighbour's pucking fiano all my OS drives will be partitioned the same catering to whatever needs to be catered to. BEFORE 7 used to be TW.
Irrelevant. You said:
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
..........^___ that's root. That partition is mounted on root, no matter your protestations.
# fdisk -l Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 860 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2CB71AC7-D2DB-4B81-A559-02802643D197
Device Start End Sectors Size Type /dev/sda1 2048 2099199 2097152 1G EFI System /dev/sda2 2099200 4196351 2097152 1G BIOS boot /dev/sda3 4196352 16779263 12582912 6G Linux swap /dev/sda4 16779264 226494463 209715200 100G Linux filesystem /dev/sda5 226494464 436209663 209715200 100G Linux filesystem /dev/sda6 436209664 645924863 209715200 100G Linux filesystem /dev/sda7 645924864 855640063 209715200 100G Linux filesystem /dev/sda8 855640064 1065355263 209715200 100G Linux filesystem /dev/sda9 1065355264 1275070463 209715200 100G Linux filesystem /dev/sda10 1275070464 1484785663 209715200 100G Linux filesystem /dev/sda11 1484785664 1694500863 209715200 100G Linux filesystem /dev/sda12 1694500864 1946159103 251658240 120G Linux filesystem
4 - Artix 5 - Devuan 6 - Slack 7 - Slowroll (formerly Leap) 8 - TW 9 - AvLinux 10 - looking for a tenant (was 'buntu-studio, gone!) 11 - unused except testing 12 - leftover for whatever
Instead (one single line): lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT | less -S -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Fri, 26 Jan 2024 19:08:33 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-26 17:39, Ben T. Fender wrote:
Fri, 26 Jan 2024 14:20:36 +0100 "Carlos E. R." <> :
On 2024-01-26 13:45, Andrei Borzenkov wrote:
On Fri, Jan 26, 2024 at 3:10 PM Ben T. Fender <slowroller@trixtar.org> wrote: ...
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
A partition that is totally off-limits unless I say otherwise is being mounted without my knowlege, permission, or directive AND I can't even unmount it?
Of course you cannot unmount your root partition.
Wow! I didn't realize this. I should have. E[GwuDq;~6{RC_+!=Wg-9{QF+6S#$r*LTsbD He said "But the thing is this: /dev/sda7 is another linux OS in this case" — so I believed this "is another linux". Well, it is not, it is the Linux that is booted.
Very cute, but you're thinking of my old rags, the times they are a changing. I just established a new standard for my drives with the first 3 partitions, so from now on I don't care if its DOS or EFI or my neighbour's pucking fiano all my OS drives will be partitioned the same catering to whatever needs to be catered to. BEFORE 7 used to be TW.
Irrelevant.
You said:
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
..........^___ that's root. That partition is mounted on root, no matter your protestations.
It's possible, but now I'm definitely on part-8 and # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy. dmesg(1) may have more information after failed mount system call. DMESG: [ 3623.707590] audit: type=1400 audit(1706298089.239:537): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1388 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003 [ 3628.696970] /dev/sda7: Can't open blockdev So the part-7 is either mounted OR the mountpoint /0/sa07 is busy. If I try to umount IT (instead of / which obviously had been a mistake) then it says the partition is not mounted. That leaves mountpoint /0/sa07 being busy as the sole alternative according to the error message.
On 2024-01-26 20:43, Ben T. Fender wrote:
Fri, 26 Jan 2024 19:08:33 +0100 "Carlos E. R." <...> :
On 2024-01-26 17:39, Ben T. Fender wrote:
Fri, 26 Jan 2024 14:20:36 +0100 "Carlos E. R." <> :
On 2024-01-26 13:45, Andrei Borzenkov wrote:
On Fri, Jan 26, 2024 at 3:10 PM Ben T. Fender <slowroller@trixtar.org> wrote: ...
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
A partition that is totally off-limits unless I say otherwise is being mounted without my knowlege, permission, or directive AND I can't even unmount it?
Of course you cannot unmount your root partition.
Wow! I didn't realize this. I should have. E[GwuDq;~6{RC_+!=Wg-9{QF+6S#$r*LTsbD He said "But the thing is this: /dev/sda7 is another linux OS in this case" — so I believed this "is another linux". Well, it is not, it is the Linux that is booted.
Very cute, but you're thinking of my old rags, the times they are a changing. I just established a new standard for my drives with the first 3 partitions, so from now on I don't care if its DOS or EFI or my neighbour's pucking fiano all my OS drives will be partitioned the same catering to whatever needs to be catered to. BEFORE 7 used to be TW.
Irrelevant.
You said:
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
..........^___ that's root. That partition is mounted on root, no matter your protestations.
It's possible, but now I'm definitely on part-8 and
# mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy. dmesg(1) may have more information after failed mount system call.
DMESG: [ 3623.707590] audit: type=1400 audit(1706298089.239:537): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1388 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003 [ 3628.696970] /dev/sda7: Can't open blockdev
Andrei told you the reason. They are in exclusive use by device-mapper. So "Can't open blockdev".
So the part-7 is either mounted OR the mountpoint /0/sa07 is busy. If I try to umount IT (instead of / which obviously had been a mistake) then it says the partition is not mounted. That leaves mountpoint /0/sa07 being busy as the sole alternative according to the error message.
Neither. Read the log. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Fri, 26 Jan 2024 20:50:00 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-26 20:43, Ben T. Fender wrote:
It's possible, but now I'm definitely on part-8 and
# mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy. dmesg(1) may have more information after failed mount system call.
DMESG: [ 3623.707590] audit: type=1400 audit(1706298089.239:537): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1388 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003 [ 3628.696970] /dev/sda7: Can't open blockdev
Andrei told you the reason. They are in exclusive use by device-mapper. So "Can't open blockdev".
Ok, they're locked out but not mounted, then that's what the error message should say. So how can I find out WHY they are locked out by device-manager? They have nothing to do with the booted system but they do make it impossible to do anything in them from the booted system, is this something from redhat too?
On 2024-01-26 21:34, Ben T. Fender wrote:
Fri, 26 Jan 2024 20:50:00 +0100 "Carlos E. R." <> :
On 2024-01-26 20:43, Ben T. Fender wrote:
It's possible, but now I'm definitely on part-8 and
# mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy. dmesg(1) may have more information after failed mount system call.
DMESG: [ 3623.707590] audit: type=1400 audit(1706298089.239:537): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1388 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003 [ 3628.696970] /dev/sda7: Can't open blockdev
Andrei told you the reason. They are in exclusive use by device-mapper. So "Can't open blockdev".
Ok, they're locked out but not mounted, then that's what the error message should say.
No, the error message can only say what it does say.
So how can I find out WHY they are locked out by device-manager? They have nothing to do with the booted system but they do make it impossible to do anything in them from the booted system, is this something from redhat too?
I have no idea. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Fri, 26 Jan 2024 19:08:33 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-26 17:39, Ben T. Fender wrote:
4 - Artix 5 - Devuan 6 - Slack 7 - Slowroll (formerly Leap) 8 - TW 9 - AvLinux 10 - looking for a tenant (was 'buntu-studio, gone!) 11 - unused except testing 12 - leftover for whatever
Instead (one single line):
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT | less -S
...done https://transfiles.ru/hiv4f this one does show dm-13 & dm-14 that blkid doesn't
On 2024-01-26 21:49, Ben T. Fender wrote:
Fri, 26 Jan 2024 19:08:33 +0100 "Carlos E. R." <> :
On 2024-01-26 17:39, Ben T. Fender wrote:
4 - Artix 5 - Devuan 6 - Slack 7 - Slowroll (formerly Leap) 8 - TW 9 - AvLinux 10 - looking for a tenant (was 'buntu-studio, gone!) 11 - unused except testing 12 - leftover for whatever
Instead (one single line):
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT | less -S
...done
It is incomplete. One line. lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT | susepaste -n "Ben T. Fender" -t "lsblk output" -e 40320 -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Fri, 26 Jan 2024 22:40:34 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-26 21:49, Ben T. Fender wrote:
Fri, 26 Jan 2024 19:08:33 +0100 "Carlos E. R." <> :
On 2024-01-26 17:39, Ben T. Fender wrote:
4 - Artix 5 - Devuan 6 - Slack 7 - Slowroll (formerly Leap) 8 - TW 9 - AvLinux 10 - looking for a tenant (was 'buntu-studio, gone!) 11 - unused except testing 12 - leftover for whatever
Instead (one single line):
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT | less -S
...done
It is incomplete.
One line.
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT | susepaste -n "Ben T. Fender" -t "lsblk output" -e 40320
Just did zypper dup and the issue is GONE, I can mount whatever I like and KDiskFree shows /dev/sdXY's
On 2024-01-26 23:16, Ben T. Fender wrote:
Fri, 26 Jan 2024 22:40:34 +0100 "Carlos E. R." <> :
On 2024-01-26 21:49, Ben T. Fender wrote:
Fri, 26 Jan 2024 19:08:33 +0100 "Carlos E. R." <> :
On 2024-01-26 17:39, Ben T. Fender wrote:
4 - Artix 5 - Devuan 6 - Slack 7 - Slowroll (formerly Leap) 8 - TW 9 - AvLinux 10 - looking for a tenant (was 'buntu-studio, gone!) 11 - unused except testing 12 - leftover for whatever
Instead (one single line):
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT | less -S
...done
It is incomplete.
One line.
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT | susepaste -n "Ben T. Fender" -t "lsblk output" -e 40320
Just did zypper dup and the issue is GONE, I can mount whatever I like and KDiskFree shows /dev/sdXY's
Oh. Well, there is a reason I don't use TW... -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Fri, 26 Jan 2024 15:45:47 +0300 Andrei Borzenkov <arvidjaar@gmail.com> :
On Fri, Jan 26, 2024 at 3:10 PM Ben T. Fender <slowroller@trixtar.org> wrote: ...
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
A partition that is totally off-limits unless I say otherwise is being mounted without my knowlege, permission, or directive AND I can't even unmount it?
Of course you cannot unmount your root partition.
That was a goof or maybe I was booted into partition 9-11, trying many different things these days. BUT your hint led me to question why KDiskFree was showing dm-9 as / when it was supposed to be partition 8. So I booted manually and got dm-8 which is what it should be. On the next boot I went again with the grub menu but ended up with dm-8 and not dm-9 as after the previous grub menu boot. I'll try to investigate a little more from a rescue frisby...
Fri, 26 Jan 2024 12:31:03 -0500 "Ben T. Fender" <slowroller@trixtar.org> :
Fri, 26 Jan 2024 15:45:47 +0300 Andrei Borzenkov <arvidjaar@gmail.com> :
On Fri, Jan 26, 2024 at 3:10 PM Ben T. Fender <slowroller@trixtar.org> wrote: ...
# umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy.
A partition that is totally off-limits unless I say otherwise is being mounted without my knowlege, permission, or directive AND I can't even unmount it?
Of course you cannot unmount your root partition.
That was a goof or maybe I was booted into partition 9-11, trying many different things these days. BUT your hint led me to question why KDiskFree was showing dm-9 as / when it was supposed to be partition 8. So I booted manually and got dm-8 which is what it should be. On the next boot I went again with the grub menu but ended up with dm-8 and not dm-9 as after the previous grub menu boot. I'll try to investigate a little more from a rescue frisby...
Just went over the lot from a Live-TW and everything that I can see checks out, partitions 4-11 are bootable and boot no problem manually, all the fstabs jive with the 3 blkids in each (/, swap, data), nothing to do. However this TW in partition 8 is throwing different fits, and I don't think its grub. VERY SLOW to BOOTZ. Before taking off on this investigation /dev/dm-9 was showing in KDiskFree as / instead of /dev/sda8. Now /dev/dm-14 is showing where /dev/sdb1 should be for data (/0/adat). Both of these readings are definetely wrong. There are /dev/dm-12, /dev/dm-13 & /dev/dm-14 but digging into them is above my paygrade. There is no sign of any /dev/dm 12,13 or 14 in fdisk: https://transfiles.ru/7hvv1 I'll be booting manually for a while.
Ben T. Fender composed on 2024-01-26 07:09 (UTC-0500):
But the thing is this: /dev/sda7 is another linux OS in this case and no-one told the freakin' system to *mount* it ANYWHERE! So why is it being mounted at all? Knowing where something is is one thing, sticking your dick into it without being told to is something else.
This has been bothering me too lately, mostly though with ESPs on multiboot systems, sticking the ESP in /efi if no entry for ESP exists in /etc/fstab. One way to deal with it generally is to create a noauto fstab entry for it. Ben T. Fender composed on 2024-01-26 11:39 (UTC-0500):
# fdisk -l Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 860 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2CB71AC7-D2DB-4B81-A559-02802643D197
Device Start End Sectors Size Type /dev/sda1 2048 2099199 2097152 1G EFI System /dev/sda2 2099200 4196351 2097152 1G BIOS boot /dev/sda3 4196352 16779263 12582912 6G Linux swap /dev/sda4 16779264 226494463 209715200 100G Linux filesystem /dev/sda5 226494464 436209663 209715200 100G Linux filesystem /dev/sda6 436209664 645924863 209715200 100G Linux filesystem /dev/sda7 645924864 855640063 209715200 100G Linux filesystem /dev/sda8 855640064 1065355263 209715200 100G Linux filesystem /dev/sda9 1065355264 1275070463 209715200 100G Linux filesystem /dev/sda10 1275070464 1484785663 209715200 100G Linux filesystem /dev/sda11 1484785664 1694500863 209715200 100G Linux filesystem /dev/sda12 1694500864 1946159103 251658240 120G Linux filesystem
That's a lot of wasted disk space. Most installations here don't get a tenth of that much allocated to /: # fdisk -l | head Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: Patriot M.2 P300 512GB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 5B330B05... Device Start End Sectors Size Type /dev/nvme0n1p1 2048 657407 655360 320M EFI System # lsblk -o NAME,FSTYPE,LABEL,SIZE,MOUNTPOINTS NAME FSTYPE LABEL SIZE MOUNTPOINTS nvme0n1 476.9G ├─nvme0n1p1 vfat PT3P01ESP 320M /boot/efi ├─nvme0n1p2 swap pt3p02swap 1.7G ├─nvme0n1p3 ext2 pt3p03res 400M /disks/res ├─nvme0n1p4 ext4 pt3p04ulcl 3.9G /usr/local ├─nvme0n1p5 ext4 pt3p05home 6.3G /home ├─nvme0n1p6 ext4 pt3p06pub 12.3G /pub ├─nvme0n1p7 ext4 pt3p07stw 7.8G / ├─nvme0n1p8 ext4 pt3p08s153 7.8G /disks/s153 ├─nvme0n1p9 ext4 pt3p09s151 7.8G /disks/s151 ├─nvme0n1p10 ext4 pt3p10deb12 7.8G ├─nvme0n1p11 ext4 pt3p11s155 7.8G /disks/s155 ├─nvme0n1p12 ext4 pt3p12ub22 7.8G ├─nvme0n1p13 ext4 pt3p13deb13 7.8G ├─nvme0n1p14 ext4 pt3p14deb11 7.8G ├─nvme0n1p15 ext4 pt3p15f39 7.8G ├─nvme0n1p16 ext4 pt3p16s154 7.8G /disks/s154 ├─nvme0n1p17 ext4 pt3p17ub20 7.8G ├─nvme0n1p18 ext4 pt3p18f38 7.8G ├─nvme0n1p19 ext4 pt3p19sslo 7.8G /disks/sslo ├─nvme0n1p20 7.8G ├─nvme0n1p21 ext4 pt3p21ub18 7.8G ├─nvme0n1p22 ext4 pt3p22mga09 7.8G ├─nvme0n1p23 7.8G └─nvme0n1p24 ext4 pt3p24ub24 7.8G # The most allocated to a / FS here is 18G, and I only put /home, /usr/local, various data types, and sometimes /boot on separate filesystems/partitions. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Fri, 26 Jan 2024 13:19:48 -0500 Felix Miata <mrmazda@earthlink.net> :
Ben T. Fender composed on 2024-01-26 07:09 (UTC-0500):
But the thing is this: /dev/sda7 is another linux OS in this case and no-one told the freakin' system to *mount* it ANYWHERE! So why is it being mounted at all? Knowing where something is is one thing, sticking your dick into it without being told to is something else.
This has been bothering me too lately, mostly though with ESPs on multiboot systems, sticking the ESP in /efi if no entry for ESP exists in /etc/fstab. One way to deal with it generally is to create a noauto fstab entry for it.
You mean as a countermeasure I should drop lines in fstab for all other partitions specifying 'noauto' so as to prevent anythingh else from mounting them? Does systemd get clobbered by noauto? May be an idea but how would I interdict automount without mounting it somewhere? Never done one of these before :-)
Ben T. Fender composed on 2024-01-26 11:39 (UTC-0500):
# fdisk -l Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 860 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2CB71AC7-D2DB-4B81-A559-02802643D197
Device Start End Sectors Size Type /dev/sda1 2048 2099199 2097152 1G EFI System /dev/sda2 2099200 4196351 2097152 1G BIOS boot /dev/sda3 4196352 16779263 12582912 6G Linux swap /dev/sda4 16779264 226494463 209715200 100G Linux filesystem /dev/sda5 226494464 436209663 209715200 100G Linux filesystem /dev/sda6 436209664 645924863 209715200 100G Linux filesystem /dev/sda7 645924864 855640063 209715200 100G Linux filesystem /dev/sda8 855640064 1065355263 209715200 100G Linux filesystem /dev/sda9 1065355264 1275070463 209715200 100G Linux filesystem /dev/sda10 1275070464 1484785663 209715200 100G Linux filesystem /dev/sda11 1484785664 1694500863 209715200 100G Linux filesystem /dev/sda12 1694500864 1946159103 251658240 120G Linux filesystem
That's a lot of wasted disk space.
I've seen some around 60gb and I wanted them to be all exactly uniform so I can just dd any one of them to any of those 100gb partitions and not just on one disk.
participants (4)
-
Andrei Borzenkov -
Ben T. Fender -
Carlos E. R. -
Felix Miata