From: Eric Sandeen <sandeen@sandeen.net>
To: Rafal Blaszczyk <blaszczykr+linux@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Fwd: xfs - fixing wrong xfs size
Date: Wed, 05 May 2010 17:12:02 -0500 [thread overview]
Message-ID: <4BE1ED32.7010108@sandeen.net> (raw)
In-Reply-To: <28465863.post@talk.nabble.com>
On 05/05/2010 03:09 PM, Rafal Blaszczyk wrote:
>
>
>
> On Mon, Apr 13, 2009 at 5:02 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
>
>
>>> attempt to access beyond end of device
>>> md0: rw=0, want=123024384, limit=123023488
>>> I/O error in filesystem ("md0") meta-data dev md0 block 0x75533f8
>>
>> ("xfs_read_buf") error 5 buf count 4096
>>>
>>> XFS: size check 2 failed
>
> Hi,
> I've had similiar problems with md on top of lvm after converting from
> single LV to mirrored (md device). I've managed to solve it by expanding
> underlying devices by just a few megabytes. I suppose it's not your case
> because you're dealing with bare devices.
> But you could still try to experiment with xfs_growfs or other xfs_* tools.
>
> From my case - this is not md's fault. XFS wants to have more underlying
> space than it has and it cannot be mounted.
xfs wants only as much space as it has when it was created :)
If that changes such that it is smaller, you'll get this warning at
mount time. This is almost certainly the result of something that
happened outside xfs's control.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-05 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 14:13 xfs - fixing wrong xfs size Nebojsa Trpkovic
2009-04-13 15:02 ` Eric Sandeen
[not found] ` <dbd747120904130913p45c2979eu5afd15f5a6ca7b7f@mail.gmail.com>
2009-04-13 16:33 ` Fwd: " Nebojsa Trpkovic
2010-05-05 20:09 ` Rafal Blaszczyk
2010-05-05 22:12 ` Eric Sandeen [this message]
2010-05-05 22:22 ` Eric Sandeen
2010-11-14 11:16 ` johahoff
2010-11-15 16:26 ` Eric Sandeen
2010-12-19 14:37 ` johahoff
2010-12-19 17:27 ` 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=4BE1ED32.7010108@sandeen.net \
--to=sandeen@sandeen.net \
--cc=blaszczykr+linux@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.