From: Eric Sandeen <sandeen@sandeen.net>
To: Nebojsa Trpkovic <trx.lists@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs - fixing wrong xfs size
Date: Mon, 13 Apr 2009 10:02:21 -0500 [thread overview]
Message-ID: <49E353FD.5060207@sandeen.net> (raw)
In-Reply-To: <dbd747120904130713t7388971axf75ee779b5b1e1f2@mail.gmail.com>
Nebojsa Trpkovic wrote:
> hello.
>
> I had problem with raid5 on my system.
> after recovering of the array, I can not mount XFS that resides on it.
> I've run xfs_check and xfs_repair (which fixed some errors) and now I
> can run them all day long without any errors.
>
> but, when I try to mount that partition, I get:
>
> mount: /dev/md0: can't read superblock
>
>
> and there's
>
> Filesystem "md0": Disabling barriers, not supported by the underlying device
>
> 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
So, the superblock says that the fs is 896 1k-blocks longer than the
device actually is.
> in the dmesg.
>
>
> is there any way to "fix" this wrong size of XFS ?
hard to say, almost certainly sounds like an md problem; is there a
chance that your raid recovery led to a device which is somehow smaller
than it started? You could change the superblock block-count value, but
I'm guessing that something else has gone wrong.
It might be useful to know what errors xfs_repair found.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-04-13 15:02 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 [this message]
[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
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=49E353FD.5060207@sandeen.net \
--to=sandeen@sandeen.net \
--cc=trx.lists@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox