From: Eric Sandeen <sandeen@sandeen.net>
To: Eli Morris <ermorris@ucsc.edu>
Cc: xfs@oss.sgi.com
Subject: Re: filesystem shrinks after using xfs_repair
Date: Sat, 24 Jul 2010 16:09:42 -0500 [thread overview]
Message-ID: <4C4B5696.8060302@sandeen.net> (raw)
In-Reply-To: <F2D7937E-43FC-47F4-B041-B9C5C2CBCCD4@ucsc.edu>
Eli Morris wrote:
> Hi All,
>
> I've got this problem where if I run xfs_repair, my filesystem
> shrinks by 11 TB, from a volume size of 62 TB to 51 TB. I can grow
> the filesystem again with xfs_growfs, but then rerunning xfs_repair
> shrinks it back down again. The first time this happened was a few
> days ago and running xfs_repair took about 7 TB of data with it. That
> is, out of the 11 TB of disk space that vanished, 7 TB had data on
> it, and 4 TB was empty space. XFS is running on top of an LVM volume.
> It's on an Intel/Linux system running Centos 5 (2.6.18-128.1.14.el5).
Running 2.6.18-138.el5 and beyond will have a much more uptodate xfs,
just FWIW.
-Eric
> Does anyone have an idea on what would cause such a thing and what I
> might try to keep it from continuing to happen. I could just never
> run xfs_repair again, but that doesn't seem like a good thing to
> count on. Major bonus points if anyone has any ideas on how to get my
> 7 TB of data back also. It must be there somewhere and it would be
> very bad to lose.
>
> thanks for any help and ideas. I'm just stumped right now.
>
> Eli _______________________________________________ xfs mailing list
> xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-24 21:06 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 23:07 filesystem shrinks after using xfs_repair Eli Morris
2010-07-10 8:16 ` Stan Hoeppner
2010-07-24 21:09 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-11 6:32 Eli Morris
2010-07-11 10:56 ` Stan Hoeppner
2010-07-11 16:29 ` Emmanuel Florac
2010-07-12 1:10 Eli Morris
2010-07-12 2:24 ` Stan Hoeppner
2010-07-12 11:47 ` Emmanuel Florac
2010-07-23 8:30 ` Eli Morris
2010-07-23 10:23 ` Emmanuel Florac
2010-07-23 16:36 ` Eli Morris
2010-07-24 0:54 ` Dave Chinner
2010-07-24 1:08 ` Eli Morris
2010-07-24 2:39 ` Dave Chinner
2010-07-26 3:20 ` Eli Morris
2010-07-26 3:45 ` Dave Chinner
2010-07-26 4:04 ` Eli Morris
2010-07-26 5:57 ` Michael Monnerie
2010-07-26 6:06 ` Dave Chinner
2010-07-26 6:46 ` Eli Morris
2010-07-26 8:40 ` Michael Monnerie
2010-07-26 9:49 ` Emmanuel Florac
2010-07-26 17:22 ` Eli Morris
2010-07-26 18:33 ` Stuart Rowan
2010-07-26 21:06 ` Emmanuel Florac
2010-07-27 5:02 ` Eli Morris
2010-07-27 6:48 ` Stan Hoeppner
2010-07-27 8:21 ` Michael Monnerie
2010-07-26 10:20 ` Dave Chinner
2010-07-28 5:12 ` Eli Morris
2010-07-29 19:22 ` Eli Morris
2010-07-29 22:09 ` Emmanuel Florac
2010-07-29 22:48 ` Eli Morris
2010-07-29 23:01 ` Dave Chinner
2010-07-29 23:15 ` Eli Morris
2010-07-30 0:39 ` Michael Monnerie
2010-07-30 1:49 ` Eli Morris
2010-07-30 7:15 ` Emmanuel Florac
2010-07-30 7:57 ` Christoph Hellwig
2010-07-30 10:23 ` Michael Monnerie
2010-07-30 10:29 ` Christoph Hellwig
2010-07-30 12:40 ` Michael Monnerie
2010-07-30 13:17 ` Emmanuel Florac
2010-07-12 6:39 Eli Morris
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=4C4B5696.8060302@sandeen.net \
--to=sandeen@sandeen.net \
--cc=ermorris@ucsc.edu \
--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