public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Tapani Tarvainen <tapani.j.tarvainen@jyu.fi>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: "This is a bug."
Date: Thu, 10 Sep 2015 21:01:28 +0300	[thread overview]
Message-ID: <20150910180128.GE18940@tarvainen.info> (raw)
In-Reply-To: <20150910175220.GD18940@tarvainen.info>

On Thu, Sep 10, 2015 at 08:52:20PM +0300, Tapani Tarvainen (tapani@tapanitarvainen.fi) wrote:

> Also, it turns out I have another similar case: another filesystem
> (in the same RAID set) failed also, even though it'd initially
> mounted without problems. Now it shows the same symptoms,
> neither mount nor repair works (have't tried repair -L yet).

Apparently it only failed after someone tried to write on it.

Potentially interesting stuff from dmesg:

[31604.130052] XFS (dm-4): xfs_da_do_buf: bno 8388608 dir: inode 964
[31604.130080] XFS (dm-4): [00] br_startoff 8388608 br_startblock -2 br_blockcount 1 br_state 0
[31604.130126] XFS (dm-4): Internal error xfs_da_do_buf(1) at line 2011 of file /build/linux-4wkEzn/
linux-3.2.68/fs/xfs/xfs_da_btree.c.  Caller 0xffffffffa0371b67
[31604.130127] 
[31604.130213] Pid: 18082, comm: du Not tainted 3.2.0-4-amd64 #1 Debian 3.2.68-1+deb7u1
[...]

-- 
Tapani Tarvainen

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

  reply	other threads:[~2015-09-10 18:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10  9:18 "This is a bug." Tapani Tarvainen
2015-09-10 10:31 ` Tapani Tarvainen
2015-09-10 11:53   ` Emmanuel Florac
2015-09-10 12:05     ` Tapani Tarvainen
2015-09-10 11:48 ` Emmanuel Florac
2015-09-10 11:55   ` Tapani Tarvainen
2015-09-10 12:30     ` Tapani Tarvainen
2015-09-10 12:36       ` Brian Foster
2015-09-10 12:54         ` Tapani Tarvainen
2015-09-10 13:01           ` Brian Foster
2015-09-10 13:05             ` Tapani Tarvainen
2015-09-10 14:51               ` Brian Foster
2015-09-10 15:05                 ` Brian Foster
2015-09-10 17:52                   ` Tapani Tarvainen
2015-09-10 18:01                     ` Tapani Tarvainen [this message]
2015-09-10 17:31                 ` Tapani Tarvainen
2015-09-10 17:55                   ` Brian Foster
2015-09-10 18:03                     ` Tapani Tarvainen
2015-09-10 18:33                       ` Brian Foster
2015-09-11  6:19                         ` Tapani Tarvainen
2015-09-11  0:12                       ` Eric Sandeen

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=20150910180128.GE18940@tarvainen.info \
    --to=tapani.j.tarvainen@jyu.fi \
    --cc=bfoster@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