1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

File system loop detected

Discussion in 'Plesk 11.x for Linux' started by Win2Pa, Sep 19, 2012.

  1. Win2Pa

    Win2Pa New Pleskian

    10
    35%
    Joined:
    Sep 19, 2012
    Messages:
    5
    Likes Received:
    0
    I do not know how this happened though. When I use find command on shell, I got the following error.

    find: File system loop detected; `/var/named/chroot/var/named' is part of the same file system loop as `/var/named'.

    It is minimal CentOS6.3 install with plesk 11. Any help would be appreciated.

    Thanks,
    Win2
     
  2. abdi

    abdi Platinum Pleskian

    31
    18%
    Joined:
    May 14, 2006
    Messages:
    2,913
    Likes Received:
    60
    Do

    ls -ldi /var/named/chroot/var/named/ /var/named


    and see if the inode numbers are the same (they shouldn't be). If they are then you need to remove the /var/named/chroot/var/named/ hard link and recreate it as a directory.
     
  3. Win2Pa

    Win2Pa New Pleskian

    10
    35%
    Joined:
    Sep 19, 2012
    Messages:
    5
    Likes Received:
    0
    Thanks for your reply abdi,

    Here is the output
    [root@serverone ~]# ls -ldi /var/named/chroot/var/named/ /var/named
    6684673 drwxr-x--- 6 root named 4096 Sep 7 17:17 /var/named
    6684673 drwxr-x--- 6 root named 4096 Sep 7 17:17 /var/named/chroot/var/named/

    Do I need to copy the content of /var/named to the newly created /var/named/chroot/var/named ?

    Thanks
     
  4. Win2Pa

    Win2Pa New Pleskian

    10
    35%
    Joined:
    Sep 19, 2012
    Messages:
    5
    Likes Received:
    0
    I still have no clue how to fix it. I would like to know any proper way of fixing file loop. Thanks in advance.
     
  5. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    Is it Virtuozzo container?
     
  6. Win2Pa

    Win2Pa New Pleskian

    10
    35%
    Joined:
    Sep 19, 2012
    Messages:
    5
    Likes Received:
    0
    No, it is not Virtuozzo container. Plesk panel 11 is installed on HP server with CentOS6.3 minimum install. Plesk setup install all the require packages.
     
  7. Faris Raouf

    Faris Raouf Silver Pleskian Plesk Guru

    31
    30%
    Joined:
    Mar 15, 2009
    Messages:
    667
    Likes Received:
    17
    We've seen this loop in a VZ container with Centos 6.x. It is annoying.

    I thought there may have been an issue with the template. But if you are having it in a non-VZ system, maybe it is something else.
     
  8. Win2Pa

    Win2Pa New Pleskian

    10
    35%
    Joined:
    Sep 19, 2012
    Messages:
    5
    Likes Received:
    0
    Yes it is same thing happened on hardware installation. Hopefully plesk will provide us some proper solution to fix it.
     
  9. SouthO

    SouthO New Pleskian

    22
    23%
    Joined:
    Jul 19, 2008
    Messages:
    6
    Likes Received:
    0
    Location:
    San Diego
    Just adding that I experienced this from a clean plesk11 / centos 6.x 64b install. It's the panel install.
     
  10. Azurel

    Azurel Regular Pleskian

    21
    57%
    Joined:
    Jan 29, 2013
    Messages:
    431
    Likes Received:
    1
    Location:
    Germany
    Same here with fresh centOS 6.4 and Plesk 11.0.9.
     
  11. Antonio Sanchez

    Antonio Sanchez Basic Pleskian

    20
    57%
    Joined:
    May 7, 2009
    Messages:
    28
    Likes Received:
    0
    I have this issue into a Container.

    Virtuozzo 4.7. CentOS 6.3

    Code:
    du: WARNING: Circular directory structure.
    This almost certainly means that you have a corrupted file system.
    NOTIFY YOUR SYSTEM MANAGER.
    The following directory is part of the cycle:
      `./var/named/chroot/var/named'
    Any news?
     
  12. Russell-SchoolsICT

    Russell-SchoolsICT Regular Pleskian

    22
    40%
    Joined:
    Oct 18, 2011
    Messages:
    109
    Likes Received:
    0
    Location:
    United Kingdom
    Whilst investigating Plesks Backup not working on our system and checking partitions we have received this same error.

    Parallels Plesk Panel 11.5.30 MU #5 CentOS 6.3 (Final) 64bit NOT in a container .
     
  13. Roberto Nunez

    Roberto Nunez Basic Pleskian

    20
    57%
    Joined:
    Apr 30, 2009
    Messages:
    42
    Likes Received:
    0
    Location:
    World
    Hello,
    I have the same issue CentOS 6.4 64bits, after upgrade to Plesk 11.5.30.

    find: File system loop detected; `/var/named/chroot/var/named' is part of the same file system loop as `/var/named'.

    Thanks for any help!

    P.S: Not Virtuozzo.
     
    Last edited: Aug 12, 2013
  14. Chris Buckley

    Chris Buckley Basic Pleskian

    23
     
    Joined:
    Mar 24, 2009
    Messages:
    28
    Likes Received:
    0
    We've got this exact same problem today. What's the solution? It's very annoying that there are lots of people on this thread with the same problem but yet nobody has posted how to fix it!

    When we run:

    ls -ldi /var/named/chroot/var/named/ /var/named

    The inode numbers are the same, but we don't know what to do next. Trying unlink gives the message "cannot unlink : Is a directory".

    Help!
     
  15. AlbertoGd

    AlbertoGd New Pleskian

    6
    60%
    Joined:
    Sep 28, 2013
    Messages:
    5
    Likes Received:
    0
    I´m surprised to see this post and without any solution...

    This problem was reported in Red Hat Bugzilla last year, and is fixed in coreutils-8.4-23.el6. Now we have coreutils-19.el6_4.2, so we´ll have to wait. Although there is no problem, only a false alarm when named process is running. I think the fix is an implementation in coreutils to detect bind-mount-induced directory cycle.

    In conclusion, there is nothing wrong. Only a false alarm. If you want more info, check the bug description here.
     
  16. _Alberto_

    _Alberto_ New Pleskian

    3
    70%
    Joined:
    May 22, 2014
    Messages:
    5
    Likes Received:
    0
    Hi, same issue here with CentOS 6.5 x64 and Plesk 11.5.30

    Is there any way to skip this annoying message?

    Thanks!
     
  17. F_H

    F_H New Pleskian

    1
     
    Joined:
    Nov 28, 2015
    Messages:
    1
    Likes Received:
    0
    This is a bigger issue with PBAS/OBAS since find returns a "1" return code and this breaks the addition of new nameservers in OBAS.

    I've had to temporarly disable bind chrooting.
    (yum remove bind-chroot and comment in the /etc/sysconfig/named
    [...]
    #ROOTDIR=/var/named/chroot


    Makes me angry since already required to disable SELINUX and now chrooting also.
    Please test better and focus on integrating better in "secure" systems.
    You gotta consider this is just the default setup of a off-the-shelf linux distribution, not something very hardened.
     
  18. Ethan_K

    Ethan_K New Pleskian

    3
     
    Joined:
    Aug 25, 2014
    Messages:
    2
    Likes Received:
    0
    The problem is caused by the init script of named which mounts the /var/named directory over /var/named/chroot. The solution for this problem too is present in the init script.
    +++++++
    ...
    mount_chroot_conf()
    {
    ...
    # Mount source is a directory. Mount it only if directory in chroot is
    # empty.
    ...
    +++++++

    As mentioned above the mount function will work only if the directory is empty. So use the below solution:

    1. Stop named
    2. Create the directory /var/named/chroot/var/named
    3. Create an empty file inside this directory
    4. Start named
     
Loading...