From: Eric Sandeen <sandeen@sandeen.net>
To: Danny Shavit <danny@zadarastorage.com>
Cc: Alex Lyakas <alex@zadarastorage.com>, xfs@oss.sgi.com
Subject: Re: xfs corruption
Date: Thu, 3 Sep 2015 11:14:39 -0500 [thread overview]
Message-ID: <55E871EF.4040603@sandeen.net> (raw)
In-Reply-To: <55E85F5F.6010005@sandeen.net>
On 9/3/15 9:55 AM, Eric Sandeen wrote:
> On 9/3/15 9:26 AM, Danny Shavit wrote:
...
>> We are using modified xfs. Mainly, added some reporting features and
>> changed discard operation to be aligned with chunk sizes used in our
>> systems. The modified code resides at https://github.com/zadarastora
>> <https://github.com/zadarastorage/zadara-xfs-pushback>ge/zadara-xfs-pushback
>> <https://github.com/zadarastorage/zadara-xfs-pushback>.
>
> Interesting, thanks for the pointer. I guess at this point I have to
> ask, do you see these same problems without your modifications?
Have you ever mounted this filesystem on non-zadara kernels?
looking at
https://github.com/zadarastorage/zadara-xfs-pushback/commit/094df949fd080ede546bb7518405ab873a444823
you've changed the disk format w/o adding a feature flag,
which is pretty dangerous.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-09-03 16:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 11:09 xfs corruption Danny Shavit
2015-09-03 13:22 ` Eric Sandeen
2015-09-03 14:26 ` Danny Shavit
2015-09-03 14:55 ` Eric Sandeen
2015-09-03 16:14 ` Eric Sandeen [this message]
2015-09-06 10:19 ` Alex Lyakas
2015-09-06 21:56 ` Eric Sandeen
2015-09-07 8:30 ` Alex Lyakas
-- strict thread matches above, loose matches on Subject: below --
2016-02-24 6:12 XFS Corruption fangchen sun
2016-02-24 22:23 ` Eric Sandeen
2014-12-21 11:42 XFS corruption Alex Lyakas
2014-12-21 18:13 ` Eric Sandeen
2014-12-21 23:08 ` Dave Chinner
2014-12-22 10:09 ` Alex Lyakas
2014-12-22 14:42 ` Brian Foster
2014-12-23 0:39 ` Dave Chinner
2014-12-23 9:57 ` Alex Lyakas
2014-12-23 20:36 ` Dave Chinner
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=55E871EF.4040603@sandeen.net \
--to=sandeen@sandeen.net \
--cc=alex@zadarastorage.com \
--cc=danny@zadarastorage.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.