All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Maiolino <cmaiolino@redhat.com>
To: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_symlink problem? 3.1 after rc10
Date: Mon, 24 Oct 2011 12:13:19 -0200	[thread overview]
Message-ID: <20111024141319.GB4441@andromeda.usersys.redhat.com> (raw)
In-Reply-To: <201110241540.01268.arekm@maven.pl>

> It happened again:
> 
> http://ixion.pld-linux.org/~arekm/100_5434.JPG
> http://ixion.pld-linux.org/~arekm/100_5433.JPG
> 
> The weird thing is that I never ever hit this before with pre 3.1rc10 git 
> kernels. Was your bugfix a fix for new issue that was introduced in 3.1 cycle 
> or for something old?
> 
Hmm, sorry, my mistake here, I fixed a problem on xfs_readlink, not at xfs_symlink.

Although, by your last screenshots, it doesn't look to be related with the problem
I was working before.

On all screenshots the system is crashing while trying to acquire a mutex lock, I don't
know much about the code path where the crash is happening, but, maybe if you enable
CONFIG_XFS_DEBUG we can get some extra hints about where the system is crashing? Also,
have you fsck'ed this FS? maybe an `xfs_repair -nv` would give any clue if there is any
corrupted metadata which would cause this error


-- 
--Carlos

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-10-24 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24  9:48 xfs_symlink problem? 3.1 after rc10 Arkadiusz Miśkiewicz
2011-10-24 12:27 ` Carlos Maiolino
2011-10-24 13:40   ` Arkadiusz Miśkiewicz
2011-10-24 14:13     ` Carlos Maiolino [this message]
2011-10-24 21:30       ` xfs_symlink problem? [Allow pquota and gquota to be used together actually] Arkadiusz Miśkiewicz

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=20111024141319.GB4441@andromeda.usersys.redhat.com \
    --to=cmaiolino@redhat.com \
    --cc=arekm@maven.pl \
    --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.