From: Eric Sandeen <sandeen@sandeen.net>
To: Kuo Hugo <tonytkdk@gmail.com>, Brian Foster <bfoster@redhat.com>,
xfs@oss.sgi.com
Cc: Hugo Kuo <hugo@swiftstack.com>, darrell@swiftstack.com
Subject: Re: Data can't be wrote to XFS RIP [<ffffffffa041a99a>] xfs_dir2_sf_get_parent_ino+0xa/0x20
Date: Thu, 18 Jun 2015 09:59:38 -0500 [thread overview]
Message-ID: <5582DCDA.9070200@sandeen.net> (raw)
In-Reply-To: <CA++_uhuLbTT32v4ZeVkP3WOjBEeMU0O1NZDcv66a67hZ=pj9Sw@mail.gmail.com>
On 6/18/15 9:29 AM, Kuo Hugo wrote:
>>- Have you tried an 'xfs_repair -n' of the affected filesystem? Note that -n will report problems only and prevent any modification by repair.
>
> *We might to to xfs_repair if we can address which disk causes the issue. *
If you do, please save the output, and if it finds anything, please provide the output in this thread.
Thanks,
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-06-18 14:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 11:56 Data can't be wrote to XFS RIP [<ffffffffa041a99a>] xfs_dir2_sf_get_parent_ino+0xa/0x20 Kuo Hugo
2015-06-18 13:31 ` Brian Foster
2015-06-18 14:29 ` Kuo Hugo
2015-06-18 14:59 ` Eric Sandeen [this message]
2015-07-09 10:57 ` Kuo Hugo
2015-07-09 12:51 ` Brian Foster
2015-07-09 13:20 ` Kuo Hugo
2015-07-09 13:27 ` Kuo Hugo
2015-07-09 15:18 ` Brian Foster
2015-07-09 16:40 ` Kuo Hugo
2015-07-09 18:32 ` Brian Foster
2015-07-10 5:36 ` Kuo Hugo
2015-07-10 10:39 ` Kuo Hugo
2015-07-10 16:25 ` Kuo Hugo
2015-07-13 12:52 ` Brian Foster
2015-07-13 14:06 ` Kuo Hugo
2015-07-13 17:01 ` Brian Foster
2015-07-13 18:10 ` Kuo Hugo
2015-07-17 19:39 ` Kuo Hugo
2015-07-20 11:46 ` Brian Foster
2015-07-20 14:30 ` Kuo Hugo
2015-07-20 15:12 ` Brian Foster
2015-07-22 8:54 ` Kuo Hugo
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=5582DCDA.9070200@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bfoster@redhat.com \
--cc=darrell@swiftstack.com \
--cc=hugo@swiftstack.com \
--cc=tonytkdk@gmail.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.