All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent CARON <lcaron@lncsa.com>
To: xfs@oss.sgi.com
Cc: David Chinner <dgc@sgi.com>
Subject: Re: Crash on 2.6.21.7 Vanilla + DRBD 0.7
Date: Thu, 11 Oct 2007 09:36:21 +0200	[thread overview]
Message-ID: <470DD275.9090602@lncsa.com> (raw)
In-Reply-To: <20071010224644.GP995458@sgi.com>

David Chinner wrote:
> Yes, please turn on slab debugging so we can try to find the cause
> of this memory corruption. I expect the problem to be in DRBD as
> nobody else running XFS is reporting this problem. However, without
> running with the right debug options enabled we'll never get to
> the bottom of the problem.


Hi,

Before installing a new kernel i've got a (little?) clue.

The setup is as follows:

The drbd partition is mounted to a generic mountpoint
/dev/drbd1 on /data/web type xfs (rw)

The subdirectories of /data/web are mounted (mount --bind) to another
directory
/data/web/var/www on /var/www type xfs (rw,bind)
/data/web/var/lib/postgresql on /var/lib/postgresql type xfs (rw,bind)
/data/web/var/lib/mysql on /var/lib/mysql type xfs (rw,bind)


It seems I made a mistake here.

mount -t xfs --bind /data/web/var/www /var/www

instead of

mount --bind /data/web/var/www /var/www

Could this be 'THE' root of the problem (if the system then sees
/var/www as a 'real' XFS filesystem and not a directory mounted over) ?

Thanks

Laurent

  reply	other threads:[~2007-10-11  7:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04 13:33 Crash on 2.6.21.7 Vanilla + DRBD 0.7 vindex+lists-xfs
2007-10-04 14:27 ` Hannes Dorbath
2007-10-04 16:42   ` Laurent CARON
2007-10-04 14:35 ` Hannes Dorbath
2007-10-04 16:33   ` Laurent CARON
2007-10-10 15:15   ` Louis-David Mitterrand
2007-10-10 22:46     ` David Chinner
2007-10-11  7:36       ` Laurent CARON [this message]
2007-10-04 23:10 ` David Chinner
  -- strict thread matches above, loose matches on Subject: below --
2007-10-04  7:29 Laurent Caron
2007-10-07 23:36 ` David Chinner
2007-10-08 12:47   ` Laurent CARON

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=470DD275.9090602@lncsa.com \
    --to=lcaron@lncsa.com \
    --cc=dgc@sgi.com \
    --cc=xfs@oss.sgi.com \
    /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.