From: Eric Sandeen <sandeen@sandeen.net>
To: Danny Shavit <danny@zadarastorage.com>,
xfs@oss.sgi.com, Dave Chinner <david@fromorbit.com>
Cc: Lev Vainblat <lev@zadarastorage.com>,
Alex Lyakas <alex@zadarastorage.com>
Subject: Re: xfs corruption issue
Date: Wed, 01 Apr 2015 13:12:28 -0400 [thread overview]
Message-ID: <551C26FC.10803@sandeen.net> (raw)
In-Reply-To: <CAC=x_0iFLbJwbKCKEe7XTKexex29wvbVQDvuN=SO5j9gX=u4rw@mail.gmail.com>
On 4/1/15 10:09 AM, Danny Shavit wrote:
> Hello Dave,
> My name is Danny Shavit and I am with Zadara storage.
> We will appreciate your feedback reagrding an xfs_corruption and xfs_reapir issue.
>
> We found a corrupted xfs volume in one of our systems. It is around 1 TB size and about 12 M files.
> We run xfs_repair on the volume which succeeded after 42 minutes.
> We noticed that memory consumption raised to about 7.5 GB.
> Since some customers are using only 4GB (and sometimes even 2 GB) we tried running "xfs_repair -m 3200" on a 4GB RAM machine.
> However, this time an OOM event happened during handling of AG 26 during step 3.
> The log of xfs_repair is enclosed below.
> We will appreciate your feedback on the amount of memory needed for xfs_repair in general and when using "-m" option specifically.
> The xfs metadata dump (prior to xfs_repair) can be found here:
> https://zadarastorage-public.s3.amazonaws.com/xfs/xfsdump-prod-ebs_2015-03-30_23-00-38.tgz
> It is a 1.2 GB file (and 5.7 GB uncompressed).
>
> We will appreciate your feedback on the corruption pattern as well.
> --
> Thank you,
> Danny Shavit
> Zadarastorage
>
> ---------- xfs_repair log ----------------
Just a note ...
> bad . entry in directory inode 5691013154, was 5691013170: correcting
101010011001101011111100000100100
101010011001101011111100000110100
^ bit flip
> bad . entry in directory inode 5691013156, was 5691013172: correcting
101010011001101011111100000100100
101010011001101011111100000110100
^ bit flip
etc ...
> bad . entry in directory inode 5691013157, was 5691013173: correcting
> bad . entry in directory inode 5691013163, was 5691013179: correcting
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-04-01 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 14:09 xfs corruption issue Danny Shavit
2015-04-01 16:38 ` Brian Foster
2015-04-01 17:12 ` Eric Sandeen [this message]
2015-04-06 7:02 ` Danny Shavit
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=551C26FC.10803@sandeen.net \
--to=sandeen@sandeen.net \
--cc=alex@zadarastorage.com \
--cc=danny@zadarastorage.com \
--cc=david@fromorbit.com \
--cc=lev@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.