All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: David Bernick <dbernick@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair problem.
Date: Sun, 21 Dec 2008 11:01:31 -0600	[thread overview]
Message-ID: <494E766B.5080102@sandeen.net> (raw)
In-Reply-To: <7bcfcfff0812210852v6c1cd522i334de914e1e9a112@mail.gmail.com>

David Bernick wrote:
> Thanks for the help so far:
>  
> It my output was from "sb 0". Thanks for reminding me to be explicit.
>  
> The system is a 64-bit system with 32-GB of RAM. It's going through the
> FS right now with XFS repair.
> Output of xfs_repair says, "arno=3" and about 81.6% of RAM is used by
> the process. Think 32 G will be enough to handle this task?
> I actually don't KNOW the original error, unfortunately, when growing. I
> came into this late.
>  
> We're using repair 2.9.4. Worth getting a more recent version?

2.9.8 had some memory usage improvements (reductions) for repair IIRC

> Kernel is - 2.6.18-92.1.1.el5

heh; RHEL5 does not support xfs ;)

You probably hit:

TAKE 959978 - growing an XFS filesystem by more than 2TB is broken
http://oss.sgi.com/archives/xfs/2007-01/msg00053.html

I'd see if you can get centos to backport that fix (I assume you're
using centos or at least their kernel module; if not you can backport it
yourself...)

> I "backed off" by vgsplit-ing the new physical device from the original
> vgroup, so I was left with my original partition. I am hoping to mount
> the original device since the "expanded" fs didn't work. I am hoping
> xfs_repair helps that.

well, you don't want to take out part of the device if the fs thinks it
owns it now, but from the db output I think you still have the smaller size.

I'd read through:

http://oss.sgi.com/archives/xfs/2008-01/msg00085.html

and see if it helps you recover.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2008-12-21 17:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-21 15:03 xfs_repair problem David Bernick
2008-12-21 15:55 ` Eric Sandeen
2008-12-21 16:52   ` David Bernick
2008-12-21 17:01     ` Eric Sandeen [this message]
2008-12-21 17:07       ` David Bernick
2008-12-21 22:08       ` David Bernick
2008-12-21 22:14         ` David Bernick
2008-12-21 22:20         ` Eric Sandeen
2008-12-21 17:12     ` Eric Sandeen
  -- strict thread matches above, loose matches on Subject: below --
2007-12-06 16:10 XFS_Repair PRoblem Kingghost
2007-12-06 21:06 ` David Chinner
2007-12-07  0:51   ` Kingghost

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=494E766B.5080102@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=dbernick@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.