From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_symlink problem? 3.1 after rc10
Date: Mon, 24 Oct 2011 15:40:01 +0200 [thread overview]
Message-ID: <201110241540.01268.arekm@maven.pl> (raw)
In-Reply-To: <20111024122729.GA4441@andromeda.usersys.redhat.com>
On Monday 24 of October 2011, Carlos Maiolino wrote:
> > My 3.1 (after) rc10 crashed (there was no xfs changes after it afaik).
> >
> > Could anyone verify that this isn't some nasty xfs problem since it's
> > close to final 3.1? Happened only once.
> >
> > http://ixion.pld-linux.org/~arekm/IMG_6019.JPG
> >
> > No quota was used, xfs on top of luks on top of ssd drive.
>
> It looks to be caused by a general protection fault, and giving the place
It happened again:
http://ixion.pld-linux.org/~arekm/100_5434.JPG
http://ixion.pld-linux.org/~arekm/100_5433.JPG
> where this crashed I would say this sounds like the bug I've fixed some
> days ago related with the size of the symlinks.
> I can be wrong though, and this is related with another problem.
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?
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-10-24 13:40 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 [this message]
2011-10-24 14:13 ` Carlos Maiolino
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=201110241540.01268.arekm@maven.pl \
--to=arekm@maven.pl \
--cc=cmaiolino@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox