From: Thomas Themel <thomas@themel.com>
To: linux-kernel@vger.kernel.org
Subject: XFS corruption on ARM
Date: Sun, 28 Dec 2008 13:33:05 +0100 [thread overview]
Message-ID: <20081228123305.GE30805@themel.com> (raw)
Hi,
there was a thread[0] on this list in 2008-10 about XFS corrupting
rather quickly on recent ARM kernels, which seems to have petered out
without any apparent results. I'm still seeing the same problems with
2.6.28, and I suspect that this qualifies as a kind of regression
(though ancient), since the devices I'm running this on (Buffalo
LinkStations) originally ship with a (vendor-modified) 2.6.16 kernel,
where XFS seems to be working.
Is this still on anyone's radar? I'm willing to test proposed fixes and
supply data[1], but lack any deep knowledge of either ARM or XFS internals.
(Please Cc: me, I'm not on the list.)
[0] http://lkml.org/lkml/2008/10/1/382
[1] Though mine doesn't look any different from what was posted in [0]
to the little-trained eye.
ciao,
--
[*Thomas Themel*]
[extended contact] But let your communication be, Yea, yea; Nay, nay:
[info provided in] for whatsoever is more than these cometh of evil.
[*message header*] - Matthew 5:37
next reply other threads:[~2008-12-28 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 12:33 Thomas Themel [this message]
2008-12-29 0:28 ` XFS corruption on ARM Dave Chinner
2008-12-29 5:49 ` 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=20081228123305.GE30805@themel.com \
--to=thomas@themel.com \
--cc=linux-kernel@vger.kernel.org \
/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