public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: M Kili <m0kili@gmail.com>, xfs@oss.sgi.com
Subject: Re: can't mount xfs partition
Date: Thu, 01 Mar 2007 18:13:16 -0600	[thread overview]
Message-ID: <45E76C1C.4040903@sandeen.net> (raw)
In-Reply-To: <29a617af0703011611p4ed51bb4g63b1ec0da42143bc@mail.gmail.com>

M Kili wrote:
> On 3/1/07, Eric Sandeen <sandeen@sandeen.net> wrote:
>> M Kili wrote:
>> > xfs_check doesn't give any message, and still, the image can't be
>> > mounted, with the same error:
>> > # mount -o loop hda5.img /mnt/
>> > mount: /dev/loop0: can't read superblock
>>
>> look at dmesg output, see what it says.
> 
> [17206988.072000] SGI XFS with ACLs, security attributes, realtime,
> large block numbers, no debug enabled
> [17206988.072000] SGI XFS Quota Management subsystem
> [17206988.080000] attempt to access beyond end of device
> [17206988.080000] hda5: rw=0, want=39086080, limit=39065600
> [17206988.080000] I/O error in filesystem ("hda5") meta-data dev hda5
> block 0x25467ff       ("xfs_read_buf") error 5 buf count 512
> [17206988.080000] XFS: size check 2 failed
> 
> I guess I must repartition, am I right?

Yep, looks like your partition endpoint is just slightly too small.

-Eric

>>
>> Does "-t xfs" help?
> 
> no
> 
>>
>> -Eric
>>
>>
> 

      parent reply	other threads:[~2007-03-02  0:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 15:48 can't mount xfs partition M Kili
2007-03-01 16:38 ` Eric Sandeen
     [not found]   ` <29a617af0703011611p4ed51bb4g63b1ec0da42143bc@mail.gmail.com>
2007-03-02  0:13     ` Eric Sandeen [this message]

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=45E76C1C.4040903@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=m0kili@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