On Thu 08 Aug 2019 at 10:56:46 (-0400), Michael Stone wrote: > On Thu, Aug 08, 2019 at 09:04:00AM -0500, David Wright wrote: > > wren 08:50:11 ~# lsblk -f | grep sda7 > > ├─sda7 ext4 swan07 4a4e352f-2180-4083-92b4-f46e4e0104b4 > > /wrenbk > > wren 08:50:26 ~# mkdir /wa1 /somethingelse > > wren 08:50:49 ~# mount /dev/sda7 /somethingelse > > mount: /dev/sda7 is already mounted or /somethingelse busy > > /dev/sda7 is already mounted on /wrenbk > > 32 wren 08:51:16 ~# mount /dev/sda7 /wa1 > > mount: /dev/sda7 is already mounted or /wa1 busy > > /dev/sda7 is already mounted on /wrenbk > > 32 wren 08:51:31 ~# rmdir /wa1 /somethingelse > > wren 08:51:53 ~# > > It's already been said repeatedly that you should post the bottom of > dmesg output because kernel mount errors show up there but not in the > output of the mount command.
I've plenty of mount errors, which you've quoted, so I think you might be addressing somebody else. Or have I missed something? But anyway, dmesg's tail is attached, with a timecheck from earlier in the file so that you can exercise forensic skills in tying the times above to those in dmesg. But the 2-1 vote wasn't whether error messages were emitted, but whether the system should mount an already-mounted partition onto another mount point. I get error messages and the mount fails. Others get no error messages (though they haven't demonstrated the lack) and a successful mount, so currently I'm in a minority of one. Cheers, David.
wren!david 11:48:24 ~ $ sudo dmesg | tail -44 [ 7.670527] input: Logitech M325 as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.2/0003:046D:C52B.0004/0003:046D:400A.0005/input/input16 [ 7.670678] logitech-hidpp-device 0003:046D:400A.0005: input,hidraw2: USB HID v1.11 Mouse [Logitech M325] on usb-0000:00:14.0-3:1 [ 7.776587] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 26.233593] NET: Registered protocol family 38 [ 26.987123] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 26.987125] Bluetooth: BNEP filters: protocol multicast [ 26.987129] Bluetooth: BNEP socket layer initialized [ 27.316823] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 28.161268] snd_hda_intel 0000:00:1b.0: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj. [ 28.939974] NET: Registered protocol family 4 [ 28.996931] NET: Registered protocol family 3 [ 29.003641] NET: Registered protocol family 5 [ 29.046309] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 29.046548] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 29.254775] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 29.255014] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 29.268134] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 34.036010] r8169 0000:01:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-3.fw [ 34.080863] r8169 0000:01:00.0 enp1s0: link down [ 34.080938] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 36.872387] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 36.872630] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 37.081325] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 37.081578] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 37.096019] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 37.268985] r8169 0000:01:00.0 enp1s0: link down [ 37.269078] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 37.364921] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 37.365164] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 37.588695] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 37.588937] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled [ 37.603886] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 40.255626] wlp2s0: authenticate with b0:39:56:6b:03:f1 [ 40.259205] wlp2s0: send auth to b0:39:56:6b:03:f1 (try 1/3) [ 40.263223] wlp2s0: authenticated [ 40.263248] wlp2s0: associating with AP with corrupt probe response [ 40.267190] wlp2s0: associate with b0:39:56:6b:03:f1 (try 1/3) [ 40.280094] wlp2s0: RX AssocResp from b0:39:56:6b:03:f1 (capab=0x411 status=0 aid=3) [ 40.300237] wlp2s0: associated [ 40.400149] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready [ 40.816452] IPv6: wlp2s0: IPv6 duplicate address fe80::e8b:fdff:fe0b:67fb detected! [ 146.463666] Bluetooth: RFCOMM TTY layer initialized [ 146.463674] Bluetooth: RFCOMM socket layer initialized [ 146.463680] Bluetooth: RFCOMM ver 1.11 wren!david 11:48:43 ~ $ sudo dmesg | grep -i 'setting system clock' [ 0.844238] rtc_cmos 00:01: setting system clock to 2019-08-08 11:49:59 UTC (1565264999) wren!david 11:49:01 ~ $
