From: "Carlos E. R." <carlos.e.r@opensuse.org>
To: XFS mailing list <xfs@oss.sgi.com>
Subject: Re: Happened again, 20140930 -- Got "Internal error XFS_WANT_CORRUPTED_GOTO". Filesystem needs reformatting to correct issue.
Date: Thu, 02 Oct 2014 13:46:18 +0200 [thread overview]
Message-ID: <542D3B0A.5030600@opensuse.org> (raw)
In-Reply-To: <20141002113205.GE19748@quack.suse.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2014-10-02 13:32, Jan Kara wrote:
> On Wed 01-10-14 04:48:42, Carlos E. R. wrote:
>> Question: where does it apply, kernel, xfsprogs? They will know,
>> but I don't, and I need that info for the bugzilla "component"
>> field ;-)
> Feel free to assign that bug to me (jack at suse.com in bugzilla)
> and I'll take care of it.
Sure, thanks.
I'm busy with other things right now, will do as soon as I can.
Yesterday I was restoring the machine.
- --
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlQtOv8ACgkQtTMYHG2NR9Ux/QCdExQvegQEierd/9RiFwvjQ+6z
wBcAmgOdaaeWY3iZaTo4HogjuxqUSsMg
=8lRj
-----END PGP SIGNATURE-----
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-02 11:46 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 9:57 Got "Internal error XFS_WANT_CORRUPTED_GOTO". Filesystem needs reformatting to correct issue Carlos E. R.
2014-07-02 12:04 ` Brian Foster
2014-07-02 13:07 ` Mark Tinguely
2014-07-03 2:54 ` Carlos E. R.
2014-07-03 3:00 ` Carlos E. R.
2014-07-03 9:43 ` Dave Chinner
2014-07-03 17:40 ` Brian Foster
2014-07-03 23:34 ` Carlos E. R.
2014-07-04 0:04 ` Dave Chinner
2014-07-04 1:29 ` Carlos E. R.
2014-07-04 1:40 ` Dave Chinner
2014-07-04 2:42 ` Carlos E. R.
2014-07-04 3:12 ` Carlos E. R.
2014-07-04 12:40 ` Brian Foster
2014-07-04 13:36 ` Carlos E. R.
2014-07-03 17:39 ` Brian Foster
2014-07-04 21:32 ` Carlos E. R.
2014-07-05 12:28 ` Brian Foster
2014-07-12 0:30 ` Carlos E. R.
2014-07-12 1:30 ` Carlos E. R.
2014-07-12 1:45 ` Carlos E. R.
2014-07-12 14:26 ` Brian Foster
2014-07-12 14:19 ` Brian Foster
2014-08-11 14:23 ` Subject : Happened again, 20140811 -- " Carlos E. R.
2014-08-11 14:44 ` Brian Foster
2014-08-11 14:58 ` Carlos E. R.
2014-08-11 17:05 ` Carlos E. R.
2014-08-11 21:31 ` Carlos E. R.
[not found] ` <53E938CC.4010103@sgi.com>
2014-08-11 22:01 ` Carlos E. R.
2014-08-11 14:57 ` Mark Tinguely
2014-08-11 15:34 ` Carlos E. R.
2014-08-11 16:14 ` Brian Foster
2014-08-11 17:08 ` Carlos E. R.
2014-08-11 21:27 ` Mark Tinguely
2014-08-11 21:50 ` Carlos E. R.
2014-08-11 21:56 ` Mark Tinguely
2014-08-11 22:36 ` Carlos E. R.
2014-08-12 0:17 ` Carlos E. R.
2014-08-12 16:51 ` Brian Foster
2014-08-12 21:17 ` Carlos E. R.
2014-08-13 12:04 ` Brian Foster
2014-08-13 13:29 ` Mark Tinguely
2014-08-13 21:04 ` Dave Chinner
2014-08-12 21:27 ` Eric Sandeen
2014-08-12 21:57 ` Dave Chinner
2014-08-12 21:59 ` Brian Foster
2014-08-12 22:21 ` Eric Sandeen
2014-08-12 23:16 ` Dave Chinner
2014-08-13 0:07 ` Carlos E. R.
2014-09-30 22:27 ` Happened again, 20140930 " Carlos E. R.
2014-10-01 0:45 ` Dave Chinner
2014-10-01 2:48 ` Carlos E. R.
2014-10-01 3:04 ` Eric Sandeen
2014-10-02 11:32 ` Jan Kara
2014-10-02 11:46 ` Carlos E. R. [this message]
2014-10-05 14:28 ` Carlos E. R.
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=542D3B0A.5030600@opensuse.org \
--to=carlos.e.r@opensuse.org \
--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