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

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

Corruption of Samba mount points

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

Contents

  Corruption of Samba mount points Joe <joe@jretrading.com> - 2020-11-18 22:50 +0100
    Re: Corruption of Samba mount points David Wright <deblis@lionunicorn.co.uk> - 2020-11-19 02:30 +0100
      Re: Corruption of Samba mount points Joe <joe@jretrading.com> - 2020-11-19 09:50 +0100
        Re: Corruption of Samba mount points songbird <songbird@anthive.com> - 2020-11-19 15:00 +0100
          Re: Corruption of Samba mount points Joe <joe@jretrading.com> - 2020-11-19 16:40 +0100

#228768 — Corruption of Samba mount points

It began with booting this morning. No wallpaper. No network shares
mounted (they are set to automount using systemd, but if I tried
accessing most of them, the error message contained the path of the
mount point followed by 'no such device'.

The mount points looked OK in a GUI file manager and also with mc. Doing
an ls-l of the parent directory showed a few mount points as normal, the
others showed the name and the 'd' of the permissions string, but
everything else was '?' marks.

Eventually tried umounting the affected points, and all was well after
that.

The same thing happened at the next boot of the day, it wasn't an
ephemeral glitch, though the mount points affected weren't exactly the
same ones.

I assume one of the upgrades to sid last night was responsible for
this, other computers have no problem seeing the same shares. Anyone
else seeing it, Google doesn't seem to find anything?

-- 
Joe

[toc] | [next] | [standalone]

#228772

On Wed 18 Nov 2020 at 21:41:30 (+0000), Joe wrote:
> It began with booting this morning. No wallpaper. No network shares
> mounted (they are set to automount using systemd, but if I tried
> accessing most of them, the error message contained the path of the
> mount point followed by 'no such device'.
> 
> The mount points looked OK in a GUI file manager and also with mc. Doing
> an ls-l of the parent directory showed a few mount points as normal, the
> others showed the name and the 'd' of the permissions string, but
> everything else was '?' marks.
> 
> Eventually tried umounting the affected points, and all was well after
> that.
> 
> The same thing happened at the next boot of the day, it wasn't an
> ephemeral glitch, though the mount points affected weren't exactly the
> same ones.
> 
> I assume one of the upgrades to sid last night was responsible for
> this, other computers have no problem seeing the same shares. Anyone
> else seeing it, Google doesn't seem to find anything?

I don't know if it helps to know that you need x permission to see any
more in a directory than, eg:

total 0
d????????? ? ? ? ?            ? DCIM
d????????? ? ? ? ?            ? MISC
-????????? ? ? ? ?            ? README

Cheers,
David.

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

#228774

On Wed, 18 Nov 2020 19:26:59 -0600
David Wright <deblis@lionunicorn.co.uk> wrote:

> On Wed 18 Nov 2020 at 21:41:30 (+0000), Joe wrote:
> > It began with booting this morning. No wallpaper. No network shares
> > mounted (they are set to automount using systemd, but if I tried
> > accessing most of them, the error message contained the path of the
> > mount point followed by 'no such device'.
> > 
> > The mount points looked OK in a GUI file manager and also with mc.
> > Doing an ls-l of the parent directory showed a few mount points as
> > normal, the others showed the name and the 'd' of the permissions
> > string, but everything else was '?' marks.
> > 
> > Eventually tried umounting the affected points, and all was well
> > after that.
> > 
> > The same thing happened at the next boot of the day, it wasn't an
> > ephemeral glitch, though the mount points affected weren't exactly
> > the same ones.
> > 
> > I assume one of the upgrades to sid last night was responsible for
> > this, other computers have no problem seeing the same shares. Anyone
> > else seeing it, Google doesn't seem to find anything?  
> 
> I don't know if it helps to know that you need x permission to see any
> more in a directory than, eg:
> 
> total 0
> d????????? ? ? ? ?            ? DCIM
> d????????? ? ? ? ?            ? MISC
> -????????? ? ? ? ?            ? README
>
Thanks, no, I didn't know that, never encountered it before.

That simplifies things a bit: so some of these mounts are being
deliberately made by root during boot. They are all automount, so
should never mount until a file is called for, and they are all data so
there is no possible reason for them to be needed during boot. Finally,
it worked for years until yesterday morning. Same again today, so last
night's upgrades didn't fix it.

No other replies, so I assume this is another of My Personal Bugs. I've
reported a few bugs over the years that have turned out to be visible
only to me. I don't suppose there are any two identical installations
of sid anywhere in the world.

Maybe this is a hint that it's time to reinstall, this installation is
probably at least ten years old, and there have been about nine
packages that can't be upgraded for a couple of months now. But that's
going to be the best part of a day that I can't really spare...

-- 
Joe

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

#228776

Joe wrote:
...
> No other replies, so I assume this is another of My Personal Bugs. I've
> reported a few bugs over the years that have turned out to be visible
> only to me. I don't suppose there are any two identical installations
> of sid anywhere in the world.
>
> Maybe this is a hint that it's time to reinstall, this installation is
> probably at least ten years old, and there have been about nine
> packages that can't be upgraded for a couple of months now. But that's
> going to be the best part of a day that I can't really spare...

  if the hardware is that old it may be having issues or a
cable connection is loose or something else.  that is what
can be tough about such a failure.  adding unstable to that
well, as they say, sometimes you get to keep all the parts
of what is broken.  :)

  i only run a few bits of unstable (firefox and a few 
other very isolated leaf packages) and always have another
partition on another device that will boot stable and also
yet another stable setup on a USB stick, besides the 
netinst image on a USB stick that will boot a rescue 
prompt if needed.  so far i haven't had to use them often
but when i've had to check something out or compare what
was going on in stable compared to testing it was a welcome
help.

  good luck!  :)


  songbird

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

#228778

On Thu, 19 Nov 2020 08:40:35 -0500
songbird <songbird@anthive.com> wrote:

> Joe wrote:
> ...
> > No other replies, so I assume this is another of My Personal Bugs.
> > I've reported a few bugs over the years that have turned out to be
> > visible only to me. I don't suppose there are any two identical
> > installations of sid anywhere in the world.
> >
> > Maybe this is a hint that it's time to reinstall, this installation
> > is probably at least ten years old, and there have been about nine
> > packages that can't be upgraded for a couple of months now. But
> > that's going to be the best part of a day that I can't really
> > spare...  
> 
>   if the hardware is that old it may be having issues or a
> cable connection is loose or something else.  that is what
> can be tough about such a failure.  adding unstable to that
> well, as they say, sometimes you get to keep all the parts
> of what is broken.  :)

I didn't say the hardware was ten years old, just the Debian
installation. You can often just move a hard drive to a new motherboard
[of the same architecture] and have it boot fairly well, with just a few
bits of messing about to restore full functionality. 

Hardware failures will normally cause unpredictable software failures,
I've seen the same problem three times now. It's some form of software
rot.
> 
>   i only run a few bits of unstable (firefox and a few 
> other very isolated leaf packages) and always have another
> partition on another device that will boot stable and also
> yet another stable setup on a USB stick, besides the 
> netinst image on a USB stick that will boot a rescue 
> prompt if needed.  so far i haven't had to use them often
> but when i've had to check something out or compare what
> was going on in stable compared to testing it was a welcome
> help.

I have two buster installations on netbooks and another on a laptop,
with a spare desktop currently containing my final jessie server before
the upgrade to a new stretch hard drive which now runs my HP
Microserver. I'm not short of spare computers. I even have a new
Raspberry Pi 4 which will become one of the new servers to replace the
Microserver in due course.
> 
>   good luck!  :)

Thank you.

-- 
Joe

[toc] | [prev] | [standalone]

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

csiph-web