Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #212275 > unrolled thread

mount weirdness

Back to article view | Back to linux.debian.user

Contents

  mount weirdness Dennis Wicks <wix@mgssub.com> - 2019-08-05 22:40 +0200
    Re: mount weirdness Andrei POPESCU <andreimpopescu@gmail.com> - 2019-08-06 08:10 +0200
      Re: mount weirdness Dennis Wicks <wix@mgssub.com> - 2019-08-06 17:10 +0200
        Re: mount weirdness rhkramer@gmail.com - 2019-08-06 17:40 +0200
          Re: mount weirdness Dennis Wicks <wix@mgssub.com> - 2019-08-06 19:40 +0200
            Re: mount weirdness Richard Hector <richard@walnut.gen.nz> - 2019-08-06 19:50 +0200
              Re: mount weirdness Dennis Wicks <wix@mgssub.com> - 2019-08-06 20:00 +0200
                Re: mount weirdness Richard Hector <richard@walnut.gen.nz> - 2019-08-06 20:20 +0200
        Re: mount weirdness Felix Miata <mrmazda@earthlink.net> - 2019-08-06 17:40 +0200
          Re: mount weirdness Dennis Wicks <wix@mgssub.com> - 2019-08-06 19:30 +0200
    Re: mount weirdness "Thomas Schmitt" <scdbackup@gmx.net> - 2019-08-06 17:40 +0200
      Re: mount weirdness Dennis Wicks <wix@mgssub.com> - 2019-08-06 19:20 +0200
        Re: mount weirdness David Wright <deblis@lionunicorn.co.uk> - 2019-08-06 20:50 +0200
          Re: mount weirdness Dennis Wicks <wix@mgssub.com> - 2019-08-07 19:50 +0200
            Re: mount weirdness Greg Wooledge <wooledg@eeg.ccf.org> - 2019-08-07 20:00 +0200
            Re: mount weirdness David Wright <deblis@lionunicorn.co.uk> - 2019-08-07 22:50 +0200
        Re: mount weirdness "Thomas Schmitt" <scdbackup@gmx.net> - 2019-08-06 21:00 +0200
          Re: mount weirdness Dennis Wicks <wix@mgssub.com> - 2019-08-07 20:00 +0200
            Re: mount weirdness "Thomas Schmitt" <scdbackup@gmx.net> - 2019-08-07 23:30 +0200
    Re: mount weirdness Curt <curty@free.fr> - 2019-08-08 10:20 +0200
      Re: mount weirdness Curt <curty@free.fr> - 2019-08-08 10:50 +0200
        Re: mount weirdness Dennis Wicks <wix@mgssub.com> - 2019-08-09 21:20 +0200
      Re: mount weirdness "Thomas Schmitt" <scdbackup@gmx.net> - 2019-08-08 12:00 +0200
        Re: mount weirdness Curt <curty@free.fr> - 2019-08-08 14:40 +0200
        Re: mount weirdness Michael Stone <mstone@debian.org> - 2019-08-08 14:40 +0200
          Re: mount weirdness Curt <curty@free.fr> - 2019-08-08 15:00 +0200
      Re: mount weirdness David Wright <deblis@lionunicorn.co.uk> - 2019-08-08 16:10 +0200
        Re: mount weirdness Michael Stone <mstone@debian.org> - 2019-08-08 17:00 +0200
          Re: mount weirdness David Wright <deblis@lionunicorn.co.uk> - 2019-08-08 19:10 +0200
            Re: mount weirdness Greg Wooledge <wooledg@eeg.ccf.org> - 2019-08-08 19:20 +0200
            Re: mount weirdness Michael Stone <mstone@debian.org> - 2019-08-08 20:20 +0200
              Re: mount weirdness David Wright <deblis@lionunicorn.co.uk> - 2019-08-09 18:30 +0200
                Re: mount weirdness Greg Wooledge <wooledg@eeg.ccf.org> - 2019-08-09 19:00 +0200
                  Re: mount weirdness "Thomas Schmitt" <scdbackup@gmx.net> - 2019-08-09 20:00 +0200
        Re: mount weirdness Dennis Wicks <wix@mgssub.com> - 2019-08-09 22:00 +0200
      Re: mount weirdness Dennis Wicks <wix@mgssub.com> - 2019-08-09 21:20 +0200

Page 1 of 2  [1] 2  Next page →

#212275 — mount weirdness

I recently rebooted after an upgrade that generated
	"Jul 28 17:13 initrd.img-4.19.0-5-686-pae"
and when I was finally U&R I discovered that a mount didn't 
happen. (I am on Debian 10 Bullseye and my last kernel 
resulted in "Jul 18 17:23 vmlinuz-4.19.0-5-686-pae".)

I have mount points /wa1-/wa4 and I have been using them 
literally for years with no problem.

So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it 
seemed to finish successfully, but "ls /wa1" indicated that 
in fact it had not. Nothing mounted on wa1! Many other tests 
told me the same thing. "umount /wa1" said "not mounted"!

After trying many things I discovered that 1) I can mount 
/dev/sdb2 on any mount point except /wa1 and 2) I can't 
mount any /dev/sdxx on /wa1!! So I mounted sdb2 on /wa11,
"rmdir /wa1"and "ln -s /wa11 /wa1" and everything seems to 
work OK.

It seems that something in the mount process does not like 
"wa1" for a mount point. Anybody have similar recent problems?

[toc] | [next] | [standalone]

#212292

[Multipart message — attachments visible in raw view] — view raw

On Lu, 05 aug 19, 15:33:57, Dennis Wicks wrote:
> 
> It seems that something in the mount process does not like "wa1" for a mount
> point. Anybody have similar recent problems?
 
Please show your fstab and the output of 'lsblk -f'.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#212317

[Multipart message — attachments visible in raw view] — view raw

Requested info attached:

I *cannot* mount *any* partition on /wa1
but I *can* mount *any* partition on any other mount point.

Regards, and Thanks!
Dennis

Andrei POPESCU wrote on 8/6/19 1:06 AM:
> On Lu, 05 aug 19, 15:33:57, Dennis Wicks wrote:
>>
>> It seems that something in the mount process does not like "wa1" for a mount
>> point. Anybody have similar recent problems?
>   
> Please show your fstab and the output of 'lsblk -f'.
> 
> Kind regards,
> Andrei
> 

[toc] | [prev] | [next] | [standalone]

#212320

I didn't fully understand your fstab, but is there a typo -- wa11 vs. wa1?

On Tuesday, August 06, 2019 11:09:32 AM Dennis Wicks wrote:
> Requested info attached:
> 
> I *cannot* mount *any* partition on /wa1
> but I *can* mount *any* partition on any other mount point.
> 
> Regards, and Thanks!
> Dennis
> 
> Andrei POPESCU wrote on 8/6/19 1:06 AM:
> > On Lu, 05 aug 19, 15:33:57, Dennis Wicks wrote:
> >> It seems that something in the mount process does not like "wa1" for a
> >> mount point. Anybody have similar recent problems?
> > 
> > Please show your fstab and the output of 'lsblk -f'.
> > 
> > Kind regards,
> > Andrei

[toc] | [prev] | [next] | [standalone]

#212327

rhkramer@gmail.com wrote on 8/6/19 10:34 AM:
> I didn't fully understand your fstab, but is there a typo -- wa11 vs. wa1?
No. My current config is;

    /wa1 -> wa11 ( soft link )
    /wa11        ( <- /dev/sdb2 )

with sdb2 mounted on /wa11 so I don't have to find and 
change all the paths that I have starting with "/wa1/..."!
> 
> On Tuesday, August 06, 2019 11:09:32 AM Dennis Wicks wrote:
>> Requested info attached:
>>
>> I *cannot* mount *any* partition on /wa1
>> but I *can* mount *any* partition on any other mount point.
>>
>> Regards, and Thanks!
>> Dennis
>>
>> Andrei POPESCU wrote on 8/6/19 1:06 AM:
>>> On Lu, 05 aug 19, 15:33:57, Dennis Wicks wrote:
>>>> It seems that something in the mount process does not like "wa1" for a
>>>> mount point. Anybody have similar recent problems?
>>>
>>> Please show your fstab and the output of 'lsblk -f'.
>>>
>>> Kind regards,
>>> Andrei
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#212328

[Multipart message — attachments visible in raw view] — view raw

On 7/08/19 5:31 AM, Dennis Wicks wrote:
> rhkramer@gmail.com wrote on 8/6/19 10:34 AM:
>> I didn't fully understand your fstab, but is there a typo -- wa11 vs.
>> wa1?
> No. My current config is;
> 
>    /wa1 -> wa11 ( soft link )
>    /wa11        ( <- /dev/sdb2 )
> 
> with sdb2 mounted on /wa11 so I don't have to find and change all the
> paths that I have starting with "/wa1/..."!

So you're trying to mount on a symlink, instead of a directory? I don't
think that's going to work. Why not mount on /wa11, as you describe?

Or does /wa11 only exist because you can't mount on /wa1, and you were
trying to mount on /wa1 when /wa1 was a directory? In which case - it
would help to provide the requested files in the state where the problem
exists :-)

(also, one vs ell is confusing ... I assume you've got the right el^Wone :-)

Cheers,

Richard

>>
>> On Tuesday, August 06, 2019 11:09:32 AM Dennis Wicks wrote:
>>> Requested info attached:
>>>
>>> I *cannot* mount *any* partition on /wa1
>>> but I *can* mount *any* partition on any other mount point.
>>>
>>> Regards, and Thanks!
>>> Dennis
>>>
>>> Andrei POPESCU wrote on 8/6/19 1:06 AM:
>>>> On Lu, 05 aug 19, 15:33:57, Dennis Wicks wrote:
>>>>> It seems that something in the mount process does not like "wa1" for a
>>>>> mount point. Anybody have similar recent problems?
>>>>
>>>> Please show your fstab and the output of 'lsblk -f'.
>>>>
>>>> Kind regards,
>>>> Andrei
>>
>>
>>
> 

[toc] | [prev] | [next] | [standalone]

#212329

Richard Hector wrote on 8/6/19 12:42 PM:
> On 7/08/19 5:31 AM, Dennis Wicks wrote:
>> rhkramer@gmail.com wrote on 8/6/19 10:34 AM:
>>> I didn't fully understand your fstab, but is there a typo -- wa11 vs.
>>> wa1?
>> No. My current config is;
>>
>>     /wa1 -> wa11 ( soft link )
>>     /wa11        ( <- /dev/sdb2 )
>>
>> with sdb2 mounted on /wa11 so I don't have to find and change all the
>> paths that I have starting with "/wa1/..."!
> 
> So you're trying to mount on a symlink, instead of a directory? I don't
> think that's going to work. Why not mount on /wa11, as you describe?
> 
> Or does /wa11 only exist because you can't mount on /wa1, and you were
    Exactly!!
> trying to mount on /wa1 when /wa1 was a directory? In which case - it
> would help to provide the requested files in the state where the problem
> exists :-)
    fstab says wa1 but I would have to reboot to get the
    exact config back, and that takes over an hour!
> 
> (also, one vs ell is confusing ... I assume you've got the right el^Wone :-)
    Oh yeah! One of the many things I verified! Been using
    /wa1 for years as is. Keep copying the fstab so it is
    tried and true; until the last aptitude upgrade.
> 
> Cheers,
> 
> Richard
> 
>>>
>>> On Tuesday, August 06, 2019 11:09:32 AM Dennis Wicks wrote:
>>>> Requested info attached:
>>>>
>>>> I *cannot* mount *any* partition on /wa1
>>>> but I *can* mount *any* partition on any other mount point.
>>>>
>>>> Regards, and Thanks!
>>>> Dennis
>>>>
>>>> Andrei POPESCU wrote on 8/6/19 1:06 AM:
>>>>> On Lu, 05 aug 19, 15:33:57, Dennis Wicks wrote:
>>>>>> It seems that something in the mount process does not like "wa1" for a
>>>>>> mount point. Anybody have similar recent problems?
>>>>>
>>>>> Please show your fstab and the output of 'lsblk -f'.
>>>>>
>>>>> Kind regards,
>>>>> Andrei
>>>
>>>
>>>
>>
> 
> 

[toc] | [prev] | [next] | [standalone]

#212332

[Multipart message — attachments visible in raw view] — view raw

On 7/08/19 5:51 AM, Dennis Wicks wrote:
> Richard Hector wrote on 8/6/19 12:42 PM:
>> On 7/08/19 5:31 AM, Dennis Wicks wrote:
>>> rhkramer@gmail.com wrote on 8/6/19 10:34 AM:
>>>> I didn't fully understand your fstab, but is there a typo -- wa11 vs.
>>>> wa1?
>>> No. My current config is;
>>>
>>>     /wa1 -> wa11 ( soft link )
>>>     /wa11        ( <- /dev/sdb2 )
>>>
>>> with sdb2 mounted on /wa11 so I don't have to find and change all the
>>> paths that I have starting with "/wa1/..."!
>>
>> So you're trying to mount on a symlink, instead of a directory? I don't
>> think that's going to work. Why not mount on /wa11, as you describe?
>>
>> Or does /wa11 only exist because you can't mount on /wa1, and you were
>    Exactly!!
>> trying to mount on /wa1 when /wa1 was a directory? In which case - it
>> would help to provide the requested files in the state where the problem
>> exists :-)
>    fstab says wa1 but I would have to reboot to get the
>    exact config back, and that takes over an hour!

In that case, I suspect the problem was (somehow) with the former
directory /wa1, which no longer exists so we can't inspect it.

And if that's the case, you'd probably find you can just recreate it,
and everything will work :-)

Richard

[toc] | [prev] | [next] | [standalone]

#212321

Dennis Wicks composed on 2019-08-06 10:09 (UTC-0500):

> I *cannot* mount *any* partition on /wa1

What is output from ls -ld /wa*/ ?
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#212326

Felix Miata wrote on 8/6/19 10:33 AM:
> Dennis Wicks composed on 2019-08-06 10:09 (UTC-0500):
> 
>> I *cannot* mount *any* partition on /wa1
> 
> What is output from ls -ld /wa*/ ?
wix@dgwicks:/$ ls -ld /wa*/
drwxrwxrwx 17 root root 4096 Jun 17 14:07 /wa1/
drwxrwxrwx 17 root root 4096 Jun 17 14:07 /wa11/
drwxrwxrwx  8 root root  111 Jun 11 11:58 /wa2/
drwxr-xr-x  6 wix  wix    72 Jun 11 11:58 /wa3/
drwxr-xr-x 16 root root 4096 Feb  2  2019 /wa4/
wix@dgwicks:/$
> 

[toc] | [prev] | [next] | [standalone]

#212319

Hi,

Dennis Wicks wrote:
> I *cannot* mount *any* partition on /wa1
> but I *can* mount *any* partition on any other mount point.

So what do you get from these shell commands ?

  ls -ld /wa1 /wa11

  find /wa1

What happens if you create a new /wa1 ?

  mv /wa1 /wa1_old
  mkdir /wa1
  mount /dev/sdb2 /wa1

--------------------------------------------------------------------

As for your fstab, there is this "x-systemd.device-timeout=20" where
all others have "=60". But the web says this is for automounting.

I fail to imagine any explanation for the symptoms you report. Especially
the silent failure riddles me.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#212325

Thomas Schmitt wrote on 8/6/19 10:30 AM:
> Hi,
> 
> Dennis Wicks wrote:
>> I *cannot* mount *any* partition on /wa1
>> but I *can* mount *any* partition on any other mount point.
> 
> So what do you get from these shell commands ?
I am currently running with "ln -s /wa11 /wa1" so this isn't 
the config I booted with. Anyway;
> 
>    ls -ld /wa1 /wa11

wix@dgwicks:~$ ls -ld /wa1 /wa11
lrwxrwxrwx  1 root root    4 Aug  1 17:40 /wa1 -> wa11
drwxrwxrwx 17 root root 4096 Jun 17 14:07 /wa11
wix@dgwicks:~$

> 
>    find /wa1

wix@dgwicks:~$ cd /
wix@dgwicks:/$ find /wa1
/wa1
wix@dgwicks:/$ lg wa1
lrwxrwxrwx   1 root root     4 Aug  1 17:40 wa1 -> wa11/
drwxrwxrwx  17 root root  4.0K Jun 17 14:07 wa11/
lrwxrwxrwx   1 root root     7 Aug  1 17:43 www -> wa1/www/
wix@dgwicks:/$

> 
> What happens if you create a new /wa1 ?
> 
>    mv /wa1 /wa1_old
>    mkdir /wa1
>    mount /dev/sdb2 /wa1
> 

Same failure. One of the many things I tried to get the 
mount on /wa1 to work, without any success.

> --------------------------------------------------------------------
> 
> As for your fstab, there is this "x-systemd.device-timeout=20" where
> all others have "=60". But the web says this is for automounting.

This param is to stop the boot process from stopping because 
all of the mounts have failed, temporarily. A previous 
thread from a few weeks(?) back.
> 
> I fail to imagine any explanation for the symptoms you report. Especially
> the silent failure riddles me.
> 
Me too! Happens during boot and when done manually!
> 
> Have a nice day :)
>
Thanks! You too!

> Thomas
> 
Regards!
Dennis

[toc] | [prev] | [next] | [standalone]

#212333

On Tue 06 Aug 2019 at 12:18:21 (-0500), Dennis Wicks wrote:
> Thomas Schmitt wrote on 8/6/19 10:30 AM:
> > Dennis Wicks wrote:
> > > I *cannot* mount *any* partition on /wa1
> > > but I *can* mount *any* partition on any other mount point.
> > 
> > So what do you get from these shell commands ?
> I am currently running with "ln -s /wa11 /wa1" so this isn't the
> config I booted with. Anyway;
> > 
> >    ls -ld /wa1 /wa11
> 
> wix@dgwicks:~$ ls -ld /wa1 /wa11
> lrwxrwxrwx  1 root root    4 Aug  1 17:40 /wa1 -> wa11
> drwxrwxrwx 17 root root 4096 Jun 17 14:07 /wa11
> wix@dgwicks:~$
> 
> > 
> >    find /wa1
> 
> wix@dgwicks:~$ cd /
> wix@dgwicks:/$ find /wa1
> /wa1
> wix@dgwicks:/$ lg wa1
> lrwxrwxrwx   1 root root     4 Aug  1 17:40 wa1 -> wa11/
> drwxrwxrwx  17 root root  4.0K Jun 17 14:07 wa11/
> lrwxrwxrwx   1 root root     7 Aug  1 17:43 www -> wa1/www/
> wix@dgwicks:/$
> 
> > 
> > What happens if you create a new /wa1 ?
> > 
> >    mv /wa1 /wa1_old
> >    mkdir /wa1
> >    mount /dev/sdb2 /wa1
> > 
> 
> Same failure. One of the many things I tried to get the mount on /wa1
> to work, without any success.

Shouldn't that fail with:

~# mkdir /wa1
~# mount /dev/sda4 /wa1
mount: /dev/sda4 is already mounted or /wa1 busy
       /dev/sda4 is already mounted on /ya
~# 

> > --------------------------------------------------------------------
> > 
> > As for your fstab, there is this "x-systemd.device-timeout=20" where
> > all others have "=60". But the web says this is for automounting.
> 
> This param is to stop the boot process from stopping because all of
> the mounts have failed, temporarily. A previous thread from a few
> weeks(?) back.
> > 
> > I fail to imagine any explanation for the symptoms you report. Especially
> > the silent failure riddles me.

Unfortunately there's too much reported speech in this thread,
and not enough direct speech. Some timely copy/paste might help.

> Me too! Happens during boot and when done manually!

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#212381

David Wright wrote on 8/6/19 1:48 PM:
> On Tue 06 Aug 2019 at 12:18:21 (-0500), Dennis Wicks wrote:
>> Thomas Schmitt wrote on 8/6/19 10:30 AM:
>>> Dennis Wicks wrote:
>>>> I *cannot* mount *any* partition on /wa1
>>>> but I *can* mount *any* partition on any other mount point.
>>>
>>> So what do you get from these shell commands ?
>> I am currently running with "ln -s /wa11 /wa1" so this isn't the
>> config I booted with. Anyway;
>>>
>>>     ls -ld /wa1 /wa11
>>
>> wix@dgwicks:~$ ls -ld /wa1 /wa11
>> lrwxrwxrwx  1 root root    4 Aug  1 17:40 /wa1 -> wa11
>> drwxrwxrwx 17 root root 4096 Jun 17 14:07 /wa11
>> wix@dgwicks:~$
>>
>>>
>>>     find /wa1
>>
>> wix@dgwicks:~$ cd /
>> wix@dgwicks:/$ find /wa1
>> /wa1
>> wix@dgwicks:/$ lg wa1
>> lrwxrwxrwx   1 root root     4 Aug  1 17:40 wa1 -> wa11/
>> drwxrwxrwx  17 root root  4.0K Jun 17 14:07 wa11/
>> lrwxrwxrwx   1 root root     7 Aug  1 17:43 www -> wa1/www/
>> wix@dgwicks:/$
>>
>>>
>>> What happens if you create a new /wa1 ?
>>>
>>>     mv /wa1 /wa1_old
>>>     mkdir /wa1
>>>     mount /dev/sdb2 /wa1
>>>
>>
>> Same failure. One of the many things I tried to get the mount on /wa1
>> to work, without any success.
> 
> Shouldn't that fail with:
> 
> ~# mkdir /wa1
> ~# mount /dev/sda4 /wa1
> mount: /dev/sda4 is already mounted or /wa1 busy
>         /dev/sda4 is already mounted on /ya
> ~#

No, it won't fail because the first mount to /wa1 did not 
succeed! And the system does not object or give an error 
when you mount the same partition on two diff dirs anyway!

> 
>>> --------------------------------------------------------------------
>>>
>>> As for your fstab, there is this "x-systemd.device-timeout=20" where
>>> all others have "=60". But the web says this is for automounting.
>>
>> This param is to stop the boot process from stopping because all of
>> the mounts have failed, temporarily. A previous thread from a few
>> weeks(?) back.
>>>
>>> I fail to imagine any explanation for the symptoms you report. Especially
>>> the silent failure riddles me.
> 
> Unfortunately there's too much reported speech in this thread,
> and not enough direct speech. Some timely copy/paste might help.
> 
>> Me too! Happens during boot and when done manually!
> 
> Cheers,
> David.
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#212383

On Wed, Aug 07, 2019 at 12:44:39PM -0500, Dennis Wicks wrote:
> And the
> system does not object or give an error when you mount the same partition on
> two diff dirs anyway!

Sadly.  And *very* surprisingly.  You can only wish that it did.

[toc] | [prev] | [next] | [standalone]

#212387

On Wed 07 Aug 2019 at 12:44:39 (-0500), Dennis Wicks wrote:
> David Wright wrote on 8/6/19 1:48 PM:
> > On Tue 06 Aug 2019 at 12:18:21 (-0500), Dennis Wicks wrote:
> > > Thomas Schmitt wrote on 8/6/19 10:30 AM:
> > > > Dennis Wicks wrote:
> > > > > I *cannot* mount *any* partition on /wa1
> > > > > but I *can* mount *any* partition on any other mount point.
> > > > 
> > > > So what do you get from these shell commands ?
> > > I am currently running with "ln -s /wa11 /wa1" so this isn't the
> > > config I booted with. Anyway;
> > > > 
> > > >     ls -ld /wa1 /wa11
> > > 
> > > wix@dgwicks:~$ ls -ld /wa1 /wa11
> > > lrwxrwxrwx  1 root root    4 Aug  1 17:40 /wa1 -> wa11
> > > drwxrwxrwx 17 root root 4096 Jun 17 14:07 /wa11
> > > wix@dgwicks:~$
> > > 
> > > > 
> > > >     find /wa1
> > > 
> > > wix@dgwicks:~$ cd /
> > > wix@dgwicks:/$ find /wa1
> > > /wa1
> > > wix@dgwicks:/$ lg wa1
> > > lrwxrwxrwx   1 root root     4 Aug  1 17:40 wa1 -> wa11/
> > > drwxrwxrwx  17 root root  4.0K Jun 17 14:07 wa11/
> > > lrwxrwxrwx   1 root root     7 Aug  1 17:43 www -> wa1/www/
> > > wix@dgwicks:/$
> > > 
> > > > 
> > > > What happens if you create a new /wa1 ?
> > > > 
> > > >     mv /wa1 /wa1_old
> > > >     mkdir /wa1
> > > >     mount /dev/sdb2 /wa1
> > > > 
> > > 
> > > Same failure. One of the many things I tried to get the mount on /wa1
> > > to work, without any success.
> > 
> > Shouldn't that fail with:
> > 
> > ~# mkdir /wa1
> > ~# mount /dev/sda4 /wa1
> > mount: /dev/sda4 is already mounted or /wa1 busy
> >         /dev/sda4 is already mounted on /ya
> > ~#
> 
> No, it won't fail because the first mount to /wa1 did not succeed!

No, but your sdb2 is already mounted (on /wa11):

sdb
├─sdb1 xfs      PubDtaMaster 4283d59b-8e0b-4f6a-ad33-47dff4e2198c   32.7G    86% /edrv
└─sdb2 xfs      Work-Area-1  20173008-eeaa-41cd-b862-f7d0b871895d  241.9G    65% /wa11

> And
> the system does not object or give an error when you mount the same
> partition on two diff dirs anyway!

Mine does: I just posted it.

> > > > --------------------------------------------------------------------
> > > > 
> > > > As for your fstab, there is this "x-systemd.device-timeout=20" where
> > > > all others have "=60". But the web says this is for automounting.
> > > 
> > > This param is to stop the boot process from stopping because all of
> > > the mounts have failed, temporarily. A previous thread from a few
> > > weeks(?) back.
> > > > 
> > > > I fail to imagine any explanation for the symptoms you report. Especially
> > > > the silent failure riddles me.
> > 
> > Unfortunately there's too much reported speech in this thread,
> > and not enough direct speech. Some timely copy/paste might help.

And, once again, you post *reports* of what is supposed to have happened.

BTW what is lg?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#212336

Hi,

more ideas: exit value, verbous mode.

  mount -v /dev/sdc /wa1
  echo $?

A nominally successful mount command would yield 0 as "$?".
Maybe -v yields some extra insight.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#212384

Thomas Schmitt wrote on 8/6/19 1:58 PM:
> Hi,
> 
> more ideas: exit value, verbous mode.
> 
>    mount -v /dev/sdc /wa1
>    echo $?
> 
> A nominally successful mount command would yield 0 as "$?".
> Maybe -v yields some extra insight.
> 
> 
> Have a nice day :)
> 
> Thomas
> 
> 
> 
Thanks, Thomas!
I'll put a note in my fstab so the next time I boot I can 
find it if the mount fails again!

You too!
Dennnis

[toc] | [prev] | [next] | [standalone]

#212389

Hi,

i wrote:
> >    mount -v /dev/sdc /wa1
> >    echo $?

Duh. "/dev/sdb2", not "/dev/sdc".
(Do as i mean, not as i write.)


Dennis Wicks wrote:
> I'll put a note in my fstab so the next time I boot I can find it if the
> mount fails again!

Did i miss the report about some miracle cure beyond the link to /wa11 ?


I did a search for "wa1" in Linux kernel git.
  https://github.com/torvalds/linux/search?utf8=%E2%9C%93&q=wa1&type=
The name seems not to be hardcoded there.
So my best guess is that it is mistaken by mount(8) for something other
than a target path.

This opportunity to be mistaken could be excluded by a test program
which uses mount(2).
I tested this program "ts_mount.c":

-------------------------------------------------------------------------
#include <stdio.h>
#include <stdlib.h>
#include <sys/mount.h>
#include <errno.h>
#include <string.h>

int main()
{
 int ret;

 ret = mount("/dev/sr4", "/mnt/iso", "iso9660", MS_RDONLY, "");
 if(ret == 0) {
   printf("Success\n");
   exit(0);
 }
 printf("Failed\n");
 printf("errno= %d (%s)\n", errno, strerror(errno));
 exit(1);
}
-------------------------------------------------------------------------

with a DVD drive by:

  cc -g -Wall -o ts_mount ts_mount.c
  ./ts_mount

As normal user i got

  Failed
  errno= 1 (Operation not permitted)

and as superuser

  Success

Drive noise and listed files confirm the optimistic message.
Without medium i get

  Failed
  errno= 123 (No medium found)


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#212410

On 2019-08-05, Dennis Wicks <wix@mgssub.com> wrote:
>
>
> So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it 
> seemed to finish successfully, but "ls /wa1" indicated that 
> in fact it had not. Nothing mounted on wa1! Many other tests 
> told me the same thing. "umount /wa1" said "not mounted"!

Would this be the result if /dev/sdb2 were already mounted (i.e. nothing?).

Many other tests. What about 'mount' from an xterm to see what's mounted
and what ain't and where?

Did you show your /etc/fstab file (cut and paste)? If so, I must've missed
it.

BTW, what's with the exclamation points? Makes you seem enthusiastic.

;-)


-- 
“We are all in the gutter, but some of us are looking at the stars.” 
― Oscar Wilde, Lady Windermere's Fan

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web