All of lore.kernel.org
 help / color / mirror / Atom feed
From: Donald Buczek <buczek@molgen.mpg.de>
To: Ian Kent <raven@themaw.net>
Cc: Alexander Viro <aviro@redhat.com>, autofs <autofs@vger.kernel.org>
Subject: Re: "Too many levels of symbolic links"
Date: Sun, 02 Mar 2014 11:22:39 +0100	[thread overview]
Message-ID: <5313066F.6040302@molgen.mpg.de> (raw)
In-Reply-To: <1393753284.9725.31.camel@perseus.fritz.box>

[-- Attachment #1: Type: text/plain, Size: 4279 bytes --]

Am 02.03.2014 10:41, schrieb Ian Kent:
> On Sun, 2014-03-02 at 09:28 +0100, Donald Buczek wrote:
>> Am 02.03.2014 03:17, schrieb Ian Kent:
>>> mnt_hash->next == mnt_hash->prev, mount has been unlinked from the mount
>>> tree so is not "visible". As far as we are concerned this mount has
>>> gone.
>> No, prev and next both point to the list_head in the mount_hashtable.
> Fair call, ->mnt_mp != NULL too which implies the mount hasn't been
> unlinked.

The problem is, that the mount is in another namespace. I've put mnt_ns 
into my perl script:

> root:kasslerbraten:/home/buczek/autofs/# ./peekmounts |grep mariux32
>  mountpoint 0xffff880125e44480 : count=   1 denty=0xffff88007c86da10 
> (mariux32)
>  struct mount 0xffff8800a3a9a6c0 : mountpoint dentry 
> 0xffff88007c86da10 (mariux32) mountpoint struct 0xffff880125e44480 NS 
> 0xffff8801271f9300
> root:kasslerbraten:/home/buczek/autofs/# ./peekmounts |grep project
>  mountpoint 0xffff8800c1d068a0 : count=   2 denty=0xffff8800c8b2e450 
> (project)
>  struct mount 0xffff8800c9e5e200 : mountpoint dentry 
> 0xffff8800c8b2e450 (project) mountpoint struct 0xffff8800c1d068a0 NS 
> 0xffff88012d00ed00
>  struct mount 0xffff8800a3a9a940 : mountpoint dentry 
> 0xffff8800c8b2e450 (project) mountpoint struct 0xffff8800c1d068a0 NS 
> 0xffff8801271f9300

We have a /project without a mounted /project/mariux32 and a /project 
with a mounted /project/mariux32 in another namespace.

This goes in the direction you mentioned in your other mail ("Illegal as 
far as autofs is concerned because an autofs mount is strictly 
associated with a path defined by its map") The system-wide, absolute 
semantics of pathnames in the automount world don't fit well into the 
process-local, relative mount semantics of the kernel.

I still don't know, where these "root" or "old-root" messages come from, 
but again the error occured after these strange messages appeared

> 2014-02-28T12:33:08.461073+01:00 kasslerbraten kernel: [13093.129511] 
> pid 7670: d_set_mounted: set mounted on dentry=ffff88007ca58a50 root
> 2014-02-28T12:33:08.461074+01:00 kasslerbraten kernel: [13093.129569] 
> pid 7670: put_mountpoint: mp=ffff8801271f9338
> 2014-02-28T12:33:08.461075+01:00 kasslerbraten kernel: [13093.129574] 
> pid 7670: d_set_mounted: dentry=ffff8800c890ce10 tmp
> 2014-02-28T12:33:08.461076+01:00 kasslerbraten kernel: [13093.129575] 
> pid 7670: d_set_mounted: set mounted on dentry=ffff8800c890ce10 tmp
> 2014-02-28T12:33:08.461077+01:00 kasslerbraten kernel: [13093.129578] 
> pid 7670: put_mountpoint: mp=ffff8801271f9338
> 2014-02-28T12:33:08.461078+01:00 kasslerbraten kernel: [13093.129599] 
> pid 7670: d_set_mounted: dentry=ffff88007ca407d0 old-root-D0k5jB
> 2014-02-28T12:33:08.461079+01:00 kasslerbraten kernel: [13093.129601] 
> pid 7670: d_set_mounted: set mounted on dentry=ffff88007ca407d0 
> old-root-D0k5jB
> 2014-02-28T12:33:08.461080+01:00 kasslerbraten kernel: [13093.129602] 
> pid 7670: put_mountpoint: mp=ffff8800c9e5e750
> 2014-02-28T12:33:08.461081+01:00 kasslerbraten kernel: [13093.129603] 
> pid 7670: put_mountpoint: cleared mounted on dentry=ffff88007ca58a50 root
> 2014-02-28T12:33:08.461082+01:00 kasslerbraten kernel: [13093.129604] 
> pid 7670: put_mountpoint: mp=ffff8800c9e5e610
> 2014-02-28T12:33:08.461082+01:00 kasslerbraten kernel: [13093.129662] 
> pid 7670: put_mountpoint: mp=0000014800450045
> 2014-02-28T12:33:08.461083+01:00 kasslerbraten kernel: [13093.129663] 
> pid 7670: put_mountpoint: mp=0000000000000006

(as explained in another mail , the addresses of "mp=" are wrong, so 
don't worry about these)

This looks like chroot or somesuch. But I have no idea. I don't find 
\"root or \"old- in any sources. There is not "root" in any map.

Hmmm. Isn't the daemon doing lazy umounts? Could it be this?
I've compiled the daemon with --enable-ignore-busy
Anything forcing the daemon to restart?
systemd doing stupid things to the daemon or the filesystem?

> [Service]
> Type=forking
> ExecStartPre=/sbin/make-automaps
> ExecStart=/usr/sbin/automount -v
> PIDFile=/run/autofs-running
> ExecReload=/bin/kill -HUP $MAINPID

   Donald

-- 
Donald Buczek
buczek@molgen.mpg.de
Tel: +49 30 8413 1433



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4541 bytes --]

  reply	other threads:[~2014-03-02 10:22 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 16:02 autofs linux 3.8.13 and "Too many levels of symbolic links" Donald Buczek
2014-01-29 17:16 ` Leonardo Chiquitto
2014-01-30  0:19 ` Ian Kent
2014-01-30 10:28   ` Donald Buczek
2014-01-30 14:30     ` Ian Kent
2014-01-31  1:36       ` Ian Kent
2014-01-31  3:31 ` Ian Kent
2014-01-31  5:13   ` Ian Kent
2014-01-31 10:10     ` Donald Buczek
2014-01-31 10:29       ` Donald Buczek
2014-02-19 10:17         ` Donald Buczek
2014-02-19 10:21           ` Donald Buczek
2014-02-20 11:41           ` Ian Kent
2014-02-20 12:18             ` Ian Kent
2014-02-20 15:57               ` Donald Buczek
2014-02-21  1:42                 ` Ian Kent
2014-02-21 15:15                   ` Donald Buczek
2014-02-28 12:12                     ` Donald Buczek
2014-02-28 13:29                       ` Alexander Viro
2014-02-28 20:35                         ` Donald Buczek
2014-03-01 21:56                           ` Donald Buczek
2014-03-02  0:52                             ` Donald Buczek
2014-03-02  2:17                               ` Ian Kent
2014-03-02  8:28                                 ` Donald Buczek
2014-03-02  9:41                                   ` Ian Kent
2014-03-02 10:22                                     ` Donald Buczek [this message]
2014-03-02 11:03                                       ` Ian Kent
2014-03-02 11:15                                         ` Donald Buczek
2014-03-02 11:30                                           ` Ian Kent
2014-03-02 11:35                                             ` Ian Kent
2014-03-02 11:25                                         ` Ian Kent
2014-03-02  2:22                         ` Ian Kent
2014-03-02  7:10                           ` Ian Kent
2014-03-02 14:55                             ` Donald Buczek
2014-03-02 18:51                               ` Donald Buczek
2014-03-03  2:40                                 ` Ian Kent
2014-03-03  2:40                               ` Ian Kent
2014-03-04  6:06                                 ` Ian Kent
2016-03-09 17:44                                   ` Donald Buczek
2016-03-16  1:32                                     ` Ian Kent
2016-03-16  1:58                                     ` Ian Kent
2016-03-16  2:10                                     ` Ian Kent
2016-05-20 14:12                                       ` Donald Buczek
2016-05-23  1:53                                         ` Ian Kent
2014-02-01  1:47       ` autofs linux 3.8.13 and " Ian Kent
2014-02-01  3:32       ` Ian Kent
2014-02-01 13:08         ` Donald Buczek
2014-02-01  2:57 ` Ian Kent
2014-02-01 13:01   ` Donald Buczek
2014-02-02  3:45     ` Ian Kent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5313066F.6040302@molgen.mpg.de \
    --to=buczek@molgen.mpg.de \
    --cc=autofs@vger.kernel.org \
    --cc=aviro@redhat.com \
    --cc=raven@themaw.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.