Freezes with 6.0 and 7-CURRENT when working with many symlinks/dirs

From: Attila Nagy (bra_at_fsn.hu)
Date: 10/28/05

  • Next message: dawnshade: "Re[4]: [PATCH] ACPICA 20051021 import" 
    Date: Fri, 28 Oct 2005 15:50:09 +0200
To: current@FreeBSD.org

    Hello,

    I'm struggling with this bug for a while now. I have a fully
    reproduceable freeze with both RELENG_6 and HEAD in amd64 mode (I could
    not try with i386).

    It strikes when I want to synchonise a large pool of
    symlinks/directories from another machine to this FreeBSD one.
    The total number of files is about 6-10 million.

    The freeze occurs randomly, either when rsync deletes a massive amount
    of symlinks, or directories on the local machine, or when it starts to
    create them. But it freezes, no matter what I do.

    The machine itself is a HP DL380G4 (two Xeons, HTT on), which has an
    additional SmartArray 6402 controller (ciss0: the SmartArray 6i on the
    motherboard and ciss1 the 6402). I would like to sync onto ciss1, that's
    where the activity happens.

    Under "freeze" I mean the machine stops working, I can not ping, ssh
    sessions disconnect and the console hungs. I can do two things in this
    stage. Turning MP_WATCHDOG on catches this and enters the debugger and
    when I issue an NMI I get the same effect (of course :).

    I've tried the following to workaround or locate the source of this problem:
    - turn HTT off
    - turn softupdates off
    - turn ACPI off (with the beastie menu)
    - turn preemption off
    - debug.mpsafevfs=0 and debug.mpsafenet=0
    - turn dirhash off
    all without success.

    I have nfsd and quota enabled, but currently the former is not in use.
    The synchronised directories and files are in the ownership of many, non
    existend (not in /etc/master.passwd) uids and I have quota for most of
    those uids.

    I could collect three traces, some of them are a little bit mangled by
    the ILO (ssh access to the console).

    http://people.fsn.hu/~bra/freebsd/crash-20051028/

    crash1 and crash2 is from the in-kernel debugger, crash3 is after the
    MP_WATCHDOG fired and a call doadump and kgdb kernel /var/crash/vmcore...

    Any ideas what else should I try, or what should I do in the debugger to
    make it easier to find where the problem is?

    Thanks, 

    -- 
Attila Nagy                                   e-mail: Attila.Nagy@fsn.hu
Adopt a directory on our free software         phone: +3630 306 6758
server! http://www.fsn.hu/?f=brick
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: dawnshade: "Re[4]: [PATCH] ACPICA 20051021 import"

    Relevant Pages

    • Re: FreeBSD 7.2-STABLE boot freeze
      ... On Mon, 28 Sep 2009, Andriy Gapon wrote: ... Did you still get the message about unresolved symbol? ... I asked - when you got your latest freeze, ... Its too bad that I cant get into the debugger. ...
      (freebsd-stable)
    • RE: Machine hangs(Beta7), only reset button works
      ... I rebuild my kernel ASAP so I'm able to ... into the debugger is good news. ... locks are held. ... >> The box completely freeze typically when it's done running the first ...
      (freebsd-current)
    • Debugging Problem w/ EHShell.exe
      ... It would just freeze. ... Registered JIT debugger is not availabble. ... What is making this happen and how can I fix my Media Center's Tv? ...
      (microsoft.public.windows.mediacenter)
    • Re: Machine hangs(Beta7), only reset button works
      ... > The box completely freeze typically when it's done running the first ... > part of my backup script, resulting in no possibility to login on the ... If you still can't get into the debugger, you might try some of the ... various watchdog drivers -- some hardware comes with built in watchdog ...
      (freebsd-current)