From: Eric Sandeen <sandeen@sandeen.net>
To: christian gattermair <christian.gattermair@mci.edu>
Cc: linux-xfs@oss.sgi.com
Subject: Re: xfs_check - out of memory | xfs_repair - superblock error reading
Date: Tue, 19 Sep 2006 10:02:50 -0500 [thread overview]
Message-ID: <4510069A.6050508@sandeen.net> (raw)
In-Reply-To: <200609191203.22083.christian.gattermair@mci.edu>
christian gattermair wrote:
> hi!
>
> thanks for all your answers
>
>
> parted:
>
> Disk geometry for /dev/sda: 0.000-3147012,000 megabytes
> Disk label type: msdos
> Minor Start End Type Filesystem Flags
> 1 0,031 1049854,423 primary xfs
>
> cat /proc/partitions
>
> 8 0 3222540288 sda
> 8 1 1075050898 sda1
sda1 is only 1 terabyte. sda itself appears to be about 3 terabytes.
I think you need to sort out where your filesystem is living...
Did someone repartition sda?
> Vendor: AMCC Model: 9500S-12 DISK Rev: 2.06
> Type: Direct-Access ANSI SCSI revision: 03
> sda : very big device. try to use READ CAPACITY(16).
Or perhaps this is the 2T lun problem... although you say it was working
before. At any rate this isn't looking like an xfs problem at this
stage - your kernel thinks that your storage is smaller than you think
it is.
-Eric
> SCSI device sda: 6445080576 512-byte hdwr sectors (3299881 MB)
> SCSI device sda: drive cache: write back, no read (daft)
> /dev/scsi/host0/bus0/target0/lun0: p1
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
next prev parent reply other threads:[~2006-09-19 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 13:19 xfs_check - out of memory | xfs_repair - superblock error reading christian gattermair
2006-09-18 14:41 ` linux-xfs
2006-09-19 10:03 ` christian gattermair
2006-09-19 15:02 ` Eric Sandeen [this message]
2006-09-20 15:35 ` christian gattermair
2006-09-18 22:23 ` David Chinner
2006-09-18 22:56 ` Stephan Jansen
2006-09-19 0:33 ` Barry Naujok
2006-09-19 7:56 ` Frank Hellmann
-- strict thread matches above, loose matches on Subject: below --
2006-09-19 13:19 christian gattermair
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=4510069A.6050508@sandeen.net \
--to=sandeen@sandeen.net \
--cc=christian.gattermair@mci.edu \
--cc=linux-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